facbook.com

facbook.com is SSL secured

Free website and domain report on facbook.com

Last Updated: 13th September, 2023 Update Now
Overview

Snoop Summary for facbook.com

This is a free and comprehensive report about facbook.com. The domain facbook.com is currently hosted on a server located in Ireland with the IP address 31.13.71.1, where the local currency is EUR and English is the local language. Our records indicate that facbook.com is owned/operated by Facebook, Inc.. Facbook.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If facbook.com was to be sold it would possibly be worth $763 USD (based on the daily revenue potential of the website over a 24 month period). Facbook.com receives an estimated 362 unique visitors every day - a decent amount of traffic! This report was last updated 13th September, 2023.

About facbook.com

Site Preview: facbook.com facbook.com
Title: Facebook - Log In or Sign Up
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: social networking
Related Terms: 24 energa log, aqu log..., bankia log in, bicupid com log in, cbs log, crontab log, edsby log in, fuegodevida com log in, kinnser log in, moodle log in
Fav Icon:
Age: Over 19 years old
Domain Created: 17th March, 2005
Domain Updated: 15th February, 2020
Domain Expires: 17th March, 2022
Review

Snoop Score

2/5

Valuation

$763 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,532,170
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: 362
Monthly Visitors: 11,018
Yearly Visitors: 132,130
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $31 USD
Yearly Revenue: $377 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: facbook.com 11
Domain Name: facbook 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.50 seconds
Load Time Comparison: Faster than 96% of sites

PageSpeed Insights

Avg. (All Categories) 77
Performance 96
Accessibility 98
Best Practices 80
SEO 73
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.facebook.com/
Updated: 16th March, 2021

4.22 seconds
First Contentful Paint (FCP)
3%
53%
44%

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

Simulate loading on desktop
96

Performance

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

Metrics

Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.0 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive facbook.com as laggy when the latency is higher than 0.05 seconds.
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://facbook.com/
http/1.1
0
103.33500000706
410
0
301
text/html
https://www.facebook.com/
h2
104.0639999992
217.69099999801
33353
176816
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/ys/l/0,cross/Bl_SsT3sZeo.css?_nc_x=Ij3Wp8lg5Kz
h2
269.19600000838
324.49199999974
119335
457664
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yG/l/0,cross/XYDswbP7afj.css?_nc_x=Ij3Wp8lg5Kz
h2
269.38599999994
292.47800000303
25680
90969
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/ya/l/0,cross/5CpfRHI1xVm.css?_nc_x=Ij3Wp8lg5Kz
h2
269.61499999743
335.82999999635
83867
300550
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/ye/l/0,cross/YWoynSiqBQP.css?_nc_x=Ij3Wp8lg5Kz
h2
269.82200000202
287.56100000464
7505
33056
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yN/l/0,cross/EZ-N_MgNavy.css?_nc_x=Ij3Wp8lg5Kz
h2
270.10000000882
286.78100000252
1143
2131
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/y6/l/0,cross/iWbQtMrJW8n.css?_nc_x=Ij3Wp8lg5Kz
h2
270.3909999982
286.37000000163
1095
1595
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yH/r/COFZ7ITuwSz.js?_nc_x=Ij3Wp8lg5Kz
h2
270.61000000685
327.00400000613
72959
274055
200
application/x-javascript
Script
https://facebook.com/security/hsts-pixel.gif
h2
428.13500000921
471.59400000237
1756
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/ys/r/fppQBnAJG1U.js?_nc_x=Ij3Wp8lg5Kz
h2
356.79499999969
374.58299999707
24449
79203
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y1/r/BnlqXcznuVX.js?_nc_x=Ij3Wp8lg5Kz
h2
357.70000000775
375.19600000815
4451
11897
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/yO/l/en_US/Gs-yw4wPDe5.js?_nc_x=Ij3Wp8lg5Kz
h2
427.68100000103
444.72800000221
27340
99898
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ys/r/fnvypMQ2hR1.js?_nc_x=Ij3Wp8lg5Kz
h2
427.926999997
456.30900000106
5893
16312
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yq/r/r8O5EwDQ2JH.png
h2
476.7700000084
490.50500000885
5319
4699
200
image/png
Image
data
543.08499999752
543.20300000836
0
74
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3ipVm4/yA/l/en_US/0nd0ZGjExb5.js?_nc_x=Ij3Wp8lg5Kz
h2
601.01900000882
619.16800000472
34620
132082
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/gM5naJOXDpu.js?_nc_x=Ij3Wp8lg5Kz
h2
602.12999999931
615.73400000634
5030
13051
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iYXl4/yn/l/en_US/rAlkD6t_tBd.js?_nc_x=Ij3Wp8lg5Kz
h2
603.74600000796
627.17500000144
25919
89231
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/HwtZ3oCtkLT.js?_nc_x=Ij3Wp8lg5Kz
h2
607.11100000481
645.52400000684
2782
5571
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yZ/r/zCLM46UvifL.js?_nc_x=Ij3Wp8lg5Kz
h2
607.99200000474
628.66600000416
17040
56066
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yw/r/j331qpFvWav.js?_nc_x=Ij3Wp8lg5Kz
h2
609.21999999846
628.27200000174
870
273
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iPwL4/yp/l/en_US/38R4CWUkqUZ.js?_nc_x=Ij3Wp8lg5Kz
h2
610.44299999776
629.24999999814
6122
17049
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yl/r/_EKTpNjVgmf.js?_nc_x=Ij3Wp8lg5Kz
h2
611.5989999962
648.6969999969
46734
156876
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/PaDDimUMWXJ.js?_nc_x=Ij3Wp8lg5Kz
h2
612.81500000041
629.76199999684
4419
16562
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/yk/l/en_US/6KyLtGqXAOA.js?_nc_x=Ij3Wp8lg5Kz
h2
615.62199999753
631.13999999769
13900
41103
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/JopZtdti8dq.js?_nc_x=Ij3Wp8lg5Kz
h2
616.58100000932
630.59200000134
2962
7270
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y4/r/-PAXP-deijE.gif
h2
690.44000000576
704.27299999574
661
43
200
image/gif
Image
https://www.facebook.com/ajax/bz?__a=1&__beoa=0&__bhv=1&__ccg=EXCELLENT&__comet_req=0&__csr=&__dyn=7xe6Fo4OQ1PyWwHBWo5O12wAxu13wqovzEdEc8uw9-3K4o1j8hwem0nCq1ewcG0KEswaq0yE7i0n2US1kyE1oU884y0Mo2swdK0D83mwaS0zE&__hsi=6940322836778111211-0&__pc=PHASED%3ADEFAULT&__req=1&__rev=1003457016&__s=vqjfo0%3Ag0omgp%3Ax5n1ui&__spin_b=trunk&__spin_r=1003457016&__spin_t=1615919833&__user=0&dpr=1&jazoest=2966&lsd=AVqK4xKtUZY
h2
1709.0380000009
1775.4589999968
1672
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.
Start Time (Ms) End Time (Ms)
288.421
2692.708
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Facbook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facbook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facbook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facbook.com should consider minifying JS files.
Remove unused JavaScript — Potential savings of 146 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/yl/r/_EKTpNjVgmf.js?_nc_x=Ij3Wp8lg5Kz
46734
45413
https://static.xx.fbcdn.net/rsrc.php/v3/yH/r/COFZ7ITuwSz.js?_nc_x=Ij3Wp8lg5Kz
72959
33519
https://static.xx.fbcdn.net/rsrc.php/v3ipVm4/yA/l/en_US/0nd0ZGjExb5.js?_nc_x=Ij3Wp8lg5Kz
34620
26625
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/yO/l/en_US/Gs-yw4wPDe5.js?_nc_x=Ij3Wp8lg5Kz
27340
23243
https://static.xx.fbcdn.net/rsrc.php/v3iYXl4/yn/l/en_US/rAlkD6t_tBd.js?_nc_x=Ij3Wp8lg5Kz
25919
21153
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 110 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/
114.622
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Facbook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://facbook.com/
190
https://www.facebook.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facbook.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 7 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/yH/r/COFZ7ITuwSz.js?_nc_x=Ij3Wp8lg5Kz
7311
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 564 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/ys/l/0,cross/Bl_SsT3sZeo.css?_nc_x=Ij3Wp8lg5Kz
119335
https://static.xx.fbcdn.net/rsrc.php/v3/ya/l/0,cross/5CpfRHI1xVm.css?_nc_x=Ij3Wp8lg5Kz
83867
https://static.xx.fbcdn.net/rsrc.php/v3/yH/r/COFZ7ITuwSz.js?_nc_x=Ij3Wp8lg5Kz
72959
https://static.xx.fbcdn.net/rsrc.php/v3/yl/r/_EKTpNjVgmf.js?_nc_x=Ij3Wp8lg5Kz
46734
https://static.xx.fbcdn.net/rsrc.php/v3ipVm4/yA/l/en_US/0nd0ZGjExb5.js?_nc_x=Ij3Wp8lg5Kz
34620
https://www.facebook.com/
33353
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/yO/l/en_US/Gs-yw4wPDe5.js?_nc_x=Ij3Wp8lg5Kz
27340
https://static.xx.fbcdn.net/rsrc.php/v3iYXl4/yn/l/en_US/rAlkD6t_tBd.js?_nc_x=Ij3Wp8lg5Kz
25919
https://static.xx.fbcdn.net/rsrc.php/v3/yG/l/0,cross/XYDswbP7afj.css?_nc_x=Ij3Wp8lg5Kz
25680
https://static.xx.fbcdn.net/rsrc.php/v3/ys/r/fppQBnAJG1U.js?_nc_x=Ij3Wp8lg5Kz
24449
Uses efficient cache policy on static assets — 0 resources found
Facbook.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 — 219 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
219
Maximum DOM Depth
15
Maximum Child Elements
34
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. Facbook.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
2697.886
0.044
0
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 — 28 requests • 564 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
28
577286
Script
16
295490
Stylesheet
6
238625
Document
1
33353
Image
3
7736
Other
2
2082
Media
0
0
Font
0
0
Third-party
25
540505
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
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

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.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 510 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Facbook.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/ys/l/0,cross/Bl_SsT3sZeo.css?_nc_x=Ij3Wp8lg5Kz
119335
350
https://static.xx.fbcdn.net/rsrc.php/v3/ya/l/0,cross/5CpfRHI1xVm.css?_nc_x=Ij3Wp8lg5Kz
83867
80
https://static.xx.fbcdn.net/rsrc.php/v3/yH/r/COFZ7ITuwSz.js?_nc_x=Ij3Wp8lg5Kz
72959
80
Remove unused CSS — Potential savings of 221 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facbook.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/ys/l/0,cross/Bl_SsT3sZeo.css?_nc_x=Ij3Wp8lg5Kz
119335
118464
https://static.xx.fbcdn.net/rsrc.php/v3/ya/l/0,cross/5CpfRHI1xVm.css?_nc_x=Ij3Wp8lg5Kz
83867
83613
https://static.xx.fbcdn.net/rsrc.php/v3/yG/l/0,cross/XYDswbP7afj.css?_nc_x=Ij3Wp8lg5Kz
25680
24366

Diagnostics

Minimize main-thread work — 2.7 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
2697.788
Rendering
0.054
Script Evaluation
0.044
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of facbook.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 `[alt]` 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"]`
Facbook.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

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.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that facbook.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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://facbook.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

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
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for facbook.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.
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 facbook.com on mobile screens.

Content Best Practices

Document does not have 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.

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.
36

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of facbook.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

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 facbook.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) 79
Performance 73
Accessibility 91
Best Practices 87
SEO 75
Progressive Web App 67
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://m.facebook.com/
Updated: 16th March, 2021

2.50 seconds
First Contentful Paint (FCP)
18%
66%
16%

0.06 seconds
First Input Delay (FID)
84%
14%
2%

Simulate loading on mobile
73

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for facbook.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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive facbook.com as laggy when the latency is higher than 0.05 seconds.
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://facbook.com/
http/1.1
0
72.501000016928
410
0
301
text/html
https://www.facebook.com/
http/1.1
73.182000080124
119.01200003922
450
0
302
text/html
https://m.facebook.com/
h2
119.68400003389
203.11200013384
16605
39108
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/y7/l/0,cross/rvBN2HlBGcU.css?_nc_x=Ij3Wp8lg5Kz
h2
258.69700009935
273.55000004172
2327
8777
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yW/l/0,cross/_Go4LPAcJK0.css?_nc_x=Ij3Wp8lg5Kz
h2
258.93000001088
273.17000017501
1310
2095
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yu/l/0,cross/uuLh2S22YH1.css?_nc_x=Ij3Wp8lg5Kz
h2
259.11199999973
275.28300019912
10551
38722
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/y6/l/0,cross/wkfrsDyUvA3.css?_nc_x=Ij3Wp8lg5Kz
h2
259.55300009809
280.25400009938
12656
50593
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yD/r/BssS1pszwOI.js?_nc_x=Ij3Wp8lg5Kz
h2
259.81100019999
281.09300020151
18754
64373
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iK-b4/yo/l/en_US/u9jdwpbVY-_.js?_nc_x=Ij3Wp8lg5Kz
h2
260.18900005147
279.49400013313
48050
170025
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y0/r/NGZ4Wd8qG0L.js?_nc_x=Ij3Wp8lg5Kz
h2
260.6050001923
283.66399998777
35469
122358
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ym/r/vVAt5FW_B0i.js?_nc_x=Ij3Wp8lg5Kz
h2
260.79400000162
274.45300016552
3923
9518
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/qE6cK94kF5e.js?_nc_x=Ij3Wp8lg5Kz
h2
260.94000018202
278.40100019239
2875
5381
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yo/r/iuh0wz-ZWHQ.js?_nc_x=Ij3Wp8lg5Kz
h2
261.07000000775
275.8300001733
17175
56277
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/YV03KbOP19v.js?_nc_x=Ij3Wp8lg5Kz
h2
262.83000013791
282.42200007662
57022
215520
200
application/x-javascript
Script
https://facebook.com/security/hsts-pixel.gif
h2
297.66899999231
361.29800020717
1746
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/sO8pFbm5AdZ.png
h2
325.43100020848
339.23800010234
9204
8601
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/JopZtdti8dq.js?_nc_x=Ij3Wp8lg5Kz
h2
486.97800002992
500.70800003596
2962
7270
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3i8594/yf/l/en_US/n4bGLjGRWrl.js?_nc_x=Ij3Wp8lg5Kz
h2
489.01400016621
505.45600010082
4604
11206
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3ikP64/yA/l/en_US/RpTFjVvO4D0.js?_nc_x=Ij3Wp8lg5Kz
h2
489.80300012045
506.65600015782
2317
3683
200
application/x-javascript
Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
514.20400012285
527.43200003169
417
79
200
image/png
Image
https://m.facebook.com/a/bz?fb_dtsg=AQE09ZjcKH6F%3AAQGfxY4oU36l&jazoest=21933&lsd=AVqcLF3vD7U&__dyn=0wzpaBwk8aU4ifGh0BBBg9odE4a2i5U4e0C86u7E39x64o1j8hwem0iy1gCwjE1xo33w2sbzo1MU88C0pS0SU2sw64w8W&__csr=&__req=1&__a=AYnVM7Lku-FI0AKpU9jCIoKt4qNRg3GGB8EGdkOxgzI82TLvPvypMNfzpgOuBgmimqUTrMY60Gy4If45N9CLW7kwiS4LIpMrBiuyc0D7o99FyQ&__user=0
h2
1486.5149999969
1536.2760000862
2052
274
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

Opportunities

Properly size images
Images can slow down the page's load time. Facbook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facbook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facbook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facbook.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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 80 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/
84.423
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facbook.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.

Diagnostics

Avoids enormous network payloads — Total size was 245 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/yR/r/YV03KbOP19v.js?_nc_x=Ij3Wp8lg5Kz
57022
https://static.xx.fbcdn.net/rsrc.php/v3iK-b4/yo/l/en_US/u9jdwpbVY-_.js?_nc_x=Ij3Wp8lg5Kz
48050
https://static.xx.fbcdn.net/rsrc.php/v3/y0/r/NGZ4Wd8qG0L.js?_nc_x=Ij3Wp8lg5Kz
35469
https://static.xx.fbcdn.net/rsrc.php/v3/yD/r/BssS1pszwOI.js?_nc_x=Ij3Wp8lg5Kz
18754
https://static.xx.fbcdn.net/rsrc.php/v3/yo/r/iuh0wz-ZWHQ.js?_nc_x=Ij3Wp8lg5Kz
17175
https://m.facebook.com/
16605
https://static.xx.fbcdn.net/rsrc.php/v3/y6/l/0,cross/wkfrsDyUvA3.css?_nc_x=Ij3Wp8lg5Kz
12656
https://static.xx.fbcdn.net/rsrc.php/v3/yu/l/0,cross/uuLh2S22YH1.css?_nc_x=Ij3Wp8lg5Kz
10551
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/sO8pFbm5AdZ.png
9204
https://static.xx.fbcdn.net/rsrc.php/v3i8594/yf/l/en_US/n4bGLjGRWrl.js?_nc_x=Ij3Wp8lg5Kz
4604
Uses efficient cache policy on static assets — 0 resources found
Facbook.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 — 79 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
79
Maximum DOM Depth
or
10
Maximum Child Elements
24
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Facbook.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
24.044
Rendering
1.232
Script Evaluation
0.12
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 — 21 requests • 245 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
21
250879
Script
10
193151
Stylesheet
4
26844
Document
1
16605
Image
3
11367
Other
3
2912
Media
0
0
Font
0
0
Third-party
17
230026
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
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

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

Other

First CPU Idle — 4.2 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Facbook.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/r/YV03KbOP19v.js?_nc_x=Ij3Wp8lg5Kz
57022
300
Remove unused CSS — Potential savings of 12 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facbook.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/y6/l/0,cross/wkfrsDyUvA3.css?_nc_x=Ij3Wp8lg5Kz
12656
12570
Remove unused JavaScript — Potential savings of 81 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/v3iK-b4/yo/l/en_US/u9jdwpbVY-_.js?_nc_x=Ij3Wp8lg5Kz
48050
34887
https://static.xx.fbcdn.net/rsrc.php/v3/yR/r/YV03KbOP19v.js?_nc_x=Ij3Wp8lg5Kz
57022
27199
https://static.xx.fbcdn.net/rsrc.php/v3/y0/r/NGZ4Wd8qG0L.js?_nc_x=Ij3Wp8lg5Kz
35469
20747
Avoid serving legacy JavaScript to modern browsers — Potential savings of 7 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/yR/r/YV03KbOP19v.js?_nc_x=Ij3Wp8lg5Kz
7266

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.2 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 4.2 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 8520 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Facbook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://facbook.com/
630
https://www.facebook.com/
780
https://m.facebook.com/
0
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of facbook.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 `[alt]` 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.

Contrast

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

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"]`
Facbook.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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.
87

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://facbook.com/
Allowed

Audits

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
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for facbook.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 facbook.com on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px
Tap targets are sized appropriately — 100% 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.

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.
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.

Content Best Practices

Document does not have 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.

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.
67

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of facbook.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

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 facbook.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: 31.13.71.1
Continent: Europe
Country: Ireland
Ireland Flag
Region:
City:
Longitude: -6.2439
Latitude: 53.3472
Currencies: EUR
Languages: English
Irish

Web Hosting Provider

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: Unknown
WOT Rating: 3.7/5 (10 reviews)
WOT Trustworthiness: 74/100
WOT Child Safety: 87/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.facebook.com
Issued By: DigiCert SHA2 High Assurance Server CA
Valid From: 10th February, 2021
Valid To: 10th May, 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: 4610391752464174971427059223496372607
Serial Number (Hex): 0377EDDCFAF8BE34BA233C7C2B9A317F
Valid From: 10th February, 2024
Valid To: 10th May, 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 : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Feb 10 19:59:11.996 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:92:A7:57:D8:07:24:E7:6A:C3:23:05:
0D:E8:67:BA:61:18:33:2E:11:40:14:C9:FF:B6:05:DF:
B3:55:96:88:D1:02:21:00:AD:74:0E:28:D8:27:D2:49:
5E:72:39:20:35:6A:6B:FF:6D:59:C2:CC:65:D0:DB:10:
2D:CA:E7:06:AA:9B:E4:B2
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 : Feb 10 19:59:12.056 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:CF:58:AB:04:8C:64:0F:CB:31:37:E0:
1F:8B:36:EC:A4:59:03:A4:81:AA:DB:03:3C:F0:D7:8E:
8D:69:E2:24:EC:02:21:00:D4:A6:77:CC:98:FA:E9:8C:
8A:67:97:6A:7D:59:08:2F:E4:E6:3F:12:15:84:66:34:
4D:62:2E:A5:2B:D9:E8:63
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
facbook.com. 31.13.66.4 IN 299

NS Records

Host Nameserver Class TTL
facbook.com. c.ns.facebook.com. IN 21599
facbook.com. b.ns.facebook.com. IN 21599
facbook.com. d.ns.facebook.com. IN 21599
facbook.com. a.ns.facebook.com. IN 21599

AAAA Records

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

SOA Records

Domain Name Primary NS Responsible Email TTL
facbook.com. a.ns.facebook.com. dns.facebook.com. 3599

TXT Records

Host Value Class TTL
facbook.com. v=spf1 IN 7199

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: 22nd March, 2021
X-Frame-Options: DENY
X-XSS-Protection: 0
Strict-Transport-Security: max-age=15552000; preload
content-security-policy: default-src * data
Set-Cookie: *
X-Content-Type-Options: nosniff
Vary: Accept-Encoding
Pragma: no-cache
x-fb-rlafr: 0
X-FB-Debug: Gg0OKLSLbc8KjdYeYnmKeK7PO+c8ID81xfJW6JlkbABPV2cw1Dt3zIe3xNrK8NHCaLkjVtix+B1DFcEsr6FTyA==
Transfer-Encoding: chunked
Alt-Svc: h3-29=":443"; ma=3600,h3-27=":443"; ma=3600
Connection: keep-alive

Whois Lookup

Created: 17th March, 2005
Changed: 15th February, 2020
Expires: 17th March, 2022
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
serverUpdateProhibited
serverTransferProhibited
serverDeleteProhibited
Nameservers: a.ns.facebook.com
b.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: facbook.com
Registry Domain ID: 146650751_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2020-02-15T02:08:53-0800
Creation Date: 2005-03-17T14:45:51-0800
Registrar Registration Expiration Date: 2022-03-17T00:00:00-0700
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: 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: 2021-03-22T05:36:46-0700 <<<

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
Related

Subdomains

Domain Subdomain
h
m

Similar Sites

Domain Valuation Snoop Score
$3,842 USD 2/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$776 USD 1/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$1,000 USD 2/5
$959 USD 2/5
$4,498 USD 2/5
$915 USD 2/5