thefacebook.com

thefacebook.com is SSL secured

Free website and domain report on thefacebook.com

Last Updated: 3rd January, 2023 Update Now
Overview

Snoop Summary for thefacebook.com

This is a free and comprehensive report about thefacebook.com. The domain thefacebook.com is currently hosted on a server located in United States with the IP address 157.240.241.17, where USD is the local currency and the local language is English. Our records indicate that thefacebook.com is owned/operated by Facebook, Inc.. Thefacebook.com is expected to earn an estimated $17 USD per day from advertising revenue. The sale of thefacebook.com would possibly be worth $12,245 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Thefacebook.com receives an estimated 5,881 unique visitors every day - a huge amount of traffic! This report was last updated 3rd January, 2023.

About thefacebook.com

Site Preview: thefacebook.com thefacebook.com
Title:
Description: Log into Facebook to start sharing and connecting with your friends, family, and people you know.
Keywords and Tags: social networking
Related Terms:
Fav Icon:
Age: Over 20 years old
Domain Created: 11th January, 2004
Domain Updated: 18th February, 2022
Domain Expires: 23rd December, 2023
Review

Snoop Score

3/5 (Great!)

Valuation

$12,245 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 89,241
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 5,881
Monthly Visitors: 178,999
Yearly Visitors: 2,146,565
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $17 USD
Monthly Revenue: $510 USD
Yearly Revenue: $6,118 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: thefacebook.com 15
Domain Name: thefacebook 11
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.57 seconds
Load Time Comparison: Faster than 61% of sites

PageSpeed Insights

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

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

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

Simulate loading on desktop
97

Performance

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

Metrics

Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 1.0 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 — 1.0 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.
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://thefacebook.com/
http/1.1
0
79.704000032507
247
0
301
text/plain
https://thefacebook.com/
http/1.1
80.619000014849
180.45600003097
434
0
302
text/html
https://www.facebook.com/
h2
180.85400003474
404.35300010722
23486
62838
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yM/l/0,cross/RGfMDLpn3Oz.css?_nc_x=Ij3Wp8lg5Kz
h2
448.59000004362
483.31200005487
5432
19868
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yV/l/0,cross/KxGJ10xTR_J.css?_nc_x=Ij3Wp8lg5Kz
h2
449.29700007197
482.07100003492
2056
3608
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yQ/l/0,cross/AsMiSWPE7CQ.css?_nc_x=Ij3Wp8lg5Kz
h2
449.44900006521
464.28499999456
3537
11002
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yI/l/0,cross/brcQZHqBO86.css?_nc_x=Ij3Wp8lg5Kz
h2
449.5740000857
482.85900009796
8062
32904
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yr/l/0,cross/u4xvA0Tw-4L.css?_nc_x=Ij3Wp8lg5Kz
h2
449.84000001568
482.47400007676
1102
1225
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
h2
450.44500008225
471.12000000197
95166
370589
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
h2
542.24700003397
576.48300006986
1708
2385
200
image/svg+xml
Image
https://facebook.com/security/hsts-pixel.gif
h2
542.45200008154
707.39900006447
3866
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/y9/r/R-poEPeDR18.js?_nc_x=Ij3Wp8lg5Kz
h2
488.1320000859
520.95900010318
3885
9443
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yu/r/1fIb2S0KdFD.js?_nc_x=Ij3Wp8lg5Kz
h2
503.47100000363
536.89700004179
7412
21015
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/y3/l/en_US/Fsng_uO7FZe.js?_nc_x=Ij3Wp8lg5Kz
h2
541.62300005555
577.12800009176
16758
62279
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y8/r/kgCswNiKScM.js?_nc_x=Ij3Wp8lg5Kz
h2
541.83200001717
575.32200007699
1090
735
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yo/r/CxsU34-o9QX.js?_nc_x=Ij3Wp8lg5Kz
h2
542.03400004189
553.65200003143
11825
35694
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yU/r/O7nelmd9XSI.png
h2
551.34800006635
583.22600007523
723
95
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/kNYkizqJr9j.png
h2
553.22100000922
564.90900006611
20264
19631
200
image/png
Image
data
623.55500005651
623.74100007582
0
0
200
text/css
Stylesheet
data
623.91100008972
624.0500001004
0
78
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/p0bcnVbl1Lr.js?_nc_x=Ij3Wp8lg5Kz
h2
665.15000001527
698.32200009841
11982
35053
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/mgxJrPv-D2y.js?_nc_x=Ij3Wp8lg5Kz
h2
670.07400002331
703.86500004679
7855
21446
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/j_uHdvkyoIZ.js?_nc_x=Ij3Wp8lg5Kz
h2
670.40900001302
703.43300001696
4634
9840
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/M08arqdo_nN.js?_nc_x=Ij3Wp8lg5Kz
h2
671.16500006523
704.25599999726
1440
1622
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/lS9_2HUikEH.js?_nc_x=Ij3Wp8lg5Kz
h2
676.63200001698
713.00200000405
10309
30283
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/APH-FcpdMJY.js?_nc_x=Ij3Wp8lg5Kz
h2
676.87900003511
711.38400002383
9892
33047
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
h2
677.01800004579
713.37900008075
13719
43510
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/_tJ17sGyxOX.js?_nc_x=Ij3Wp8lg5Kz
h2
677.14500008151
714.60900001694
8218
18154
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
h2
677.26700007915
712.22000010312
9976
50828
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yZ/r/QhPwpTphYGn.js?_nc_x=Ij3Wp8lg5Kz
h2
677.41000000387
711.83800010476
8077
26127
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/y_/l/en_US/LHUxA4o6J25.js?_nc_x=Ij3Wp8lg5Kz
h2
677.72600008175
713.84100010619
14101
43610
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yF/r/PtmfxLVwAb7.js?_nc_x=Ij3Wp8lg5Kz
h2
677.92700009886
709.34400008991
966
285
200
application/x-javascript
Script
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU29zEdEc8uwdK0lW4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwnU1oU884y0lW0ny0RE2Jw8W0iW0lK3qaw4kwbS1Lw4Cw&__hs=19360.BP%3ADEFAULT.2.0.0.0.0&__hsi=7184248585238887380&__req=1&__rev=1006774989&__s=wuagz6%3Ad8l1dq%3Amydn57&__spin_b=trunk&__spin_r=1006774989&__spin_t=1672713222&__user=0&dpr=1&jazoest=21016&lsd=AVoow3jLpDo
h2
804.40100003034
950.43500000611
4069
0
200
text/html
XHR
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU29zEdEc8uwdK0lW4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwnU1oU884y0lW0ny0RE2Jw8W0iW0lK3qaw4kwbS1Lw4Cw&__hs=19360.BP%3ADEFAULT.2.0.0.0.0&__hsi=7184248585238887380&__req=2&__rev=1006774989&__s=wuagz6%3Ad8l1dq%3Amydn57&__spin_b=trunk&__spin_r=1006774989&__spin_t=1672713222&__user=0&dpr=1&jazoest=21016&lsd=AVoow3jLpDo
h2
1813.4580000769
1915.9260001034
4069
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. Thefacebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Thefacebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Thefacebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Thefacebook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Thefacebook.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/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
95166
50121
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 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://www.facebook.com/
224.492
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Thefacebook.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/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
13806
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 309 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/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
95166
https://www.facebook.com/
23486
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/kNYkizqJr9j.png
20264
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/y3/l/en_US/Fsng_uO7FZe.js?_nc_x=Ij3Wp8lg5Kz
16758
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/y_/l/en_US/LHUxA4o6J25.js?_nc_x=Ij3Wp8lg5Kz
14101
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
11982
https://static.xx.fbcdn.net/rsrc.php/v3/yo/r/CxsU34-o9QX.js?_nc_x=Ij3Wp8lg5Kz
11825
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/lS9_2HUikEH.js?_nc_x=Ij3Wp8lg5Kz
10309
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
9976
Uses efficient cache policy on static assets — 0 resources found
Thefacebook.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 — 159 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
159
Maximum DOM Depth
18
Maximum Child Elements
31
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Thefacebook.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.962
Rendering
0.073
Script Evaluation
0.035
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 — 32 requests • 309 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
32
316360
Script
18
237305
Image
4
26561
Document
1
23486
Stylesheet
5
20189
Other
4
8819
Media
0
0
Font
0
0
Third-party
26
280189
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.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.

Audits

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

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. Thefacebook.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/yM/l/0,cross/RGfMDLpn3Oz.css?_nc_x=Ij3Wp8lg5Kz
5432
230
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
95166
80
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Thefacebook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://thefacebook.com/
190
https://thefacebook.com/
150
https://www.facebook.com/
0

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 thefacebook.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 thefacebook.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"]`
Thefacebook.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 thefacebook.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://thefacebook.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 thefacebook.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 thefacebook.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 thefacebook.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 thefacebook.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) 74
Performance 70
Accessibility 83
Best Practices 75
SEO 82
PWA 60
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://m.facebook.com/
Updated: 3rd January, 2023

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

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

Simulate loading on mobile
70

Performance

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

Metrics

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://thefacebook.com/
http/1.1
0
47.570000053383
244
0
301
text/plain
https://thefacebook.com/
http/1.1
48.032999970019
116.90700007603
448
0
302
text/html
https://www.facebook.com/
http/1.1
117.47900000773
143.50900007412
411
0
302
text/html
https://m.facebook.com/
h2
143.91800004523
704.74900002591
24231
56517
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yH/l/0,cross/8pbaT5LFcxq.css?_nc_x=Ij3Wp8lg5Kz
h2
768.76800006721
804.4050000608
3980
14472
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yn/l/0,cross/pplJS07odi_.css?_nc_x=Ij3Wp8lg5Kz
h2
769.77700006682
803.3089999808
8812
39908
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yH/l/0,cross/XRk-3W7cWsW.css?_nc_x=Ij3Wp8lg5Kz
h2
770.0130000012
806.22500006575
14372
57184
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
h2
770.62700001989
805.46100006904
79168
311433
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
h2
911.40800004359
919.07200007699
1708
2385
200
image/svg+xml
Image
https://facebook.com/security/hsts-pixel.gif
h2
911.62400005851
975.92900006566
3856
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
h2
829.79800004978
838.89500005171
50935
181945
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/tttf5FDK7WA.js?_nc_x=Ij3Wp8lg5Kz
h2
880.42800000403
888.22199997958
13796
44468
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yu/r/4z8at6z2jaS.js?_nc_x=Ij3Wp8lg5Kz
h2
880.88200008497
887.60700006969
11424
36060
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/LqXI6W_bsOb.js?_nc_x=Ij3Wp8lg5Kz
h2
911.08800005168
918.57500001788
9215
26709
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/cvj8rfO8RgU.png
h2
922.81100002583
930.79400004353
4036
3404
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yi/r/HoeIqiP3dNO.png
h2
1029.6060000546
1036.5920000477
81651
81018
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
h2
1159.9660000065
1170.0780000538
9979
50828
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/_tJ17sGyxOX.js?_nc_x=Ij3Wp8lg5Kz
h2
1160.6460000621
1167.068000068
8187
18154
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yT/r/OQ2NlcQEZ4F.js?_nc_x=Ij3Wp8lg5Kz
h2
1161.3239999861
1175.3980000503
9064
27129
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iL7o4/yw/l/en_US/CJAv6e1f-aD.js?_nc_x=Ij3Wp8lg5Kz
h2
1162.2579999967
1175.9709999897
13423
39701
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/KKlvRURRLk8.js?_nc_x=Ij3Wp8lg5Kz
h2
1166.4280000841
1178.2910000766
6848
17749
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3ih-D4/yM/l/en_US/yaw05i6HDSf.js?_nc_x=Ij3Wp8lg5Kz
h2
1172.3900000798
1196.1790000787
19177
78246
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
h2
1172.928999993
1197.2930000629
13722
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
1173.1119999895
1189.1509999987
11048
39106
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yn/r/lNCIXQG6fuL.js?_nc_x=Ij3Wp8lg5Kz
h2
1173.2779999729
1194.4770000409
8803
23738
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yK/l/en_US/0D75Vw0sOuD.js?_nc_x=Ij3Wp8lg5Kz
h2
1173.4479999868
1195.0010000728
3963
8771
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yg/r/GaT0-DQJdWD.js?_nc_x=Ij3Wp8lg5Kz
h2
1173.758000019
1195.3549999744
863
313
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y9/r/ie38mp0O07P.js?_nc_x=Ij3Wp8lg5Kz
h2
1175.1250000671
1197.6710000308
11098
25101
200
application/x-javascript
Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
1346.3650000049
1351.5619999962
384
79
200
image/png
Image
https://m.facebook.com/a/bz?fb_dtsg=NAcNvsD9DMDu3kqPIJQpIw0QeWIsBLblcshEjr2RYvyLIyfoNbvRD-A%3A0%3A0&jazoest=25060&lsd=AVp50Gn5RyU&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=1&__a=AYkkohzsF9UWiukT26BeWC9KJ6IAwNIUGs1W9nk6MeV8yQAUO5CsASV00MyMrQChRInCuMFWaINI87jUZ-7mqks-VnkkhJ94kPY-HRUty-PjqQ&__user=0
h2
1409.3550000107
1442.4610000569
4451
249
200
application/x-javascript
XHR
https://m.facebook.com/a/bz?fb_dtsg=NAcNvsD9DMDu3kqPIJQpIw0QeWIsBLblcshEjr2RYvyLIyfoNbvRD-A%3A0%3A0&jazoest=25060&lsd=AVp50Gn5RyU&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=2&__a=AYkkohzsF9UWiukT26BeWC9KJ6IAwNIUGs1W9nk6MeV8yQAUO5CsASV00MyMrQChRInCuMFWaINI87jUZ-7mqks-VnkkhJ94kPY-HRUty-PjqQ&__user=0
h2
1454.9380000681
1478.1700000167
4434
249
200
application/x-javascript
XHR
https://m.facebook.com/data/manifest/
h2
1455.1600000123
1485.9880000586
4427
954
200
application/json
Manifest
https://m.facebook.com/a/bz?fb_dtsg=NAcNvsD9DMDu3kqPIJQpIw0QeWIsBLblcshEjr2RYvyLIyfoNbvRD-A%3A0%3A0&jazoest=25060&lsd=AVp50Gn5RyU&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=3&__a=AYkkohzsF9UWiukT26BeWC9KJ6IAwNIUGs1W9nk6MeV8yQAUO5CsASV00MyMrQChRInCuMFWaINI87jUZ-7mqks-VnkkhJ94kPY-HRUty-PjqQ&__user=0
h2
2401.622000034
2437.1500000125
4434
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. Thefacebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Thefacebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Thefacebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Thefacebook.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 13 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Thefacebook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yH/l/0,cross/XRk-3W7cWsW.css?_nc_x=Ij3Wp8lg5Kz
14372
13050
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 54 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/yi/r/HoeIqiP3dNO.png
81018
55594.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 560 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/
561.823
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Thefacebook.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/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
13666
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 432 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/yi/r/HoeIqiP3dNO.png
81651
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
79168
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
50935
https://m.facebook.com/
24231
https://static.xx.fbcdn.net/rsrc.php/v3ih-D4/yM/l/en_US/yaw05i6HDSf.js?_nc_x=Ij3Wp8lg5Kz
19177
https://static.xx.fbcdn.net/rsrc.php/v3/yH/l/0,cross/XRk-3W7cWsW.css?_nc_x=Ij3Wp8lg5Kz
14372
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/tttf5FDK7WA.js?_nc_x=Ij3Wp8lg5Kz
13796
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
13722
https://static.xx.fbcdn.net/rsrc.php/v3iL7o4/yw/l/en_US/CJAv6e1f-aD.js?_nc_x=Ij3Wp8lg5Kz
13423
https://static.xx.fbcdn.net/rsrc.php/v3/yu/r/4z8at6z2jaS.js?_nc_x=Ij3Wp8lg5Kz
11424
Uses efficient cache policy on static assets — 0 resources found
Thefacebook.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. Thefacebook.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 — 0.0 s
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.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
58.54
0.34
0
Minimizes main-thread work — 0.1 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
57.792
Rendering
0.408
Script Evaluation
0.34
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 — 33 requests • 432 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
33
442592
Script
17
280713
Image
5
91635
Stylesheet
3
27164
Document
1
24231
Other
7
18849
Media
0
0
Font
0
0
Third-party
24
395656
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 thefacebook.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

Time to Interactive — 4.2 s
The time taken for the page to become fully interactive.
Speed Index — 4.2 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

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/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
79168
40260
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
50935
32077

Metrics

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,380 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Thefacebook.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/yH/l/0,cross/8pbaT5LFcxq.css?_nc_x=Ij3Wp8lg5Kz
3980
780
https://static.xx.fbcdn.net/rsrc.php/v3/yH/l/0,cross/XRk-3W7cWsW.css?_nc_x=Ij3Wp8lg5Kz
14372
150
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
79168
450
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Thefacebook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://thefacebook.com/
630
https://thefacebook.com/
480
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) — 8250 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 thefacebook.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"]`
Thefacebook.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 thefacebook.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://thefacebook.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 thefacebook.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 thefacebook.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 thefacebook.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 thefacebook.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 Administrator
Organization: Facebook, 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
MarkMonitor, Inc. 172.64.148.104
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 88/100
WOT Child Safety: 67/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.facebook.com
Issued By: DigiCert SHA2 High Assurance Server CA
Valid From: 26th May, 2021
Valid To: 24th August, 2021
Subject: CN = *.facebook.com
O = Facebook, Inc.
L = Menlo Park
S = US
Hash: 1a9ad8e0
Issuer: CN = DigiCert SHA2 High Assurance Server CA
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 11649360478121669874897127695171127468
Serial Number (Hex): 08C395D0D50FB6D8349A9DD1415F08AC
Valid From: 26th May, 2024
Valid To: 24th August, 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 : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : May 26 13:06:03.898 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A1:63:A6:13:2A:77:9A:A6:B6:9D:F0:
C1:81:AF:08:59:9E:D9:78:F1:5E:9E:C1:07:C9:B0:71:
94:D1:D8:C3:50:02:21:00:AB:B6:13:23:88:29:96:41:
A6:45:14:73:F1:8D:D2:5F:0D:94:07:0A:64:1F:C6:B9:
19:E3:88:8A:24:88:64:7D
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : May 26 13:06:03.875 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EE:A7:76:3F:D0:A2:26:A4:21:C3:98:
0A:F2:F8:64:63:BF:30:96:38:6D:08:5B:7E:66:E5:EF:
C9:D5:59:7A:9C:02:21:00:F1:26:07:19:D3:9A:61:ED:
F7:83:B1:C1:94:65:B9:2E:2E:12:CE:D3:8D:C2:F2:AD:
69:E6:48:C5:C4:F0:40:A1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:C0:95:EE:8D:72:64:0F:92:E3:C3:B9:1B:C7:12:A3:
69:6A:09:7B:4B:6A:1A:14:38:E6:47:B2:CB:ED:C5:F9
Timestamp : May 26 13:06:03.923 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EF:8E:BC:F2:1D:4A:39:F1:41:74:BC:
68:E2:9F:0D:31:35:E8:64:6F:06:8D:12:94:B7:E7:E0:
95:73:C9:6D:86:02:21:00:CC:C9:BD:45:F4:01:3B:16:
1F:FE:E0:C5:15:80:82:E1:D1:15:C4:D1:3C:2B:CE:52:
B5:CF:58:36:6C:0B:5D:38
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
thefacebook.com. 31.13.66.4 IN 300

NS Records

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

AAAA Records

IP Address Class TTL
2a03:2880:f003:c07:face:b00c:0:2 IN 300

CAA Records

Domain Flags Tag Class TTL
mailto:ssl@fb.com 0 iodef IN 3600
digicert.com 0 issue IN 3600
digicert.com 0 issuewild IN 3600

MX Records

Priority Host Server Class TTL
10 thefacebook.com. mxb-00082601.gslb.pphosted.com. IN 600
10 thefacebook.com. mxa-00082601.gslb.pphosted.com. IN 600

SOA Records

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

TXT Records

Host Value Class TTL
thefacebook.com. zwCHCnHDnIjisT0O1jm0J96963VBuapt4jNYzBJbk3k+4/UepE+vEY8dG5Ekox2Wftfuu9L6+PyDSnNJiunE7g== IN 3600
thefacebook.com. MS=ms90237461 IN 3600
thefacebook.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: 11th July, 2021
Vary: Accept-Encoding
Set-Cookie: *
x-fb-rlafr: 0
Pragma: no-cache
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
content-security-policy: default-src * data
X-Frame-Options: DENY
Strict-Transport-Security: max-age=15552000; preload
X-FB-Debug: M9m0/kFz1V+q5JcFt34yV2C7uZw8IvajL8nDm9nHXbqeENMfjjFcbWz2WtlcRElMPa1SNhdCll6YMGLg7o4Tmw==
Transfer-Encoding: chunked
Alt-Svc: h3-29=":443"; ma=3600,h3-27=":443"; ma=3600
Connection: keep-alive

Whois Lookup

Created: 11th January, 2004
Changed: 18th February, 2022
Expires: 23rd December, 2023
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
serverUpdateProhibited
serverTransferProhibited
serverDeleteProhibited
Nameservers: a.ns.facebook.com
b.ns.facebook.com
c.ns.facebook.com
d.ns.facebook.com
Owner Name: Domain Administrator
Owner Organization: Facebook, Inc.
Owner Street: 1601 Willow Road,
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 Administrator
Admin Organization: Facebook, Inc.
Admin Street: 1601 Willow Road,
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 Administrator
Tech Organization: Facebook, Inc.
Tech Street: 1601 Willow Road,
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: thefacebook.com
Registry Domain ID: 109702479_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2022-02-18T18:13:19+0000
Creation Date: 2004-01-11T17:52:30+0000
Registrar Registration Expiration Date: 2023-12-23T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895770
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)
Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)
Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: Facebook, Inc.
Registrant Street: 1601 Willow Road,
Registrant City: Menlo Park
Registrant State/Province: CA
Registrant Postal Code: 94025
Registrant Country: US
Registrant Phone: +1.6505434800
Registrant Phone Ext:
Registrant Fax: +1.6505434800
Registrant Fax Ext:
Registrant Email: domain@fb.com
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: Facebook, Inc.
Admin Street: 1601 Willow Road,
Admin City: Menlo Park
Admin State/Province: CA
Admin Postal Code: 94025
Admin Country: US
Admin Phone: +1.6505434800
Admin Phone Ext:
Admin Fax: +1.6505434800
Admin Fax Ext:
Admin Email: domain@fb.com
Registry Tech ID:
Tech Name: Domain Administrator
Tech Organization: Facebook, Inc.
Tech Street: 1601 Willow Road,
Tech City: Menlo Park
Tech State/Province: CA
Tech Postal Code: 94025
Tech Country: US
Tech Phone: +1.6505434800
Tech Phone Ext:
Tech Fax: +1.6505434800
Tech Fax Ext:
Tech Email: domain@fb.com
Name Server: d.ns.facebook.com
Name Server: c.ns.facebook.com
Name Server: a.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-01-03T02:33:38+0000 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

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

Domain Valuation Snoop Score
$942 USD
0/5
0/5
0/5
$222,064,910 USD 5/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$185 USD

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