fcebook.com

fcebook.com is SSL secured

Free website and domain report on fcebook.com

Last Updated: 17th September, 2021 Update Now
Overview

Snoop Summary for fcebook.com

This is a free and comprehensive report about fcebook.com. The domain fcebook.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 fcebook.com is owned/operated by Facebook, Inc.. If fcebook.com was to be sold it would possibly be worth $509 USD (based on the daily revenue potential of the website over a 24 month period). Fcebook.com receives an estimated 240 unique visitors every day - a decent amount of traffic! This report was last updated 17th September, 2021.

About fcebook.com

Site Preview: fcebook.com fcebook.com
Title: Facebook
Description: Create an account or log into Facebook. Connect with friends, family and other people you know. Share photos and videos, send messages and get updates.
Keywords and Tags: blogs, scam, wiki
Related Terms:
Fav Icon:
Age: Over 17 years old
Domain Created: 21st July, 2006
Domain Updated: 23rd April, 2021
Domain Expires: 21st July, 2022
Review

Snoop Score

1/5

Valuation

$509 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,719,894
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: 240
Monthly Visitors: 7,305
Yearly Visitors: 87,600
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

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

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 77
Performance 100
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: 17th September, 2021

4.33 seconds
First Contentful Paint (FCP)
20%
34%
46%

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

Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
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.
First Meaningful Paint — 0.6 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://fcebook.com/
http/1.1
0
68.986000027508
444
0
301
text/html
https://www.facebook.com/
h2
69.543000310659
202.07000011578
39224
221818
200
text/html
Document
https://www.facebook.com/rsrc.php/v3/yc/l/0,cross/uNHsnsSpmSh.css?_nc_x=Ij3Wp8lg5Kz
h2
248.87000024319
263.52700032294
6402
19616
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yz/l/0,cross/3xiS7iPugLl.css?_nc_x=Ij3Wp8lg5Kz
h2
249.09500032663
261.10400026664
3223
6471
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/y1/l/0,cross/EPrChZcd_SJ.css?_nc_x=Ij3Wp8lg5Kz
h2
249.3030000478
267.7810001187
12580
53067
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yJ/l/0,cross/YytQ2o3TBbV.css?_nc_x=Ij3Wp8lg5Kz
h2
249.52000007033
260.66899998114
1206
3321
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yH/l/0,cross/AUpB7eoMhKr.css?_nc_x=Ij3Wp8lg5Kz
h2
249.72700001672
282.61100035161
1896
4320
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yH/l/0,cross/JqPt5CpHYqq.css?_nc_x=Ij3Wp8lg5Kz
h2
249.98600035906
265.68800024688
2423
8569
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yP/l/0,cross/r0ZysP3aGND.css?_nc_x=Ij3Wp8lg5Kz
h2
250.23000035435
263.78200016916
1222
3406
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yU/r/BZDm6Zcufz_.js?_nc_x=Ij3Wp8lg5Kz
h2
250.5900003016
267.03500002623
89161
328009
200
application/x-javascript
Script
https://facebook.com/security/hsts-pixel.gif
h2
336.68099995703
390.15999995172
2626
43
200
image/gif
Image
https://www.facebook.com/rsrc.php/v3/yr/r/BNzLtjA89q3.js?_nc_x=Ij3Wp8lg5Kz
h2
284.14300037548
296.06000008062
9975
30405
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yF/r/dATna7NWzvc.js?_nc_x=Ij3Wp8lg5Kz
h2
286.69600002468
298.05500013754
12185
38789
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yp/r/XpFprvKSai6.js?_nc_x=Ij3Wp8lg5Kz
h2
336.28199994564
349.57899991423
9617
29465
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3i7M54/y4/l/en_US/aMXCqJ5tscL.js?_nc_x=Ij3Wp8lg5Kz
h2
336.48700034246
350.26300000027
20156
74573
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/y4/r/HI2nserIj2x.png
h2
343.66400027648
354.53299991786
15846
15305
200
image/png
Image
data
413.11200009659
413.24699996039
0
0
200
text/css
Stylesheet
data
413.42100035399
413.46100019291
0
78
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yI/r/z44tIw900d6.js?_nc_x=Ij3Wp8lg5Kz
h2
454.0190002881
478.36500033736
778
245
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iYXl4/yN/l/en_US/Ou0wKR1sTZQ.js?_nc_x=Ij3Wp8lg5Kz
h2
454.25500022247
475.43200012296
26677
93248
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3ipVm4/yQ/l/en_US/paSmJfOErCc.js?_nc_x=Ij3Wp8lg5Kz
h2
454.8650002107
473.28600008041
30053
112704
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/y0/r/fvmSzDrhmwU.js?_nc_x=Ij3Wp8lg5Kz
h2
455.26499999687
474.33100035414
7233
17442
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/ya/r/KxDP19oxIwA.js?_nc_x=Ij3Wp8lg5Kz
h2
455.59599995613
472.57500002161
2165
4251
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yL/r/NCpmJB5SlXr.js?_nc_x=Ij3Wp8lg5Kz
h2
455.93699999154
476.25300008804
18823
54932
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yy/r/fhK1xmKsAs_.js?_nc_x=Ij3Wp8lg5Kz
h2
456.34900033474
474.07600004226
2624
5675
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yX/r/sV6rEbVnOoV.js?_nc_x=Ij3Wp8lg5Kz
h2
456.68600033969
473.75200036913
1292
670
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yR/r/JEikBAe4aDj.js?_nc_x=Ij3Wp8lg5Kz
h2
457.16900005937
474.62200000882
2303
5116
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yz/r/lYejkzyV906.js?_nc_x=Ij3Wp8lg5Kz
h2
457.44800008833
475.80499993637
1949
770
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yB/r/FYIV9LyqXbP.js?_nc_x=Ij3Wp8lg5Kz
h2
457.84600032493
474.961000029
2149
1006
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iPwL4/yB/l/en_US/BgKmHNcqK-z.js?_nc_x=Ij3Wp8lg5Kz
h2
458.29400001094
476.69900022447
14929
45282
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yj/r/-jY7SqbZSzy.js?_nc_x=Ij3Wp8lg5Kz
h2
458.82500009611
510.23600017652
1372
446
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yX/r/2jpi00l_u7R.js?_nc_x=Ij3Wp8lg5Kz
h2
459.26700020209
477.25300025195
43021
142718
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yv/r/cN-N4Eu_deZ.js?_nc_x=Ij3Wp8lg5Kz
h2
461.16900024936
477.71500004455
2892
7286
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iqES4/y1/l/en_US/ozPZJBVboQA.js?_nc_x=Ij3Wp8lg5Kz
h2
461.56500000507
478.73700037599
16480
48496
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/ye/r/3mc4XDZ6Guq.js?_nc_x=Ij3Wp8lg5Kz
h2
461.94500010461
478.0379999429
3634
8331
200
application/x-javascript
Script
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__csr=&__dyn=7xe6Fo4OQ1PyUbFuC1swgE98nwgU6C7UW3q327E2vwXx60kO4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwl8G0me2218w5uwdK0D83mwaS0zE5W09yyE158&__hs=18887.PHASED%3ADEFAULT.2.0.0.0.0&__hsi=7008926543271727445-0&__req=1&__rev=1004413329&__s=c6xbqe%3Amzjbuh%3Aw5dizd&__spin_b=trunk&__spin_r=1004413329&__spin_t=1631892878&__user=0&dpr=1&jazoest=2904&lsd=AVpLz0SAzM0
h2
1541.7180000804
1576.8369999714
2542
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)
246.385
3656.776
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.

Opportunities

Eliminate render-blocking resources — Potential savings of 120 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fcebook.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://www.facebook.com/rsrc.php/v3/yU/r/BZDm6Zcufz_.js?_nc_x=Ij3Wp8lg5Kz
89161
80
Properly size images
Images can slow down the page's load time. Fcebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fcebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fcebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fcebook.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fcebook.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://www.facebook.com/rsrc.php/v3/y1/l/0,cross/EPrChZcd_SJ.css?_nc_x=Ij3Wp8lg5Kz
12580
11486
Reduce unused JavaScript — Potential savings of 130 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://www.facebook.com/rsrc.php/v3/yU/r/BZDm6Zcufz_.js?_nc_x=Ij3Wp8lg5Kz
89161
45328
https://www.facebook.com/rsrc.php/v3/yX/r/2jpi00l_u7R.js?_nc_x=Ij3Wp8lg5Kz
43021
42818
https://www.facebook.com/rsrc.php/v3ipVm4/yQ/l/en_US/paSmJfOErCc.js?_nc_x=Ij3Wp8lg5Kz
30053
23142
https://www.facebook.com/rsrc.php/v3iYXl4/yN/l/en_US/Ou0wKR1sTZQ.js?_nc_x=Ij3Wp8lg5Kz
26677
21651
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 9 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://www.facebook.com/rsrc.php/v3/y4/r/HI2nserIj2x.png
15305
8994.15
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 130 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/
133.524
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Fcebook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fcebook.com/
190
https://www.facebook.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fcebook.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 15 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://www.facebook.com/rsrc.php/v3/yU/r/BZDm6Zcufz_.js?_nc_x=Ij3Wp8lg5Kz
15720
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 400 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.facebook.com/rsrc.php/v3/yU/r/BZDm6Zcufz_.js?_nc_x=Ij3Wp8lg5Kz
89161
https://www.facebook.com/rsrc.php/v3/yX/r/2jpi00l_u7R.js?_nc_x=Ij3Wp8lg5Kz
43021
https://www.facebook.com/
39224
https://www.facebook.com/rsrc.php/v3ipVm4/yQ/l/en_US/paSmJfOErCc.js?_nc_x=Ij3Wp8lg5Kz
30053
https://www.facebook.com/rsrc.php/v3iYXl4/yN/l/en_US/Ou0wKR1sTZQ.js?_nc_x=Ij3Wp8lg5Kz
26677
https://www.facebook.com/rsrc.php/v3i7M54/y4/l/en_US/aMXCqJ5tscL.js?_nc_x=Ij3Wp8lg5Kz
20156
https://www.facebook.com/rsrc.php/v3/yL/r/NCpmJB5SlXr.js?_nc_x=Ij3Wp8lg5Kz
18823
https://www.facebook.com/rsrc.php/v3iqES4/y1/l/en_US/ozPZJBVboQA.js?_nc_x=Ij3Wp8lg5Kz
16480
https://www.facebook.com/rsrc.php/v3/y4/r/HI2nserIj2x.png
15846
https://www.facebook.com/rsrc.php/v3iPwL4/yB/l/en_US/BgKmHNcqK-z.js?_nc_x=Ij3Wp8lg5Kz
14929
Uses efficient cache policy on static assets — 0 resources found
Fcebook.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 — 210 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
210
Maximum DOM Depth
15
Maximum Child Elements
29
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fcebook.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
3663.473
0.028
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 — 34 requests • 400 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
34
409102
Script
22
319468
Document
1
39224
Stylesheet
7
28952
Image
2
18472
Other
2
2986
Media
0
0
Font
0
0
Third-party
1
444
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.

Diagnostics

Minimize main-thread work — 3.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
3663.355
Rendering
0.09
Script Evaluation
0.028
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fcebook.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"]`
Fcebook.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 fcebook.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
Elements controlled by object-src are considered legacy features. Consider setting object-src to 'none' to prevent the injection of plugins that execute unsafe scripts.
object-src
High
Host allowlists can frequently be bypassed. Consider using 'strict-dynamic' in combination with CSP nonces or hashes.
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
No CSP configures a reporting destination. This makes it difficult to maintain the CSP over time and monitor for any breakages.
report-uri
Medium

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://fcebook.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 fcebook.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 fcebook.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 fcebook.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 fcebook.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 75
Accessibility 89
Best Practices 87
SEO 75
Progressive Web App 67
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://m.facebook.com/
Updated: 17th September, 2021

2.87 seconds
First Contentful Paint (FCP)
46%
31%
23%

0.04 seconds
First Input Delay (FID)
87%
11%
2%

Simulate loading on mobile
75

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for fcebook.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.
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://fcebook.com/
http/1.1
0
153.03200000199
430
0
301
text/html
https://www.facebook.com/
http/1.1
153.84699997958
202.96999998391
470
0
302
text/html
https://m.facebook.com/
h2
203.61599995522
326.40999997966
18112
40323
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yi/l/0,cross/9QOztNwJD93.css?_nc_x=Ij3Wp8lg5Kz
h2
457.24299998255
496.85900000622
3027
10178
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yM/l/0,cross/B3soumo67Qo.css?_nc_x=Ij3Wp8lg5Kz
h2
457.735999953
552.17599996831
8441
28976
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/y5/l/0,cross/NiuPq4tFN_z.css?_nc_x=Ij3Wp8lg5Kz
h2
458.0100000021
554.08400000306
8285
35268
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3iS674/yQ/l/en_US/F3ejf4qN7Pi.js?_nc_x=Ij3Wp8lg5Kz
h2
458.40699999826
558.96399996709
50204
176663
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y7/r/tmoaFSpR9lO.js?_nc_x=Ij3Wp8lg5Kz
h2
458.73999997275
552.84600000596
15390
48781
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/UP7cGnAcBAF.js?_nc_x=Ij3Wp8lg5Kz
h2
459.18999996502
553.32599999383
9997
30706
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/2jr_tFUjDMy.js?_nc_x=Ij3Wp8lg5Kz
h2
459.49599996675
495.79999997513
886
235
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iVH_4/yp/l/en_US/jcMAXTbdORl.js?_nc_x=Ij3Wp8lg5Kz
h2
459.83800000977
556.1480000033
13063
41170
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/M4WYEDn5b1N.js?_nc_x=Ij3Wp8lg5Kz
h2
460.11099999305
555.1989999949
3844
7817
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yl/r/ilMFccLWbov.js?_nc_x=Ij3Wp8lg5Kz
h2
460.38599999156
554.69399999129
8053
22515
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/lXiDeprKTkF.js?_nc_x=Ij3Wp8lg5Kz
h2
462.10399997653
557.6669999864
73228
268946
200
application/x-javascript
Script
https://facebook.com/security/hsts-pixel.gif
h2
582.01799995732
652.7519999654
2616
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/y6/r/KVAlhzGjaiF.png
h2
684.69999998342
754.14199999068
12054
11431
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/Ek_BSN5mdZ5.js?_nc_x=Ij3Wp8lg5Kz
h2
1056.1049999669
1071.8369999668
22303
83347
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yv/r/cN-N4Eu_deZ.js?_nc_x=Ij3Wp8lg5Kz
h2
1056.8089999724
1078.3059999812
3956
7286
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yV/r/Dg-fRqrcPq6.js?_nc_x=Ij3Wp8lg5Kz
h2
1057.5989999925
1072.8159999708
11681
35503
200
application/x-javascript
Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
1096.819999977
1152.8059999691
436
79
200
image/png
Image
https://m.facebook.com/a/bz?fb_dtsg=AQHtYSpWxtDIl6c%3A0%3A0&jazoest=21555&lsd=AVorBwAiglw&__dyn=0wzpaBwk8aU4ifDg9ppk2m3q12wAxu13w9y1DxW0Oohx60kO4o3Bw4Ewk9E4W0om0MU0D2US0se229w6twdK0D81x82ew5fw5NyE158&__csr=&__req=1&__a=AYlJkUe6xBAGRdoC7eWr7XyOzmu6hNkeax8ruHZyO2KBP73FIYN56f8ikW4ZvAB5h4bZ0Oyd3WTSr16uU2d1VJxCcNQ0Sgb_LzjGIUiYOp7C2Q&__user=0
h2
2154.3069999898
2252.5259999675
3040
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.
Start Time (Ms) End Time (Ms)
396.77
4273.77
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.

Opportunities

Properly size images
Images can slow down the page's load time. Fcebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fcebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fcebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fcebook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fcebook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 120 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/
123.791
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fcebook.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 15 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/y3/r/lXiDeprKTkF.js?_nc_x=Ij3Wp8lg5Kz
15747
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 263 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/y3/r/lXiDeprKTkF.js?_nc_x=Ij3Wp8lg5Kz
73228
https://static.xx.fbcdn.net/rsrc.php/v3iS674/yQ/l/en_US/F3ejf4qN7Pi.js?_nc_x=Ij3Wp8lg5Kz
50204
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/Ek_BSN5mdZ5.js?_nc_x=Ij3Wp8lg5Kz
22303
https://m.facebook.com/
18112
https://static.xx.fbcdn.net/rsrc.php/v3/y7/r/tmoaFSpR9lO.js?_nc_x=Ij3Wp8lg5Kz
15390
https://static.xx.fbcdn.net/rsrc.php/v3iVH_4/yp/l/en_US/jcMAXTbdORl.js?_nc_x=Ij3Wp8lg5Kz
13063
https://static.xx.fbcdn.net/rsrc.php/v3/y6/r/KVAlhzGjaiF.png
12054
https://static.xx.fbcdn.net/rsrc.php/v3/yV/r/Dg-fRqrcPq6.js?_nc_x=Ij3Wp8lg5Kz
11681
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/UP7cGnAcBAF.js?_nc_x=Ij3Wp8lg5Kz
9997
https://static.xx.fbcdn.net/rsrc.php/v3/yM/l/0,cross/B3soumo67Qo.css?_nc_x=Ij3Wp8lg5Kz
8441
Uses efficient cache policy on static assets — 0 resources found
Fcebook.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. Fcebook.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
17129.592
0.112
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 — 21 requests • 263 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
269516
Script
11
212605
Stylesheet
3
19753
Document
1
18112
Image
3
15106
Other
3
3940
Media
0
0
Font
0
0
Third-party
17
245278
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.0 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 4.0 s
The time taken for the page to become fully interactive.

Other

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

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. Fcebook.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/y3/r/lXiDeprKTkF.js?_nc_x=Ij3Wp8lg5Kz
73228
300
Reduce unused JavaScript — Potential savings of 70 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/y3/r/lXiDeprKTkF.js?_nc_x=Ij3Wp8lg5Kz
73228
39549
https://static.xx.fbcdn.net/rsrc.php/v3iS674/yQ/l/en_US/F3ejf4qN7Pi.js?_nc_x=Ij3Wp8lg5Kz
50204
32627

Metrics

First Contentful Paint — 4.0 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.

Opportunities

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

Diagnostics

Minimize main-thread work — 17.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
17128.268
Rendering
1.212
Script Evaluation
0.112

Other

First Contentful Paint (3G) — 8220 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
89

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fcebook.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"]`
Fcebook.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 fcebook.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.
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
Elements controlled by object-src are considered legacy features. Consider setting object-src to 'none' to prevent the injection of plugins that execute unsafe scripts.
object-src
High
Host allowlists can frequently be bypassed. Consider using 'strict-dynamic' in combination with CSP nonces or hashes.
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
No CSP configures a reporting destination. This makes it difficult to maintain the CSP over time and monitor for any breakages.
report-uri
Medium

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://fcebook.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 fcebook.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 fcebook.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 fcebook.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 fcebook.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 Admin
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
RegistrarSEC, LLC 192.0.66.80
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.facebook.com
Issued By: DigiCert SHA2 High Assurance Server CA
Valid From: 9th September, 2021
Valid To: 8th December, 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: 8780474663858295784024704130842666748
Serial Number (Hex): 069B0ED310CCA51690045A57CDFCA6FC
Valid From: 9th September, 2024
Valid To: 8th December, 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 : Sep 9 18:41:35.252 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:83:1E:1B:A7:D4:27:E2:47:7F:38:ED:
6D:A1:7D:F4:44:6F:D3:6A:38:41:54:90:FF:71:93:28:
F3:4B:08:AD:95:02:20:7E:7E:9A:3D:56:E2:48:A8:31:
D6:19:0A:CA:4D:36:93:D9:0A:C3:1D:B8:61:96:2E:2C:
34:EC:67:90:B9:2E:34
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 : Sep 9 18:41:35.282 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D8:DF:83:44:05:C6:38:9D:E7:C4:54:
95:72:D4:BB:48:A2:69:58:A2:50:B8:1E:06:C5:26:E4:
17:64:C5:26:E6:02:20:24:C3:93:C3:6D:81:20:67:96:
25:15:79:65:A0:98:07:B0:3F:1C:4B:D6:6C:D3:EF:E2:
23:6A:69:55:75:E0:EC
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 : Sep 9 18:41:35.332 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:E6:B3:E1:9D:A9:25:14:75:26:B2:8D:
EE:A9:9C:F7:DC:24:37:51:BA:13:FA:23:42:48:86:F1:
50:AE:15:83:11:02:20:4C:28:D9:BC:E5:BD:8E:CA:13:
83:22:DE:2F:53:D9:3F:C0:E5:AE:F9:5B:A2:07:2B:2C:
4F:EC:68:20:73:AA:76
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
fcebook.com. 31.13.71.1 IN 300

NS Records

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

AAAA Records

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

SOA Records

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

TXT Records

Host Value Class TTL
fcebook.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: 17th September, 2021
Pragma: no-cache
content-security-policy-report-only: default-src 'self' data
content-security-policy: default-src * data
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
Vary: Accept-Encoding
Strict-Transport-Security: max-age=15552000; preload
X-FB-Debug: i8wJKzWyiOW9Ht+v3g5wGiLxiPSaIeWoDprOygGZq+nZyOZLJ1YSMjLyLWff0N3KJLaTuGa3dAtlUiAxGptqwQ==
Transfer-Encoding: chunked
Alt-Svc: h3=":443"; ma=3600, h3-29=":443"; ma=3600,h3-27=":443"; ma=3600
Connection: keep-alive

Whois Lookup

Created: 21st July, 2006
Changed: 23rd April, 2021
Expires: 21st July, 2022
Registrar: RegistrarSEC, LLC
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: a.ns.facebook.com
b.ns.facebook.com
c.ns.facebook.com
d.ns.facebook.com
Owner Name: Domain Admin
Owner Organization: Facebook, Inc.
Owner Street: 1601 Willow Rd
Owner Post Code: 94025
Owner City: Menlo Park
Owner State: CA
Owner Country: US
Owner Phone: +1.6505434800
Owner Email: domain@fb.com
Admin Name: Domain Admin
Admin Organization: Facebook, Inc.
Admin Street: 1601 Willow Rd
Admin Post Code: 94025
Admin City: Menlo Park
Admin State: CA
Admin Country: US
Admin Phone: +1.6505434800
Admin Email: domain@fb.com
Tech Name: Domain Admin
Tech Organization: Facebook, Inc.
Tech Street: 1601 Willow Rd
Tech Post Code: 94025
Tech City: Menlo Park
Tech State: CA
Tech Country: US
Tech Phone: +1.6505434800
Tech Email: domain@fb.com
Full Whois: Domain Name: FCEBOOK.COM
Registry Domain ID: 526916662_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrarsec.com
Registrar URL: https://www.registrarsec.com
Updated Date: 2021-04-23T09:00:09Z
Creation Date: 2006-07-21T18:44:55Z
Registrar Registration Expiration Date: 2022-07-21T18:44:55Z
Registrar: RegistrarSEC, LLC
Registrar IANA ID: 2475
Registrar Abuse Contact Email: abusecomplaints@registrarsec.com
Registrar Abuse Contact Phone: +1.6503087004
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: Domain Admin
Registrant Organization: Facebook, Inc.
Registrant Street: 1601 Willow Rd
Registrant City: Menlo Park
Registrant State/Province: CA
Registrant Postal Code: 94025
Registrant Country: US
Registrant Phone: +1.6505434800
Registrant Phone Ext:
Registrant Fax: +1.6505434800
Registrant Fax Ext:
Registrant Email: domain@fb.com
Registry Admin ID:
Admin Name: Domain Admin
Admin Organization: Facebook, Inc.
Admin Street: 1601 Willow Rd
Admin City: Menlo Park
Admin State/Province: CA
Admin Postal Code: 94025
Admin Country: US
Admin Phone: +1.6505434800
Admin Phone Ext:
Admin Fax: +1.6505434800
Admin Fax Ext:
Admin Email: domain@fb.com
Registry Tech ID:
Tech Name: Domain Admin
Tech Organization: Facebook, Inc.
Tech Street: 1601 Willow Rd
Tech City: Menlo Park
Tech State/Province: CA
Tech Postal Code: 94025
Tech Country: US
Tech Phone: +1.6505434800
Tech Phone Ext:
Tech Fax: +1.6505434800
Tech Fax Ext:
Tech Email: domain@fb.com
Name Server: D.NS.FACEBOOK.COM
Name Server: A.NS.FACEBOOK.COM
Name Server: B.NS.FACEBOOK.COM
Name Server: C.NS.FACEBOOK.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-09-17T15:34:35Z <<<

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

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

Nameservers

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

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

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