fecbook.com

fecbook.com is SSL secured

Free website and domain report on fecbook.com

Last Updated: 9th March, 2023 Update Now
Overview

Snoop Summary for fecbook.com

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

About fecbook.com

Site Preview: fecbook.com fecbook.com
Title: Facebook
Description: Log into Facebook to start sharing and connecting with your friends, family, and people you know.
Keywords and Tags: social networking
Related Terms:
Fav Icon:
Age: Over 12 years old
Domain Created: 27th January, 2012
Domain Updated: 30th October, 2022
Domain Expires: 27th January, 2024
Review

Snoop Score

1/5

Valuation

$780 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,392,168
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 21
Moz Page Authority: 30

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 370
Monthly Visitors: 11,262
Yearly Visitors: 135,050
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $32 USD
Yearly Revenue: $385 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: fecbook.com 11
Domain Name: fecbook 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: 26th August, 2021

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

0.02 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 fecbook.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://fecbook.com/
http/1.1
0
67.619999987073
410
0
301
text/html
https://www.facebook.com/
h2
68.226000003051
182.32099997113
38586
215627
200
text/html
Document
https://www.facebook.com/rsrc.php/v3/yl/l/0,cross/QALwxiYrAS3.css?_nc_x=Ij3Wp8lg5Kz
h2
245.82499999087
261.74599997466
7199
23865
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yR/l/0,cross/_xMVT4ahFHk.css?_nc_x=Ij3Wp8lg5Kz
h2
246.57800002024
262.01900001615
2995
6878
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yB/l/0,cross/COzfGZbhfQE.css?_nc_x=Ij3Wp8lg5Kz
h2
246.78400001721
263.59899999807
9159
37387
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yv/l/0,cross/fp8-mOFTWQj.css?_nc_x=Ij3Wp8lg5Kz
h2
246.96499999845
261.43800001591
1491
1506
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yu/l/0,cross/dNU0-BAD4y4.css?_nc_x=Ij3Wp8lg5Kz
h2
247.16299999272
261.01000001654
1854
2577
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yo/r/fVrccGYeqA3.js?_nc_x=Ij3Wp8lg5Kz
h2
247.55500000902
268.73299997533
89090
327747
200
application/x-javascript
Script
https://facebook.com/security/hsts-pixel.gif
h2
365.4230000102
429.41899999278
2478
43
200
image/gif
Image
https://www.facebook.com/rsrc.php/v3/yH/r/3D1GSk25Cva.js?_nc_x=Ij3Wp8lg5Kz
h2
268.11399997678
284.05100002419
11032
32523
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3i7M54/yS/l/en_US/C9c1zn1DdlK.js?_nc_x=Ij3Wp8lg5Kz
h2
289.19799998403
304.40000002272
17617
63573
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yw/r/tdDEfmyARg8.js?_nc_x=Ij3Wp8lg5Kz
h2
297.08400001982
312.18000000808
6775
17243
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yt/r/HwqsTXzG09N.js?_nc_x=Ij3Wp8lg5Kz
h2
365.22899998818
381.06899999548
10935
29664
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yX/r/vpNyM5SaEcn.png
h2
375.18799997633
390.13000001432
8740
7676
200
image/png
Image
data
468.45099999337
468.5499999905
0
0
200
text/css
Stylesheet
data
468.8389999792
468.90400000848
0
78
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yp/r/RcbC8Iz1Dw1.js?_nc_x=Ij3Wp8lg5Kz
h2
537.54900000058
551.91400001058
5771
13827
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3ipVm4/yp/l/en_US/9Uf9YmZJ-zs.js?_nc_x=Ij3Wp8lg5Kz
h2
538.45699998783
552.42999998154
7028
18458
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yp/r/M_RYK_Kpsdg.js?_nc_x=Ij3Wp8lg5Kz
h2
539.30200001923
553.72000002535
5971
14301
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yZ/r/4pC2DcdajL5.js?_nc_x=Ij3Wp8lg5Kz
h2
540.09999998379
555.59000000358
2207
2577
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yl/r/dH0i5mMgCSJ.js?_nc_x=Ij3Wp8lg5Kz
h2
540.77600000892
555.05700001959
10265
28271
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yq/r/5fUqTLVv42u.js?_nc_x=Ij3Wp8lg5Kz
h2
541.59300000174
559.6689999802
20180
74809
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iYXl4/yg/l/en_US/ojBwTvIv7bS.js?_nc_x=Ij3Wp8lg5Kz
h2
542.09000000264
557.45500000194
26792
90728
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yp/r/OE1GvYQP60y.js?_nc_x=Ij3Wp8lg5Kz
h2
542.75099997176
558.39299998479
3463
7973
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yI/r/jVt3lQ9jDac.js?_nc_x=Ij3Wp8lg5Kz
h2
543.60299999826
558.83900000481
10647
27856
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yY/r/1RSiIL-ofVK.js?_nc_x=Ij3Wp8lg5Kz
h2
544.21600000933
560.11700001545
2760
4267
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yZ/r/a0oVgaeI1iB.js?_nc_x=Ij3Wp8lg5Kz
h2
544.94200000772
560.58599997777
1076
909
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/y9/r/zembomw19DT.js?_nc_x=Ij3Wp8lg5Kz
h2
545.62799999258
566.69100001454
2749
4931
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yX/r/sV6rEbVnOoV.js?_nc_x=Ij3Wp8lg5Kz
h2
546.20300000533
567.1250000014
1515
670
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yG/r/vDmZmEHXuDg.js?_nc_x=Ij3Wp8lg5Kz
h2
547.00399999274
569.19700000435
820
251
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yN/r/Igb6aDFCLfe.js?_nc_x=Ij3Wp8lg5Kz
h2
547.67699999502
579.12499998929
5319
11518
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yQ/r/WEEp_zVW3er.js?_nc_x=Ij3Wp8lg5Kz
h2
548.39900002116
578.54299998144
4640
12849
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yp/r/cqDWHfAyymG.js?_nc_x=Ij3Wp8lg5Kz
h2
549.33499998879
579.61199997226
2392
3655
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yu/r/L3ULNmQJCDl.js?_nc_x=Ij3Wp8lg5Kz
h2
549.89800002659
580.08699998027
2861
5340
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iPwL4/yJ/l/en_US/rHiNvfvWC61.js?_nc_x=Ij3Wp8lg5Kz
h2
550.48400000669
581.91000000807
15790
46558
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yb/r/HBrjVeHV3Lw.js?_nc_x=Ij3Wp8lg5Kz
h2
551.20500002522
583.17900000839
43108
140763
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yv/r/cN-N4Eu_deZ.js?_nc_x=Ij3Wp8lg5Kz
h2
554.71499997657
584.87299998524
3422
7286
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yd/r/lGvLxO7RlAm.js?_nc_x=Ij3Wp8lg5Kz
h2
556.12000002293
587.20800001174
4320
9609
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iqES4/yY/l/en_US/0g-h6QmT-I2.js?_nc_x=Ij3Wp8lg5Kz
h2
556.32600001991
588.47199997399
15819
46200
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yr/r/6z71NcKIBkP.js?_nc_x=Ij3Wp8lg5Kz
h2
556.63000000641
586.33499999996
2595
4716
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/y9/r/ugD21mPGNBo.js?_nc_x=Ij3Wp8lg5Kz
h2
557.08399997093
587.98700000625
1700
1437
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yy/r/lGAfVW6pT4t.js?_nc_x=Ij3Wp8lg5Kz
h2
558.26899997192
589.27799999947
3242
6846
200
application/x-javascript
Script
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__csr=&__dyn=7xe6Fo4OQ1PyUbFuC1swgE98nwgU6C7UW3q327E2vwXx60kO4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwl8G0me2218w5uwdK0D83mwaS0zE5W09yyE&__hs=18865.PHASED%3ADEFAULT.2.0.0.0.0&__hsi=7000881518847249056-0&__req=1&__rev=1004315508&__s=fp7s6r%3Ax2y9db%3A1xe2q0&__spin_b=trunk&__spin_r=1004315508&__spin_t=1630019750&__user=0&dpr=1&jazoest=2897&lsd=AVq9K0XicPQ
h2
1701.9669999718
1767.4090000219
2411
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)
195.755
5.568
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. Fecbook.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/yo/r/fVrccGYeqA3.js?_nc_x=Ij3Wp8lg5Kz
89090
80
Properly size images
Images can slow down the page's load time. Fecbook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fecbook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fecbook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fecbook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fecbook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 107 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/yo/r/fVrccGYeqA3.js?_nc_x=Ij3Wp8lg5Kz
89090
45324
https://www.facebook.com/rsrc.php/v3/yb/r/HBrjVeHV3Lw.js?_nc_x=Ij3Wp8lg5Kz
43108
42902
https://www.facebook.com/rsrc.php/v3iYXl4/yg/l/en_US/ojBwTvIv7bS.js?_nc_x=Ij3Wp8lg5Kz
26792
21843
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://www.facebook.com/
115.091
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Fecbook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fecbook.com/
190
https://www.facebook.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fecbook.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/yo/r/fVrccGYeqA3.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 407 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/yo/r/fVrccGYeqA3.js?_nc_x=Ij3Wp8lg5Kz
89090
https://www.facebook.com/rsrc.php/v3/yb/r/HBrjVeHV3Lw.js?_nc_x=Ij3Wp8lg5Kz
43108
https://www.facebook.com/
38586
https://www.facebook.com/rsrc.php/v3iYXl4/yg/l/en_US/ojBwTvIv7bS.js?_nc_x=Ij3Wp8lg5Kz
26792
https://www.facebook.com/rsrc.php/v3/yq/r/5fUqTLVv42u.js?_nc_x=Ij3Wp8lg5Kz
20180
https://www.facebook.com/rsrc.php/v3i7M54/yS/l/en_US/C9c1zn1DdlK.js?_nc_x=Ij3Wp8lg5Kz
17617
https://www.facebook.com/rsrc.php/v3iqES4/yY/l/en_US/0g-h6QmT-I2.js?_nc_x=Ij3Wp8lg5Kz
15819
https://www.facebook.com/rsrc.php/v3iPwL4/yJ/l/en_US/rHiNvfvWC61.js?_nc_x=Ij3Wp8lg5Kz
15790
https://www.facebook.com/rsrc.php/v3/yH/r/3D1GSk25Cva.js?_nc_x=Ij3Wp8lg5Kz
11032
https://www.facebook.com/rsrc.php/v3/yt/r/HwqsTXzG09N.js?_nc_x=Ij3Wp8lg5Kz
10935
Uses efficient cache policy on static assets — 0 resources found
Fecbook.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 — 208 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
208
Maximum DOM Depth
15
Maximum Child Elements
29
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. Fecbook.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
9.542
Rendering
0.048
Script Evaluation
0.026
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 — 41 requests • 407 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
41
417224
Script
31
341901
Document
1
38586
Stylesheet
5
22698
Image
2
11218
Other
2
2821
Media
0
0
Font
0
0
Third-party
1
410
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.
98

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fecbook.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"]`
Fecbook.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 fecbook.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://fecbook.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 fecbook.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 fecbook.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 fecbook.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 fecbook.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) 78
Performance 74
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: 26th August, 2021

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

0.05 seconds
First Input Delay (FID)
86%
11%
3%

Simulate loading on mobile
74

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for fecbook.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://fecbook.com/
http/1.1
0
64.971999963745
384
0
301
text/html
https://www.facebook.com/
http/1.1
65.454999916255
99.460999947041
420
0
302
text/html
https://m.facebook.com/
h2
99.962999811396
225.10799998417
18094
40829
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yk/l/0,cross/DcGDxEkELm2.css?_nc_x=Ij3Wp8lg5Kz
h2
264.06899979338
301.89699982293
2109
5717
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yi/l/0,cross/1o7j2NA-rb5.css?_nc_x=Ij3Wp8lg5Kz
h2
264.21299995854
279.88899988122
9094
29496
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/y6/l/0,cross/YvBqlAU8ROL.css?_nc_x=Ij3Wp8lg5Kz
h2
264.52699978836
281.42999997362
8414
32873
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yY/l/en_US/oqLiJlt60SD.js?_nc_x=Ij3Wp8lg5Kz
h2
264.84699989669
284.9649998825
51218
176544
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/QZnyh0f28Vs.js?_nc_x=Ij3Wp8lg5Kz
h2
265.01499977894
285.860999953
15411
46783
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yZ/l/0,cross/v7AcTWJZZva.css?_nc_x=Ij3Wp8lg5Kz
h2
265.24699991569
281.77999984473
3142
7545
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3isIi4/yq/l/en_US/7xwPLIJREOG.js?_nc_x=Ij3Wp8lg5Kz
h2
265.46499994583
282.94199984521
15609
47844
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/UP7cGnAcBAF.js?_nc_x=Ij3Wp8lg5Kz
h2
265.640999889
280.48999980092
10502
30706
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/2jr_tFUjDMy.js?_nc_x=Ij3Wp8lg5Kz
h2
265.78299980611
283.78399997018
1414
235
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/oNc1zYCy2PI.js?_nc_x=Ij3Wp8lg5Kz
h2
265.92299994081
283.4239997901
3918
8010
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y7/r/PYgQcxUrcX_.js?_nc_x=Ij3Wp8lg5Kz
h2
266.17699977942
284.38099985942
11130
31054
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/-oBflkGHHEM.js?_nc_x=Ij3Wp8lg5Kz
h2
267.54599995911
287.23799996078
73145
268757
200
application/x-javascript
Script
https://facebook.com/security/hsts-pixel.gif
h2
302.93599981815
354.36899983324
2485
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/hGJcREQrXhX.png
h2
324.80299985036
340.43499990366
30375
29213
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/ROJ_l_eUinL.js?_nc_x=Ij3Wp8lg5Kz
h2
420.92099995352
436.5009998437
23180
84972
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yv/r/cN-N4Eu_deZ.js?_nc_x=Ij3Wp8lg5Kz
h2
421.28099990077
435.66799978726
3485
7286
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yw/r/HuVQwJ6Qu6t.js?_nc_x=Ij3Wp8lg5Kz
h2
421.69799981639
437.01599980704
12358
37013
200
application/x-javascript
Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
455.84999979474
471.13499999978
417
79
200
image/png
Image
https://m.facebook.com/a/bz?fb_dtsg=AQHMfSXqyk94JyE%3A0%3A0&jazoest=21494&lsd=AVpfPQ1rYXM&__dyn=0wzpaBwk8aU4ifDg9ppk2m3q12wAxu13w9y1DxW0Oohx60kO4o3Bw4Ewk9E4W0om0MU0D2US0se229w6twdK0D81x82ew5fw5NyE&__csr=&__req=1&__a=AYlnnWxseMkYYiMk8bL9c8HGIPfdzXTvm_n_G4rq7bTFA_K229vGH6A8Z5rLmj-l1ngRko7SzOZqGGNfkEV1xm9fhyUChw_nJXHFvJXNbSciNA&__user=0
h2
1467.9309998173
1501.3899998739
2810
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
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images
Images can slow down the page's load time. Fecbook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fecbook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fecbook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fecbook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fecbook.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 — Potential savings of 15 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/hGJcREQrXhX.png
29213
15753
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://m.facebook.com/
126.143
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fecbook.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/yP/r/-oBflkGHHEM.js?_nc_x=Ij3Wp8lg5Kz
15740
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 292 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/yP/r/-oBflkGHHEM.js?_nc_x=Ij3Wp8lg5Kz
73145
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yY/l/en_US/oqLiJlt60SD.js?_nc_x=Ij3Wp8lg5Kz
51218
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/hGJcREQrXhX.png
30375
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/ROJ_l_eUinL.js?_nc_x=Ij3Wp8lg5Kz
23180
https://m.facebook.com/
18094
https://static.xx.fbcdn.net/rsrc.php/v3isIi4/yq/l/en_US/7xwPLIJREOG.js?_nc_x=Ij3Wp8lg5Kz
15609
https://static.xx.fbcdn.net/rsrc.php/v3/yB/r/QZnyh0f28Vs.js?_nc_x=Ij3Wp8lg5Kz
15411
https://static.xx.fbcdn.net/rsrc.php/v3/yw/r/HuVQwJ6Qu6t.js?_nc_x=Ij3Wp8lg5Kz
12358
https://static.xx.fbcdn.net/rsrc.php/v3/y7/r/PYgQcxUrcX_.js?_nc_x=Ij3Wp8lg5Kz
11130
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/UP7cGnAcBAF.js?_nc_x=Ij3Wp8lg5Kz
10502
Uses efficient cache policy on static assets — 0 resources found
Fecbook.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 — 80 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
80
Maximum DOM Depth
or
10
Maximum Child Elements
25
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. Fecbook.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
30.932
Rendering
1.072
Script Evaluation
0.088
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 — 22 requests • 292 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
22
299114
Script
11
221370
Image
3
33277
Stylesheet
4
22759
Document
1
18094
Other
3
3614
Media
0
0
Font
0
0
Third-party
18
275305
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.

Opportunities

Eliminate render-blocking resources — Potential savings of 450 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fecbook.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/yP/r/-oBflkGHHEM.js?_nc_x=Ij3Wp8lg5Kz
73145
450
Reduce unused JavaScript — Potential savings of 91 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/-oBflkGHHEM.js?_nc_x=Ij3Wp8lg5Kz
73145
38848
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yY/l/en_US/oqLiJlt60SD.js?_nc_x=Ij3Wp8lg5Kz
51218
33453
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/ROJ_l_eUinL.js?_nc_x=Ij3Wp8lg5Kz
23180
21123

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.3 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. Fecbook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://fecbook.com/
630
https://www.facebook.com/
780
https://m.facebook.com/
0
89

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fecbook.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"]`
Fecbook.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 fecbook.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://fecbook.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 fecbook.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 fecbook.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 fecbook.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 fecbook.com on mobile screens.

PWA Optimized

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

Manual Checks

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

Server Location

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

Web Hosting Provider

Name IP Address
Facebook, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
RegistrarSEC, LLC 192.0.66.80
Security

Visitor Safety

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

SSL/TLS Certificate

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

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

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jan 10 04:04:17.488 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:D3:74:46:99:93:95:2C:55:FB:E8:1A:
3F:1B:21:F4:78:94:D3:EF:DA:75:1E:B3:D1:68:EF:0F:
90:31:61:6E:FA:02:21:00:D8:A2:E0:71:60:47:80:E6:
10:99:21:92:2E:10:51:31:DC:4D:64:E1:AD:CD:A7:33:
3A:F2:38:0A:9E:18:7B:D7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jan 10 04:04:17.547 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:72:DA:81:A9:30:78:34:83:C8:30:E3:40:
69:8D:7F:CA:CE:83:DF:6E:81:7A:CF:7B:F4:2B:F1:78:
9C:74:35:F6:02:20:3A:01:4B:F1:00:87:50:4D:23:B8:
66:2A:D1:48:2C:DD:1F:B2:DB:37:D0:B8:0A:37:91:19:
7D:1F:F7:1E:67:0C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Jan 10 04:04:17.562 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:24:54:13:C9:4F:2E:F4:B0:92:3F:4C:18:
01:A8:4F:98:68:25:F0:15:2D:AF:64:A7:67:48:59:87:
3A:92:88:A0:02:20:2D:A7:A9:B7:2A:66:7F:36:CC:7C:
5E:70:B4:81:1D:7E:9A:28:76:F7:25:FC:F6:FE:48:8B:
3E:28:C1:38:E8:78
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
fecbook.com. 157.240.241.17 IN 300

NS Records

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

AAAA Records

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

SOA Records

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

TXT Records

Host Value Class TTL
fecbook.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: 9th March, 2023
Pragma: no-cache
content-security-policy: default-src data
report-to: {"max_age":86400,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reporting\/?minimize=0"}],"group":"coep_report"}, {"max_age":259200,"endpoints":[{"url":"https:\/\/www.facebook.com\/ajax\/browser_error_reports\/?device_level=unknown"}]}
cross-origin-embedder-policy-report-only: require-corp;report-to="coep_report"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
cross-origin-opener-policy: same-origin-allow-popups
Vary: Accept-Encoding
Strict-Transport-Security: max-age=15552000; preload
X-FB-Debug: p6FuUdD0hPOFKr8BC6v7KWqDn4nmNoDHtGMsfUb9I3OBl3U/0VBaslxAH7lI6JjdjE/6AIasj9RUwD+k3vYQ2A==
Transfer-Encoding: chunked
Alt-Svc: h3=":443"; ma=86400
Connection: keep-alive

Whois Lookup

Created: 27th January, 2012
Changed: 30th October, 2022
Expires: 27th January, 2024
Registrar: RegistrarSEC, LLC
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: a.ns.facebook.com
b.ns.facebook.com
c.ns.facebook.com
d.ns.facebook.com
Owner Name: Domain Admin
Owner Organization: Meta Platforms, Inc.
Owner Street: 1601 Willow Rd
Owner Post Code: 94025
Owner City: Menlo Park
Owner State: CA
Owner Country: US
Owner Phone: +1.6505434800
Owner Email: domain@fb.com
Admin Name: Domain Admin
Admin Organization: Meta Platforms, Inc.
Admin Street: 1601 Willow Rd
Admin Post Code: 94025
Admin City: Menlo Park
Admin State: CA
Admin Country: US
Admin Phone: +1.6505434800
Admin Email: domain@fb.com
Tech Name: Domain Admin
Tech Organization: Meta Platforms, Inc.
Tech Street: 1601 Willow Rd
Tech Post Code: 94025
Tech City: Menlo Park
Tech State: CA
Tech Country: US
Tech Phone: +1.6505434800
Tech Email: domain@fb.com
Full Whois: Domain Name: FECBOOK.COM
Registry Domain ID: 1699042503_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrarsec.com
Registrar URL: https://www.registrarsec.com
Updated Date: 2022-10-30T09:00:22Z
Creation Date: 2012-01-27T19:20:06Z
Registrar Registration Expiration Date: 2024-01-27T19:20:06Z
Registrar: RegistrarSEC, LLC
Registrar IANA ID: 2475
Registrar Abuse Contact Email: abusecomplaints@registrarsec.com
Registrar Abuse Contact Phone: +1.6503087004
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited
Registry Registrant ID:
Registrant Name: Domain Admin
Registrant Organization: Meta Platforms, Inc.
Registrant Street: 1601 Willow Rd
Registrant City: Menlo Park
Registrant State/Province: CA
Registrant Postal Code: 94025
Registrant Country: US
Registrant Phone: +1.6505434800
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: domain@fb.com
Registry Admin ID:
Admin Name: Domain Admin
Admin Organization: Meta Platforms, Inc.
Admin Street: 1601 Willow Rd
Admin City: Menlo Park
Admin State/Province: CA
Admin Postal Code: 94025
Admin Country: US
Admin Phone: +1.6505434800
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: domain@fb.com
Registry Tech ID:
Tech Name: Domain Admin
Tech Organization: Meta Platforms, Inc.
Tech Street: 1601 Willow Rd
Tech City: Menlo Park
Tech State/Province: CA
Tech Postal Code: 94025
Tech Country: US
Tech Phone: +1.6505434800
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: domain@fb.com
Name Server: D.NS.FACEBOOK.COM
Name Server: A.NS.FACEBOOK.COM
Name Server: 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: 2023-03-09T09:37:36Z <<<

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

Domain Subdomain
m
mbasic

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address

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