freefacebook.com

freefacebook.com is SSL secured

Free website and domain report on freefacebook.com

Last Updated: 14th March, 2023 Update Now
Overview

Snoop Summary for freefacebook.com

This is a free and comprehensive report about freefacebook.com. The domain freefacebook.com is currently hosted on a server located in United States with the IP address 157.240.241.17, where the local currency is USD and English is the local language. Our records indicate that freefacebook.com is owned/operated by Meta Platforms, Inc.. If freefacebook.com was to be sold it would possibly be worth $503 USD (based on the daily revenue potential of the website over a 24 month period). Freefacebook.com receives an estimated 237 unique visitors every day - a decent amount of traffic! This report was last updated 14th March, 2023.

About freefacebook.com

Site Preview: freefacebook.com freefacebook.com
Title: Facebook
Description: Create an account or log into Facebook. Connect with friends, family and other people you know. Share photos and videos, send messages and get updates.
Keywords and Tags:
Related Terms:
Fav Icon:
Age: Over 8 years old
Domain Created: 3rd September, 2015
Domain Updated: 6th June, 2022
Domain Expires: 3rd September, 2023
Review

Snoop Score

1/5

Valuation

$503 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,759,338
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 7
Moz Page Authority: 18

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 237
Monthly Visitors: 7,214
Yearly Visitors: 86,505
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $21 USD
Yearly Revenue: $247 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: freefacebook.com 16
Domain Name: freefacebook 12
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 77
Performance 99
Accessibility 98
Best Practices 83
SEO 83
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.facebook.com/
Updated: 16th January, 2023

1.88 seconds
First Contentful Paint (FCP)
74%
13%
13%

0.01 seconds
First Input Delay (FID)
95%
3%
2%

Simulate loading on desktop
99

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for freefacebook.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://freefacebook.com/
http/1.1
0
178.27400000533
373
0
301
text/html
https://www.facebook.com/
h2
178.63600002602
387.81600003131
23558
64075
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/y4/l/0,cross/ZtwO7u3tI0A.css?_nc_x=Ij3Wp8lg5Kz
h2
422.24300000817
440.73400000343
4126
14025
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yV/l/0,cross/KxGJ10xTR_J.css?_nc_x=Ij3Wp8lg5Kz
h2
422.76099999435
439.93699998828
2056
3608
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yF/l/0,cross/CkWclLPozxq.css?_nc_x=Ij3Wp8lg5Kz
h2
422.90700000012
441.51099998271
2276
6521
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yK/l/0,cross/gCjTaPZldvh.css?_nc_x=Ij3Wp8lg5Kz
h2
423.02699998254
446.40700001037
8309
33765
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yi/l/0,cross/yotEdcUw9Gj.css?_nc_x=Ij3Wp8lg5Kz
h2
423.13399998238
438.68999998085
958
567
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yn/l/0,cross/qGdP5mQHk9S.css?_nc_x=Ij3Wp8lg5Kz
h2
423.34199999459
445.3050000011
2883
7637
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yr/l/0,cross/u4xvA0Tw-4L.css?_nc_x=Ij3Wp8lg5Kz
h2
423.48400002811
444.89300000714
1119
1225
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/5qNQnR2Vk-N.js?_nc_x=Ij3Wp8lg5Kz
h2
423.62200003117
447.92000000598
95128
370407
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
h2
506.65500003379
530.10299999733
1708
2385
200
image/svg+xml
Image
https://facebook.com/security/hsts-pixel.gif
h2
506.80500001181
564.79899998521
3883
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yH/r/Beg-lgh4F5-.js?_nc_x=Ij3Wp8lg5Kz
h2
448.70399998035
463.14900001744
1878
2623
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/F3saR61Z2qK.js?_nc_x=Ij3Wp8lg5Kz
h2
465.30099998927
485.18000001786
8881
26231
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yu/r/1fIb2S0KdFD.js?_nc_x=Ij3Wp8lg5Kz
h2
473.79200003343
496.4940000209
7412
21015
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y7/r/ZXk3n4Ns6mf.js?_nc_x=Ij3Wp8lg5Kz
h2
506.18299999041
523.96999998018
3185
7143
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/yA/l/en_US/k0t_ZluwxbD.js?_nc_x=Ij3Wp8lg5Kz
h2
506.418999983
523.42799998587
16861
62996
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y9/r/R-poEPeDR18.js?_nc_x=Ij3Wp8lg5Kz
h2
506.54299999587
521.28600003198
3902
9443
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yU/r/O7nelmd9XSI.png
h2
514.05599998543
529.72200000659
708
95
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/kNYkizqJr9j.png
h2
515.39200003026
530.48700001091
20273
19631
200
image/png
Image
data
593.48500001943
593.71600003215
0
0
200
text/css
Stylesheet
data
593.87799998512
594.06500001205
0
78
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/p0bcnVbl1Lr.js?_nc_x=Ij3Wp8lg5Kz
h2
638.22700001765
680.3470000159
11999
35053
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yb/r/OxOwVwf8Ncg.js?_nc_x=Ij3Wp8lg5Kz
h2
638.73599999351
676.62500002189
1900
3083
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/1OGwbGbDEwH.js?_nc_x=Ij3Wp8lg5Kz
h2
639.18800000101
657.41400001571
5384
13994
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y6/r/l6vBJbL3cbT.js?_nc_x=Ij3Wp8lg5Kz
h2
639.78199998382
665.27200001292
3640
7470
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y1/r/ycSXPX6P6W5.js?_nc_x=Ij3Wp8lg5Kz
h2
640.60400001472
677.29500000132
4936
10205
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yI/r/pPEWqCTW2Ud.js?_nc_x=Ij3Wp8lg5Kz
h2
640.95999998972
677.62800003402
9746
28457
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/APH-FcpdMJY.js?_nc_x=Ij3Wp8lg5Kz
h2
641.44300000044
678.0869999784
9909
33047
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
h2
642.12600002065
657.9180000117
13719
43510
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/_tJ17sGyxOX.js?_nc_x=Ij3Wp8lg5Kz
h2
644.76500003366
679.88399998285
8201
18154
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
h2
645.11600002879
697.44399999036
9993
50828
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/y_/l/en_US/LHUxA4o6J25.js?_nc_x=Ij3Wp8lg5Kz
h2
645.5539999879
681.09500000719
14118
43610
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y1/r/senRRbYy1tL.js?_nc_x=Ij3Wp8lg5Kz
h2
645.88900003582
679.19599998277
4669
13493
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yV/r/NVFkPpYW_MU.js?_nc_x=Ij3Wp8lg5Kz
h2
646.39000000898
677.02599999029
2277
5474
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yv/r/_ey69GUvBVn.js?_nc_x=Ij3Wp8lg5Kz
h2
646.74100000411
678.94900002284
3062
7196
200
application/x-javascript
Script
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU29zEdEc8uwdK0lW4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwnU1oU884y0lW0ny0RE2Jw8W0iW0lK3qaw4kwbS1Lw4Cw&__hs=19373.BP%3ADEFAULT.2.0.0.0.0&__hsi=7189065703743922852&__req=1&__rev=1006821231&__s=twj6hn%3Alllcdp%3A9walxc&__spin_b=trunk&__spin_r=1006821231&__spin_t=1673834795&__user=0&dpr=1&jazoest=2952&lsd=AVoMXCEmanI
h2
779.72400002182
817.75699998252
4069
0
200
text/html
XHR
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU29zEdEc8uwdK0lW4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwnU1oU884y0lW0ny0RE2Jw8W0iW0lK3qaw4kwbS1Lw4Cw&__hs=19373.BP%3ADEFAULT.2.0.0.0.0&__hsi=7189065703743922852&__req=2&__rev=1006821231&__s=twj6hn%3Alllcdp%3A9walxc&__spin_b=trunk&__spin_r=1006821231&__spin_t=1673834795&__user=0&dpr=1&jazoest=2952&lsd=AVoMXCEmanI
h2
1733.3080000244
1872.5480000139
4086
0
200
text/html
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Freefacebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Freefacebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Freefacebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Freefacebook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Freefacebook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 49 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/5qNQnR2Vk-N.js?_nc_x=Ij3Wp8lg5Kz
95128
50126
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 13 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/kNYkizqJr9j.png
19631
12811.2
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.facebook.com/
210.173
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Freefacebook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://freefacebook.com/
190
https://www.facebook.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Freefacebook.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/5qNQnR2Vk-N.js?_nc_x=Ij3Wp8lg5Kz
13807
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
0
Avoids enormous network payloads — Total size was 314 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/5qNQnR2Vk-N.js?_nc_x=Ij3Wp8lg5Kz
95128
https://www.facebook.com/
23558
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/kNYkizqJr9j.png
20273
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/yA/l/en_US/k0t_ZluwxbD.js?_nc_x=Ij3Wp8lg5Kz
16861
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/y_/l/en_US/LHUxA4o6J25.js?_nc_x=Ij3Wp8lg5Kz
14118
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
13719
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/p0bcnVbl1Lr.js?_nc_x=Ij3Wp8lg5Kz
11999
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
9993
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/APH-FcpdMJY.js?_nc_x=Ij3Wp8lg5Kz
9909
https://static.xx.fbcdn.net/rsrc.php/v3/yI/r/pPEWqCTW2Ud.js?_nc_x=Ij3Wp8lg5Kz
9746
Uses efficient cache policy on static assets — 0 resources found
Freefacebook.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 162 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
162
Maximum DOM Depth
18
Maximum Child Elements
31
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Freefacebook.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Minimizes main-thread work — 0.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
7.678
Rendering
0.052
Script Evaluation
0.033
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 36 requests • 314 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
36
321185
Script
21
240800
Image
4
26572
Document
1
23558
Stylesheet
7
21727
Other
3
8528
Media
0
0
Font
0
0
Third-party
31
285216
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Eliminate render-blocking resources — Potential savings of 350 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Freefacebook.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static.xx.fbcdn.net/rsrc.php/v3/y4/l/0,cross/ZtwO7u3tI0A.css?_nc_x=Ij3Wp8lg5Kz
4126
230
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/5qNQnR2Vk-N.js?_nc_x=Ij3Wp8lg5Kz
95128
80

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freefacebook.com on mobile screens.
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of freefacebook.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Freefacebook.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that freefacebook.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://freefacebook.com/
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Relaxing the same-origin policy by setting `document.domain` is deprecated, and will be disabled by default. To continue using this feature, please opt-out of origin-keyed agent clusters by sending an `Origin-Agent-Cluster: ?0` header along with the HTTP response for the document and frames. See https://developer.chrome.com/blog/immutable-document-domain/ for more details.
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for freefacebook.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freefacebook.com on mobile screens.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of freefacebook.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freefacebook.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 75
Performance 77
Accessibility 83
Best Practices 75
SEO 82
PWA 60
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://m.facebook.com/
Updated: 16th January, 2023

1.89 seconds
First Contentful Paint (FCP)
74%
15%
11%

0.02 seconds
First Input Delay (FID)
93%
5%
2%

Simulate loading on mobile
77

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for freefacebook.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 3.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://freefacebook.com/
http/1.1
0
135.29899995774
377
0
301
text/html
https://www.facebook.com/
http/1.1
135.6069999747
245.4119999893
428
0
302
text/html
https://m.facebook.com/
h2
245.73699990287
463.7690000236
24072
56222
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yr/l/0,cross/ld63NTxh1pw.css?_nc_x=Ij3Wp8lg5Kz
h2
506.82599982247
531.63199964911
3923
14166
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yS/l/0,cross/F9CrHVuyORe.css?_nc_x=Ij3Wp8lg5Kz
h2
507.15099973604
526.48400003091
8485
37923
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yR/l/0,cross/bm62alViWXI.css?_nc_x=Ij3Wp8lg5Kz
h2
507.55099998787
529.50699999928
9971
36625
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/ya/r/1y8tM4IVve3.js?_nc_x=Ij3Wp8lg5Kz
h2
507.80999986455
528.95099995658
79146
311251
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
h2
573.49799992517
590.99599998444
1708
2385
200
image/svg+xml
Image
https://facebook.com/security/hsts-pixel.gif
h2
573.63400002941
633.69600009173
3873
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3iczx4/yN/l/en_US/SdtDSnQ5Pqo.js?_nc_x=Ij3Wp8lg5Kz
h2
535.08500009775
553.83099988103
52051
186866
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ym/r/QBkA9ZfAK-V.js?_nc_x=Ij3Wp8lg5Kz
h2
555.08399987593
570.89000009
13127
42424
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yX/r/XmO_5adUbuq.js?_nc_x=Ij3Wp8lg5Kz
h2
573.09299986809
590.67999990657
11130
34738
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yi/r/ohs53z_4AL7.js?_nc_x=Ij3Wp8lg5Kz
h2
573.31099966541
588.66499969736
8048
22536
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/cvj8rfO8RgU.png
h2
578.96899990737
592.67699997872
4019
3404
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/Hea_LYynh2s.png
h2
613.92399994656
628.97099973634
66374
65741
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
h2
717.66200009733
737.63999994844
9979
50828
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/_tJ17sGyxOX.js?_nc_x=Ij3Wp8lg5Kz
h2
718.1139998138
736.56799970195
8187
18154
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yQ/r/DWNW_HjAG5A.js?_nc_x=Ij3Wp8lg5Kz
h2
718.65499997512
739.19499991462
18795
60331
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yc/r/2oHddz12uT9.js?_nc_x=Ij3Wp8lg5Kz
h2
721.14999964833
737.2139999643
4081
8848
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3ih-D4/yx/l/en_US/GKILFiHJIh1.js?_nc_x=Ij3Wp8lg5Kz
h2
721.53599979356
738.74099971727
18880
76329
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yb/r/m82IO1HXQRH.js?_nc_x=Ij3Wp8lg5Kz
h2
721.98399994522
738.10900002718
11382
32639
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
h2
722.42800006643
741.51499988511
13705
43510
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iLQG4/yv/l/en_US/Sa1jhi1-Bt9.js?_nc_x=Ij3Wp8lg5Kz
h2
722.92799968272
743.4390000999
11048
39106
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yK/l/en_US/0D75Vw0sOuD.js?_nc_x=Ij3Wp8lg5Kz
h2
723.35299989209
742.39300005138
3980
8771
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yg/r/GaT0-DQJdWD.js?_nc_x=Ij3Wp8lg5Kz
h2
723.83099980652
742.05200001597
863
313
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y9/r/ie38mp0O07P.js?_nc_x=Ij3Wp8lg5Kz
h2
724.35399983078
742.78499977663
11081
25101
200
application/x-javascript
Script
https://m.facebook.com/a/bz?fb_dtsg=NAcO41zZ5smJeN8X2zPh1sA2wNXnUK2HQdSdt39lR2CFemwqsCAZG7Q%3A0%3A0&jazoest=24783&lsd=AVr_zjUL2a8&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=1&__a=AYna6De8ZuK_2d-eRoF2UWN5mHztBYOKRTSPD0_fZbnqzCIavEeblkDDpV59a-gDANfv004uCKk0Yxu2UHngNQpykP4vGphpPC9SbEAptq9EVA&__user=0
h2
819.61499992758
890.30799968168
4434
249
200
application/x-javascript
XHR
https://m.facebook.com/data/manifest/
h2
820.90099994093
869.59199979901
4427
954
200
application/json
Manifest
https://m.facebook.com/a/bz?fb_dtsg=NAcO41zZ5smJeN8X2zPh1sA2wNXnUK2HQdSdt39lR2CFemwqsCAZG7Q%3A0%3A0&jazoest=24783&lsd=AVr_zjUL2a8&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=2&__a=AYna6De8ZuK_2d-eRoF2UWN5mHztBYOKRTSPD0_fZbnqzCIavEeblkDDpV59a-gDANfv004uCKk0Yxu2UHngNQpykP4vGphpPC9SbEAptq9EVA&__user=0
h2
879.8119998537
950.52899979055
4434
249
200
application/x-javascript
XHR
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
881.12600008026
897.11700007319
384
79
200
image/png
Image
https://m.facebook.com/a/bz?fb_dtsg=NAcO41zZ5smJeN8X2zPh1sA2wNXnUK2HQdSdt39lR2CFemwqsCAZG7Q%3A0%3A0&jazoest=24783&lsd=AVr_zjUL2a8&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=3&__a=AYna6De8ZuK_2d-eRoF2UWN5mHztBYOKRTSPD0_fZbnqzCIavEeblkDDpV59a-gDANfv004uCKk0Yxu2UHngNQpykP4vGphpPC9SbEAptq9EVA&__user=0
h2
1886.7869996466
1928.559999913
4451
249
200
application/x-javascript
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Freefacebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Freefacebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Freefacebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Freefacebook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Freefacebook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://m.facebook.com/
219.024
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Freefacebook.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 407 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/ya/r/1y8tM4IVve3.js?_nc_x=Ij3Wp8lg5Kz
79146
https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/Hea_LYynh2s.png
66374
https://static.xx.fbcdn.net/rsrc.php/v3iczx4/yN/l/en_US/SdtDSnQ5Pqo.js?_nc_x=Ij3Wp8lg5Kz
52051
https://m.facebook.com/
24072
https://static.xx.fbcdn.net/rsrc.php/v3ih-D4/yx/l/en_US/GKILFiHJIh1.js?_nc_x=Ij3Wp8lg5Kz
18880
https://static.xx.fbcdn.net/rsrc.php/v3/yQ/r/DWNW_HjAG5A.js?_nc_x=Ij3Wp8lg5Kz
18795
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
13705
https://static.xx.fbcdn.net/rsrc.php/v3/ym/r/QBkA9ZfAK-V.js?_nc_x=Ij3Wp8lg5Kz
13127
https://static.xx.fbcdn.net/rsrc.php/v3/yb/r/m82IO1HXQRH.js?_nc_x=Ij3Wp8lg5Kz
11382
https://static.xx.fbcdn.net/rsrc.php/v3/yX/r/XmO_5adUbuq.js?_nc_x=Ij3Wp8lg5Kz
11130
Uses efficient cache policy on static assets — 0 resources found
Freefacebook.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 196 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
196
Maximum DOM Depth
20
Maximum Child Elements
23
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Freefacebook.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Minimizes main-thread work — 0.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
18.076
Rendering
0.384
Script Evaluation
0.168
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 31 requests • 407 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
31
416843
Script
16
275483
Image
5
76358
Document
1
24072
Stylesheet
3
22379
Other
6
18551
Media
0
0
Font
0
0
Third-party
23
370347
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freefacebook.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.107
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 71 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/ya/r/1y8tM4IVve3.js?_nc_x=Ij3Wp8lg5Kz
79146
40252
https://static.xx.fbcdn.net/rsrc.php/v3iczx4/yN/l/en_US/SdtDSnQ5Pqo.js?_nc_x=Ij3Wp8lg5Kz
52051
32894
Serve images in next-gen formats — Potential savings of 42 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/Hea_LYynh2s.png
65741
42544.4
Avoid serving legacy JavaScript to modern browsers — Potential savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/ya/r/1y8tM4IVve3.js?_nc_x=Ij3Wp8lg5Kz
13671

Metrics

First Contentful Paint — 3.6 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 4.0 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 1,230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Freefacebook.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static.xx.fbcdn.net/rsrc.php/v3/yr/l/0,cross/ld63NTxh1pw.css?_nc_x=Ij3Wp8lg5Kz
3923
780
https://static.xx.fbcdn.net/rsrc.php/v3/yR/l/0,cross/bm62alViWXI.css?_nc_x=Ij3Wp8lg5Kz
9971
150
https://static.xx.fbcdn.net/rsrc.php/v3/ya/r/1y8tM4IVve3.js?_nc_x=Ij3Wp8lg5Kz
79146
300
Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Freefacebook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://freefacebook.com/
630
https://www.facebook.com/
780
https://m.facebook.com/
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
First Contentful Paint (3G) — 7320 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
83

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of freefacebook.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Freefacebook.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-*]` attributes do not match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that freefacebook.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
script-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://freefacebook.com/
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Relaxing the same-origin policy by setting `document.domain` is deprecated, and will be disabled by default. To continue using this feature, please opt-out of origin-keyed agent clusters by sending an `Origin-Agent-Cluster: ?0` header along with the HTTP response for the document and frames. See https://developer.chrome.com/blog/immutable-document-domain/ for more details.
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
ErrorUtils caught an error: Tried to get element with id of "m_login_auto_search_form_contactpoint_hidden_input" but it is not present on the page Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs.
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for freefacebook.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freefacebook.com on mobile screens.
Document uses legible font sizes — 93.3% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
._96qw
6.70%
10px
93.30%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 56% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
44x14
38x14
43x14
44x14
94x14

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
60

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of freefacebook.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of freefacebook.com on mobile screens.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 157.240.241.17
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Facebook, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Domain Admin
Organization: Meta Platforms, Inc.
Country: US
City: Menlo Park
State: CA
Post Code: 94025
Email: domain@fb.com
Phone: +1.6505434800
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
RegistrarSEC, LLC 192.0.66.80
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.facebook.com
Issued By: DigiCert SHA2 High Assurance Server CA
Valid From: 10th January, 2023
Valid To: 21st March, 2023
Subject: CN = *.facebook.com
O = Meta Platforms, Inc.
L = Menlo Park
S = US
Hash: a5a6422f
Issuer: CN = DigiCert SHA2 High Assurance Server CA
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 10705026621578912901250720066705752968
Serial Number (Hex): 080DB68FDB9A1D1264DAAF0089030388
Valid From: 10th January, 2024
Valid To: 21st March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:51:68:FF:90:AF:02:07:75:3C:CC:D9:65:64:62:A2:12:B8:59:72:3B
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/sha2-ha-server-g6.crl

Full Name:
URI:http://crl4.digicert.com/sha2-ha-server-g6.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2HighAssuranceServerCA.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jan 10 04:03:33.681 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:64:AD:56:5A:EB:F1:46:35:17:76:1D:ED:
16:A9:15:BE:52:39:A9:36:69:9C:F7:57:F1:51:4B:3D:
BF:1D:B6:DE:02:20:16:57:35:26:08:4C:A1:64:D8:7F:
61:12:28:A2:53:12:EF:90:6E:2A:A3:E9:95:8D:40:D3:
53:0F:F7:F5:88:B5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jan 10 04:03:33.743 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:30:52:F0:53:F7:CD:7F:65:EB:C9:90:15:
70:C3:5B:66:69:DB:11:11:93:1D:6E:E7:22:3D:3B:63:
9D:EA:72:0B:02:20:76:DF:37:81:4A:5B:A6:01:30:07:
C7:D6:94:21:4D:54:FD:B5:DF:B0:0C:84:C4:E9:E3:2F:
F6:9F:55:95:35:6C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Jan 10 04:03:33.773 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:9E:F2:D6:81:7F:0C:C9:E5:12:BC:68:
E8:77:84:FD:D8:7E:A0:A0:0A:EF:0E:27:F9:73:1A:FE:
AD:94:E1:9B:D5:02:20:43:AC:BF:3C:3B:C7:9C:83:61:
0E:67:53:25:43:03:81:A7:0B:2D:57:EA:CA:2E:72:D3:
30:5D:05:76:73:77:6A
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.facebook.net
DNS:*.fbcdn.net
DNS:*.fbsbx.com
DNS:*.m.facebook.com
DNS:*.messenger.com
DNS:*.xx.fbcdn.net
DNS:*.xy.fbcdn.net
DNS:*.xz.fbcdn.net
DNS:facebook.com
DNS:messenger.com
DNS:*.facebook.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
freefacebook.com. 157.240.241.17 IN 300

NS Records

Host Nameserver Class TTL
freefacebook.com. c.ns.facebook.com. IN 21600
freefacebook.com. a.ns.facebook.com. IN 21600
freefacebook.com. d.ns.facebook.com. IN 21600
freefacebook.com. b.ns.facebook.com. IN 21600

AAAA Records

IP Address Class TTL
2a03:2880:f012:100:face:b00c:0:2 IN 300

SOA Records

Domain Name Primary NS Responsible Email TTL
freefacebook.com. a.ns.facebook.com. dns.facebook.com. 3600

TXT Records

Host Value Class TTL
freefacebook.com. v=spf1 IN 7200

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Cache-Control: private, no-cache, no-store, must-revalidate
Expires: 1st January, 2000
Content-Type: text/html; charset="utf-8"
Date: 14th March, 2023
Pragma: no-cache
content-security-policy: default-src data
report-to: {"max_age":86400,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reporting\/?minimize=0"}],"group":"coep_report"}, {"max_age":259200,"endpoints":[{"url":"https:\/\/www.facebook.com\/ajax\/browser_error_reports\/?device_level=unknown"}]}
cross-origin-embedder-policy-report-only: require-corp;report-to="coep_report"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
cross-origin-opener-policy: same-origin-allow-popups
Vary: Accept-Encoding
Strict-Transport-Security: max-age=15552000; preload
X-FB-Debug: aeYsesIF0T4+shVUiThpQ+IT5YlQPzlH5yorJ4O9AV02/xRfqbdd+avibtkIBUCn7pDBcReGdSA/6/acA9+BEw==
Priority: u=3,i
Transfer-Encoding: chunked
Alt-Svc: h3=":443"; ma=86400
Connection: keep-alive

Whois Lookup

Created: 3rd September, 2015
Changed: 6th June, 2022
Expires: 3rd September, 2023
Registrar: RegistrarSEC, LLC
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: a.ns.facebook.com
b.ns.facebook.com
c.ns.facebook.com
d.ns.facebook.com
Owner Name: Domain Admin
Owner Organization: Meta Platforms, Inc.
Owner Street: 1601 Willow Rd
Owner Post Code: 94025
Owner City: Menlo Park
Owner State: CA
Owner Country: US
Owner Phone: +1.6505434800
Owner Email: domain@fb.com
Admin Name: Domain Admin
Admin Organization: Meta Platforms, Inc.
Admin Street: 1601 Willow Rd
Admin Post Code: 94025
Admin City: Menlo Park
Admin State: CA
Admin Country: US
Admin Phone: +1.6505434800
Admin Email: domain@fb.com
Tech Name: Domain Admin
Tech Organization: Meta Platforms, Inc.
Tech Street: 1601 Willow Rd
Tech Post Code: 94025
Tech City: Menlo Park
Tech State: CA
Tech Country: US
Tech Phone: +1.6505434800
Tech Email: domain@fb.com
Full Whois: Domain Name: FREEFACEBOOK.COM
Registry Domain ID: 1957313737_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrarsec.com
Registrar URL: https://www.registrarsec.com
Updated Date: 2022-06-06T09:00:11Z
Creation Date: 2015-09-03T18:28:07Z
Registrar Registration Expiration Date: 2023-09-03T18:28:07Z
Registrar: RegistrarSEC, LLC
Registrar IANA ID: 2475
Registrar Abuse Contact Email: abusecomplaints@registrarsec.com
Registrar Abuse Contact Phone: +1.6503087004
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: Domain Admin
Registrant Organization: Meta Platforms, Inc.
Registrant Street: 1601 Willow Rd
Registrant City: Menlo Park
Registrant State/Province: CA
Registrant Postal Code: 94025
Registrant Country: US
Registrant Phone: +1.6505434800
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: domain@fb.com
Registry Admin ID:
Admin Name: Domain Admin
Admin Organization: Meta Platforms, Inc.
Admin Street: 1601 Willow Rd
Admin City: Menlo Park
Admin State/Province: CA
Admin Postal Code: 94025
Admin Country: US
Admin Phone: +1.6505434800
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: domain@fb.com
Registry Tech ID:
Tech Name: Domain Admin
Tech Organization: Meta Platforms, Inc.
Tech Street: 1601 Willow Rd
Tech City: Menlo Park
Tech State/Province: CA
Tech Postal Code: 94025
Tech Country: US
Tech Phone: +1.6505434800
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: domain@fb.com
Name Server: D.NS.FACEBOOK.COM
Name Server: A.NS.FACEBOOK.COM
Name Server: C.NS.FACEBOOK.COM
Name Server: B.NS.FACEBOOK.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-14T04:29:25Z <<<

Search results obtained from the RegistrarSEC, LLC WHOIS database are
provided by RegistrarSEC, LLC for information purposes only, to assist
users in obtaining information concerning a domain name registration record.
The information contained therein is provided on an "as is" and "as available"
basis and RegistrarSEC, LLC does not guarantee the accuracy or completeness
of any information provided through the WHOIS database. By submitting a WHOIS query,
you agree to the following: (1) that you will use any information provided through
the WHOIS only for lawful purposes; (2) that you will comply with all ICANN rules
and regulations governing use of the WHOIS; (3) that you will not use any information
provided through the WHOIS to enable, or otherwise cause the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail (i.e., spam); or
(4) that you will not use the WHOIS to enable or otherwise utilize high volume,
automated, electronic processes that apply to or attach to RegistrarSEC, LLC or
its systems. RegistrarSEC, LLC reserves the right to modify these terms
at any time and to take any other appropriate actions, including but not limited to
restricting any access that violates these terms and conditions. By submitting this
query, you acknowledge and agree to abide by the foregoing terms, conditions and policies.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
a.ns.facebook.com 129.134.30.12
b.ns.facebook.com 129.134.31.12
c.ns.facebook.com 185.89.218.12
d.ns.facebook.com 185.89.219.12
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$780 USD 1/5
$713 USD 1/5
$243 USD 1/5
$595 USD 1/5
$12,245 USD 3/5