Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

facebook.com

facebook.com is SSL secured

Free website and domain report on facebook.com

Last Updated: 18th April, 2024
Overview

Snoop Summary for facebook.com

This is a free and comprehensive report about facebook.com. Our records indicate that facebook.com is owned/operated by Meta Platforms, Inc.. Facebook.com is expected to earn an estimated $3,137,362 USD per day from advertising revenue. The sale of facebook.com would possibly be worth $2,290,274,603 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Facebook.com receives an estimated 227,087,189 unique visitors every day - an unbelievable amount of traffic! This report was last updated 18th April, 2024.

About facebook.com

Site Preview: facebook.com facebook.com
Title: Facebook
Description: A social utility that connects people, to keep up with friends, upload photos, share links and videos.
Keywords and Tags: amazon, f, face, facebook, facebook com, facebook com login, facebook log in, facebook login, facebook marketplace, facebook sign in, fb, kobe bryant, social networking, www facebook com, yahoo, youtube
Related Terms: connects
Fav Icon:
Age: Over 27 years old
Domain Created: 29th March, 1997
Domain Updated: 26th April, 2023
Domain Expires: 30th March, 2032
Review

Snoop Score

5/5 (Perfect!)

Valuation

$2,290,274,603 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 4
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score: 96
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords:
Traffic:
Cost:
Traffic

Visitors

Daily Visitors: 227,087,189
Monthly Visitors: 6,911,818,686
Yearly Visitors: 82,886,823,985
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $3,137,362 USD
Monthly Revenue: $95,491,430 USD
Yearly Revenue: $1,145,137,297 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 50,043,085,709
Referring Domains: 27,999,786
Referring IPs: 4,325,895
Facebook.com has 50,043,085,709 backlinks according to SEMrush. 75% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve facebook.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
99% of facebook.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://www.idosell.com/pl/shop/
Target: https://www.facebook.com/IAISA.fp/
2
Source: https://careerbuilder.vn/
Target: https://www.facebook.com/pages/CareerBuilder-Vietnam/265321726945679?ref=tn_tnmn
3
Source: https://www.perforce.com/message-our-customers
Target: https://www.facebook.com/Perforce/
4
Source: https://b.hatena.ne.jp/
Target: https://www.facebook.com/kunihiko.kooguchi/posts/covid-19%E8%82%BA%E7%82%8E%E3%81%AB%E5%AF%BE%E3%81%97%E3%81%A6%E3%81%AE%E4%BA%BA%E5%B7%A5%E8%82%BA%E3%82%A8%E3%82%AF%E3%83%A2ecmo%E3%81%8C%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9%E3%81%A7%E3%81%A8%E3%82%8A%E3%81%82%E3%81%92%E3%82%89%E3%82%8C%E3%82%8B%E3%81%93%E3%81%A8%E3%81%8C%E5%A2%97%E3%81%88%E3%81%BE%E3%81%97%E3%81%9F%E3%81%8A%E3%81%9D%E3%82%8D%E3%81%97%E3%81%84%E6%95%B0%E3%82%92%E5%85%A8%E5%9B%BD%E3%81%AB%E9%85%8D%E3%82%8B%E3%83%97%E3%83%A9%E3%83%B3%E3%81%BE%E3%81%A7%E3%81%82%E3%82%8B%E3%82%88%E3%81%86%E3%81%A7%E3%81%99%E3%81%BE%E3%82%8B%E3%81%A7%E9%87%8D%E7%97%87%E8%82%BA%E7%82%8E%E3%81%AB%E5%AF%BE%E3%81%97%E3%81%A6/2458443127590682/
5
Source: https://b.hatena.ne.jp/
Target: https://www.facebook.com/kunihiko.kooguchi/posts/covid-19%E8%82%BA%E7%82%8E%E3%81%AB%E5%AF%BE%E3%81%97%E3%81%A6%E3%81%AE%E4%BA%BA%E5%B7%A5%E8%82%BA%E3%82%A8%E3%82%AF%E3%83%A2ecmo%E3%81%8C%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9%E3%81%A7%E3%81%A8%E3%82%8A%E3%81%82%E3%81%92%E3%82%89%E3%82%8C%E3%82%8B%E3%81%93%E3%81%A8%E3%81%8C%E5%A2%97%E3%81%88%E3%81%BE%E3%81%97%E3%81%9F%E3%81%8A%E3%81%9D%E3%82%8D%E3%81%97%E3%81%84%E6%95%B0%E3%82%92%E5%85%A8%E5%9B%BD%E3%81%AB%E9%85%8D%E3%82%8B%E3%83%97%E3%83%A9%E3%83%B3%E3%81%BE%E3%81%A7%E3%81%82%E3%82%8B%E3%82%88%E3%81%86%E3%81%A7%E3%81%99%E3%81%BE%E3%82%8B%E3%81%A7%E9%87%8D%E7%97%87%E8%82%BA%E7%82%8E%E3%81%AB%E5%AF%BE%E3%81%97%E3%81%A6/2458443127590682/

Top Ranking Keywords (US)

1
Keyword: facebook
Ranked Page: https://www.facebook.com/
2
Keyword: facebook login
Ranked Page: https://en-gb.facebook.com/login/
3
Keyword: facebook log in
Ranked Page: https://www.facebook.com/
4
Keyword: fb
Ranked Page: https://www.facebook.com/
5
Keyword: face
Ranked Page: https://www.facebook.com/

Domain Analysis

Value Length
Domain: facebook.com 12
Domain Name: facebook 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 3.41 seconds
Load Time Comparison: Faster than 14% of sites

PageSpeed Insights

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

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

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

Simulate loading on desktop
97

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://facebook.com/
http/1.1
0
25.691000046209
259
0
301
text/plain
https://facebook.com/
http/1.1
26.192000019364
82.564000040293
446
0
301
text/html
https://www.facebook.com/
h2
83.010000060312
197.7290000068
23792
64413
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/y4/l/0,cross/ZtwO7u3tI0A.css?_nc_x=Ij3Wp8lg5Kz
h2
240.53900002036
255.44600002468
4109
14025
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yk/l/0,cross/sSlfrJnWhMb.css?_nc_x=Ij3Wp8lg5Kz
h2
242.60400002822
258.8870000327
3823
10851
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yz/l/0,cross/B3Sgte-nqm6.css?_nc_x=Ij3Wp8lg5Kz
h2
242.77900008019
259.41100006457
8553
35302
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yI/l/0,cross/b58lhXKrxe_.css?_nc_x=Ij3Wp8lg5Kz
h2
242.94000002556
258.12000001315
1833
5034
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yr/l/0,cross/u4xvA0Tw-4L.css?_nc_x=Ij3Wp8lg5Kz
h2
243.10199997853
258.53400002234
1102
1225
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
h2
243.28200006858
267.35800004099
95149
370589
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
h2
340.44800000265
355.07699998561
1708
2385
200
image/svg+xml
Image
https://facebook.com/security/hsts-pixel.gif
h2
340.64700000454
450.91200002935
3883
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yl/r/lP3xlXBlUds.js?_nc_x=Ij3Wp8lg5Kz
h2
261.6440000711
276.42000000924
1002
735
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y-/r/qu9vi-bmWl3.js?_nc_x=Ij3Wp8lg5Kz
h2
278.69900001679
294.38500001561
3616
8492
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/y3/l/en_US/HtnbT366ZD_.js?_nc_x=Ij3Wp8lg5Kz
h2
297.26500005927
312.54100007936
16513
61549
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/sczXDyPA0UL.js?_nc_x=Ij3Wp8lg5Kz
h2
300.33200001344
314.99099999201
942
435
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yL/r/W6WQVqzvdrq.js?_nc_x=Ij3Wp8lg5Kz
h2
340.00800002832
356.19199997745
11740
35496
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yd/r/LFJDMBbOfee.js?_nc_x=Ij3Wp8lg5Kz
h2
340.27000004426
355.74500006624
7993
22865
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yU/r/O7nelmd9XSI.png
h2
348.21600001305
361.89800000284
725
95
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yr/r/FqnMzVyVHVQ.png
h2
349.58100004587
363.30099997576
20832
20216
200
image/png
Image
data
440.57700003032
440.76200004201
0
0
200
text/css
Stylesheet
data
440.91900007334
441.10100006219
0
78
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/p0bcnVbl1Lr.js?_nc_x=Ij3Wp8lg5Kz
h2
489.54099998809
505.35800005309
11999
35053
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/mgxJrPv-D2y.js?_nc_x=Ij3Wp8lg5Kz
h2
490.98700005561
507.41000007838
7855
21446
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/j_uHdvkyoIZ.js?_nc_x=Ij3Wp8lg5Kz
h2
491.16299999878
506.98900001589
4634
9840
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/M08arqdo_nN.js?_nc_x=Ij3Wp8lg5Kz
h2
495.49700005446
516.79500006139
1440
1622
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/lS9_2HUikEH.js?_nc_x=Ij3Wp8lg5Kz
h2
496.51299999095
517.41700002458
10292
30283
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yN/r/APH-FcpdMJY.js?_nc_x=Ij3Wp8lg5Kz
h2
497.03900003806
518.49699998274
9892
33047
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
h2
497.79599998146
517.97799998894
13719
43510
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/_tJ17sGyxOX.js?_nc_x=Ij3Wp8lg5Kz
h2
501.56800006516
525.51100007258
8201
18154
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
h2
501.96500006132
519.25400004257
9993
50828
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/y_/l/en_US/LHUxA4o6J25.js?_nc_x=Ij3Wp8lg5Kz
h2
502.85799999256
519.71100002993
14118
43610
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y0/r/_RNmJ6y0L6_.js?_nc_x=Ij3Wp8lg5Kz
h2
504.18200006243
520.18099999987
1273
1385
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yr/r/4wltOmgbysb.js?_nc_x=Ij3Wp8lg5Kz
h2
504.74600004964
520.58900007978
5972
18700
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yI/r/AUxLYgKu2ko.js?_nc_x=Ij3Wp8lg5Kz
h2
505.04000007641
520.94800001942
2797
6318
200
application/x-javascript
Script
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU29zEdEc8uwdK0lW4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwnU1oU884y0lW0ny0RE2Jw8W0iW0lK3qaw4kwbS1Lw4Cw&__hs=19356.BP%3ADEFAULT.2.0.0.0.0&__hsi=7183031623272459926&__req=1&__rev=1006773923&__s=o2fzwf%3Azsq8tp%3Ay136dn&__spin_b=trunk&__spin_r=1006773923&__spin_t=1672429876&__user=0&dpr=1&jazoest=2905&lsd=AVpp2FXC1ck
h2
633.77200008836
710.53899999242
4086
0
200
text/html
XHR
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__dyn=7xe6E5aQ1PyUbFuC1swgE98nwgU29zEdEc8uwdK0lW4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwnU1oU884y0lW0ny0RE2Jw8W0iW0lK3qaw4kwbS1Lw4Cw&__hs=19356.BP%3ADEFAULT.2.0.0.0.0&__hsi=7183031623272459926&__req=2&__rev=1006773923&__s=o2fzwf%3Azsq8tp%3Ay136dn&__spin_b=trunk&__spin_r=1006773923&__spin_t=1672429876&__user=0&dpr=1&jazoest=2905&lsd=AVpp2FXC1ck
h2
1601.0040000547
1652.762999991
4069
0
200
text/html
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
243.486
3727.131
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Facebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facebook.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facebook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 49 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
95149
50112
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 13 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yr/r/FqnMzVyVHVQ.png
20216
13165.7
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.713
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facebook.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
13803
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
0
Avoids enormous network payloads — Total size was 311 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
95149
https://www.facebook.com/
23792
https://static.xx.fbcdn.net/rsrc.php/v3/yr/r/FqnMzVyVHVQ.png
20832
https://static.xx.fbcdn.net/rsrc.php/v3i7M54/y3/l/en_US/HtnbT366ZD_.js?_nc_x=Ij3Wp8lg5Kz
16513
https://static.xx.fbcdn.net/rsrc.php/v3iqES4/y_/l/en_US/LHUxA4o6J25.js?_nc_x=Ij3Wp8lg5Kz
14118
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
13719
https://static.xx.fbcdn.net/rsrc.php/v3/yC/r/p0bcnVbl1Lr.js?_nc_x=Ij3Wp8lg5Kz
11999
https://static.xx.fbcdn.net/rsrc.php/v3/yL/r/W6WQVqzvdrq.js?_nc_x=Ij3Wp8lg5Kz
11740
https://static.xx.fbcdn.net/rsrc.php/v3/ye/r/lS9_2HUikEH.js?_nc_x=Ij3Wp8lg5Kz
10292
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
9993
Uses efficient cache policy on static assets — 0 resources found
Facebook.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 — 160 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
160
Maximum DOM Depth
div#u_0_3_A/ > a > div._9lsa > div#u_0_4_nE
18
Maximum Child Elements
Sign UpLog InMessengerFacebook LiteWatchPlacesGamesMarketplaceMeta PayOculusPor…
31
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Facebook.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
3732.428
0.045
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 • 311 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
318360
Script
20
239140
Image
4
27148
Document
1
23792
Stylesheet
5
19420
Other
4
8860
Media
0
0
Font
0
0
Third-party
28
281825
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
Facebook
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Facebook
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

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

Metrics

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

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 350 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Facebook.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static.xx.fbcdn.net/rsrc.php/v3/y4/l/0,cross/ZtwO7u3tI0A.css?_nc_x=Ij3Wp8lg5Kz
4109
230
https://static.xx.fbcdn.net/rsrc.php/v3/yK/r/mHzUmnUOXQN.js?_nc_x=Ij3Wp8lg5Kz
95149
80
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Facebook.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://facebook.com/
190
https://facebook.com/
150
https://www.facebook.com/
0
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
3732.306
Rendering
0.077
Script Evaluation
0.045

Other

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

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

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

Mobile Friendly

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

Crawling and Indexing

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

Manual Checks

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

PWA

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

Installable

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

PWA Optimized

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of facebook.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) 76
Performance 79
Accessibility 83
Best Practices 75
SEO 82
PWA 60
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://m.facebook.com/
Updated: 30th December, 2022

1.84 seconds
First Contentful Paint (FCP)
75%
15%
10%

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

Simulate loading on mobile
79

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://facebook.com/
http/1.1
0
6.7920000292361
241
0
301
text/plain
https://facebook.com/
http/1.1
7.1379999862984
70.032999967225
448
0
301
text/html
https://m.facebook.com/
h2
70.372999995016
283.77099998761
24212
56516
200
text/html
Document
https://static.xx.fbcdn.net/rsrc.php/v3/yH/l/0,cross/8pbaT5LFcxq.css?_nc_x=Ij3Wp8lg5Kz
h2
326.53700001538
336.74499997869
3980
14472
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/y6/l/0,cross/hO7IhVa-nO2.css?_nc_x=Ij3Wp8lg5Kz
h2
326.83899998665
334.5519999275
8940
40364
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yS/l/0,cross/BCtJMrkSMbV.css?_nc_x=Ij3Wp8lg5Kz
h2
327.05600000918
337.97599992249
13577
53370
200
text/css
Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
h2
327.25199998822
341.67300001718
79168
311433
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/y8/r/dF5SId3UHWd.svg
h2
383.49899998866
390.39199997205
1708
2385
200
image/svg+xml
Image
https://facebook.com/security/hsts-pixel.gif
h2
383.62099998631
481.98799998499
3856
43
200
image/gif
Image
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
h2
342.9649999598
351.84699995443
50935
181945
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/tttf5FDK7WA.js?_nc_x=Ij3Wp8lg5Kz
h2
366.9359999476
373.42199997511
13796
44468
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yu/r/4z8at6z2jaS.js?_nc_x=Ij3Wp8lg5Kz
h2
368.43599996064
374.73199993838
11424
36060
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/LqXI6W_bsOb.js?_nc_x=Ij3Wp8lg5Kz
h2
383.32299992908
388.66299996153
9215
26709
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y3/r/cvj8rfO8RgU.png
h2
387.61199999135
392.40100001916
4036
3404
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yi/r/HoeIqiP3dNO.png
h2
444.25699999556
450.83500002511
81651
81018
200
image/png
Image
https://static.xx.fbcdn.net/rsrc.php/v3/yY/r/ue_OWlkLDZP.js?_nc_x=Ij3Wp8lg5Kz
h2
533.33200002089
540.92900000978
9979
50828
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yO/r/_tJ17sGyxOX.js?_nc_x=Ij3Wp8lg5Kz
h2
533.72700000182
538.54099998716
8187
18154
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yT/r/OQ2NlcQEZ4F.js?_nc_x=Ij3Wp8lg5Kz
h2
534.16799998377
545.81599996891
9064
27129
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iL7o4/yq/l/en_US/Rssvn-MfGxr.js?_nc_x=Ij3Wp8lg5Kz
h2
534.6529999515
550.15399993863
12641
36341
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/KKlvRURRLk8.js?_nc_x=Ij3Wp8lg5Kz
h2
536.93299996667
548.42799995095
6848
17749
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3ih-D4/yM/l/en_US/yaw05i6HDSf.js?_nc_x=Ij3Wp8lg5Kz
h2
537.2910000151
552.36500001047
19177
78246
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
h2
537.79800003394
551.8049999373
13705
43510
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iLQG4/yv/l/en_US/Sa1jhi1-Bt9.js?_nc_x=Ij3Wp8lg5Kz
h2
538.38899999391
553.39499993715
11048
39106
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yn/r/lNCIXQG6fuL.js?_nc_x=Ij3Wp8lg5Kz
h2
538.97200000938
553.74100001063
8786
23738
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3iLl54/yK/l/en_US/0D75Vw0sOuD.js?_nc_x=Ij3Wp8lg5Kz
h2
539.41199998371
554.03200001456
3963
8771
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/yg/r/GaT0-DQJdWD.js?_nc_x=Ij3Wp8lg5Kz
h2
539.87999993842
552.86599998362
863
313
200
application/x-javascript
Script
https://static.xx.fbcdn.net/rsrc.php/v3/y9/r/ie38mp0O07P.js?_nc_x=Ij3Wp8lg5Kz
h2
540.42199999094
554.35999995098
11098
25101
200
application/x-javascript
Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png
h2
636.325999978
640.50500001758
384
79
200
image/png
Image
https://m.facebook.com/a/bz?fb_dtsg=NAcOlXRLkBx52n4M3yaULqz3GKQn5QSnWB3n8g0GSgKfQSxbknTpoeQ%3A0%3A0&jazoest=24945&lsd=AVpZYGkgO8U&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=1&__a=AYkd0cwmZf8OKmTO0tLnoTenvmPQJ6XDC5mOEoCOOk38sm8G9sTn_xljXecpbvbHqf62B5i7I92VzT9vxoHqH4J3LK2sNUVwhAzkmJ6pPZcrRQ&__user=0
h2
673.96199994255
703.54899996892
4452
249
200
application/x-javascript
XHR
https://m.facebook.com/a/bz?fb_dtsg=NAcOlXRLkBx52n4M3yaULqz3GKQn5QSnWB3n8g0GSgKfQSxbknTpoeQ%3A0%3A0&jazoest=24945&lsd=AVpZYGkgO8U&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=2&__a=AYkd0cwmZf8OKmTO0tLnoTenvmPQJ6XDC5mOEoCOOk38sm8G9sTn_xljXecpbvbHqf62B5i7I92VzT9vxoHqH4J3LK2sNUVwhAzkmJ6pPZcrRQ&__user=0
h2
697.19700003043
730.97799997777
4435
249
200
application/x-javascript
XHR
https://m.facebook.com/data/manifest/
h2
700.42599993758
766.14800002426
4427
954
200
application/json
Manifest
https://m.facebook.com/a/bz?fb_dtsg=NAcOlXRLkBx52n4M3yaULqz3GKQn5QSnWB3n8g0GSgKfQSxbknTpoeQ%3A0%3A0&jazoest=24945&lsd=AVpZYGkgO8U&__dyn=1KidAG1mwHwh8-t0BBBg9odE4a2i5U4e0C86u7E39x60lW4o3Bw4Ewk9E4W0Io3jwce09MKdw73wwyo1Do1u86i0h-0zE1bE881eEdEG0hi0Lo6-0Co2cw8-&__csr=&__req=3&__a=AYkd0cwmZf8OKmTO0tLnoTenvmPQJ6XDC5mOEoCOOk38sm8G9sTn_xljXecpbvbHqf62B5i7I92VzT9vxoHqH4J3LK2sNUVwhAzkmJ6pPZcrRQ&__user=0
h2
1668.1470000185
1693.8389999559
4452
249
200
application/x-javascript
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Facebook.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facebook.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facebook.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facebook.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 210 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://m.facebook.com/
214.393
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facebook.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 430 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yi/r/HoeIqiP3dNO.png
81651
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
79168
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
50935
https://m.facebook.com/
24212
https://static.xx.fbcdn.net/rsrc.php/v3ih-D4/yM/l/en_US/yaw05i6HDSf.js?_nc_x=Ij3Wp8lg5Kz
19177
https://static.xx.fbcdn.net/rsrc.php/v3/y2/r/tttf5FDK7WA.js?_nc_x=Ij3Wp8lg5Kz
13796
https://static.xx.fbcdn.net/rsrc.php/v3/yf/r/LgvwffuKmeX.js?_nc_x=Ij3Wp8lg5Kz
13705
https://static.xx.fbcdn.net/rsrc.php/v3/yS/l/0,cross/BCtJMrkSMbV.css?_nc_x=Ij3Wp8lg5Kz
13577
https://static.xx.fbcdn.net/rsrc.php/v3iL7o4/yq/l/en_US/Rssvn-MfGxr.js?_nc_x=Ij3Wp8lg5Kz
12641
https://static.xx.fbcdn.net/rsrc.php/v3/yu/r/4z8at6z2jaS.js?_nc_x=Ij3Wp8lg5Kz
11424
Uses efficient cache policy on static assets — 0 resources found
Facebook.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 196 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
196
Maximum DOM Depth
HIDE
20
Maximum Child Elements
Log in
23
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Facebook.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
31.452
Rendering
0.24
Script Evaluation
0.128
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 32 requests • 430 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
440696
Script
17
279897
Image
5
91635
Stylesheet
3
26497
Document
1
24212
Other
6
18455
Media
0
0
Font
0
0
Third-party
24
394173
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
Get Facebook for Android and browse faster.
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of facebook.com on mobile screens.

Budgets

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

Metrics

Speed Index — 3.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.107
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

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

Other

Reduce unused CSS — Potential savings of 12 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facebook.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yS/l/0,cross/BCtJMrkSMbV.css?_nc_x=Ij3Wp8lg5Kz
13577
12239
Reduce unused JavaScript — Potential savings of 71 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
79168
40260
https://static.xx.fbcdn.net/rsrc.php/v3iZkm4/yB/l/en_US/Ozv8GA-bKfD.js?_nc_x=Ij3Wp8lg5Kz
50935
32077
Serve images in next-gen formats — Potential savings of 54 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yi/r/HoeIqiP3dNO.png
81018
55594.2
Avoid serving legacy JavaScript to modern browsers — Potential savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/ljsc1_0R9P-.js?_nc_x=Ij3Wp8lg5Kz
13666

Metrics

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

Other

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

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

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

Best practices

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

Audio and video

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

ARIA

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

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
Create new account
English (US)
About
Help
More
Meta © 2022

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
head > meta

Manual Checks

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

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

Audits

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

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for facebook.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 facebook.com on mobile screens.
Document uses legible font sizes — 93.3% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
SHOW DETAILS
._96qw
6.70%
10px
SHOW DETAILS
93.30%
≥ 12px

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 56% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
Deutsch
44x14
Complete list of languages
Italiano
38x14
Português (Brasil)
Español
43x14
中文(简体)
Deutsch
44x14
中文(简体)
Français (France)
94x14
Português (Brasil)

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
SHOW DETAILS

Manual Checks

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

PWA

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

Installable

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

PWA Optimized

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of facebook.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.202.35
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

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
RegistrarSafe, LLC 157.240.202.35
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.facebook.com
Issued By: DigiCert SHA2 High Assurance Server CA
Valid From: 26th January, 2024
Valid To: 25th April, 2024
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: 2780746819825333804249901050007771869
Serial Number (Hex): 02178D67417200D81A7F44272FE5DADD
Valid From: 26th January, 2024
Valid To: 25th April, 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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Jan 26 00:25:19.277 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:5A:65:24:22:78:2C:33:A9:C3:F5:CA:90:
90:36:25:39:5D:3A:6A:6E:7D:F2:9F:2D:5E:78:38:74:
7C:3B:AC:BE:02:21:00:FD:C5:B8:73:0B:39:E8:10:9C:
A0:65:CB:A4:7A:5A:B0:4E:E0:57:56:84:96:4D:6C:C8:
C7:B1:72:65:3F:DF:89
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Jan 26 00:25:19.283 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:A3:AA:13:D2:91:72:F2:E3:BD:67:00:
FA:79:FE:CC:D3:7A:07:30:06:00:B9:94:8D:B8:9A:76:
A7:99:0A:BD:AC:02:20:6B:DF:0D:6A:14:27:1D:9D:D2:
58:6E:4A:84:01:AC:B1:D6:22:C5:57:F3:4F:77:10:D7:
CA:83:05:A9:6C:B8:71
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Jan 26 00:25:19.268 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C0:B9:87:D6:75:7A:B3:6B:83:0B:80:
96:51:7E:D7:A2:C9:43:27:EA:B1:14:D8:90:EA:07:15:
85:A9:E5:D2:DD:02:20:41:DF:E4:96:D3:9D:BC:06:7B:
69:30:24:F7:99:0D:95:FB:C1:2F:A3:53:94:2D:79:B8:
C8:17:DD:09:5D:B8:7E
Key Usage: Digital Signature, Key Agreement
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
facebook.com. 157.240.241.35 IN 300

NS Records

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

AAAA Records

IP Address Class TTL
2a03:2880:f112:182:face:b00c:0:25de IN 300

CAA Records

Domain Flags Tag Class TTL
digicert.com 0 issue IN 3600

MX Records

Priority Host Server Class TTL
10 facebook.com. smtpin.vvv.facebook.com. IN 3600

SOA Records

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

TXT Records

Host Value Class TTL
facebook.com. google-site-verification=wdH5DTJTc9AYNwVunSVFeK0hYDGUIEOGb-RReU6pJlY IN 7200
facebook.com. v=spf1 IN 21600
facebook.com. google-site-verification=sK6uY9x7eaMoEMfn3OILqwTFYgaNp4llmguKI-C3_iA IN 7200
facebook.com. google-site-verification=A2WZWCNQHrGV_TWwKh6KHY90tY0SHZo_RnyMJoDaG0s IN 7200
facebook.com. zoom-domain-verification=a6c90d61-66ec-485c-9f3d-cce7036f01bb IN 3600

HTTP Response Headers

HTTP-Code: HTTP/2 301
content-type: text/html; charset="utf-8"
date: 18th April, 2024
location: https://www.facebook.com/
strict-transport-security: max-age=15552000; includeSubDomains
x-fb-debug: 3PSahV/1Fg/qxEnUGazrHKlSqiFoKS9UclNMxpxZCa6qb1ChKJ1wWFpuWj2nCS6o1x2GTBotmpkrfIS0RE6MQw==
content-length: 0
x-fb-connection-quality: GOOD; q=0.7, rtt=77, rtx=0, c=10, mss=1380, tbw=3533, tp=-1, tpl=-1, uplat=32, ullat=0
alt-svc: h3=":443"; ma=86400

Whois Lookup

Created: 29th March, 1997
Changed: 26th April, 2023
Expires: 30th March, 2032
Registrar: RegistrarSafe, LLC
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
serverDeleteProhibited
serverTransferProhibited
serverUpdateProhibited
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: FACEBOOK.COM
Registry Domain ID: 2320948_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrarsafe.com
Registrar URL: https://www.registrarsafe.com
Updated Date: 2023-04-26T19:04:19Z
Creation Date: 1997-03-29T05:00:00Z
Registrar Registration Expiration Date: 2032-03-30T04:00:00Z
Registrar: RegistrarSafe, LLC
Registrar IANA ID: 3237
Registrar Abuse Contact Email: abusecomplaints@registrarsafe.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
Domain Status: serverDeleteProhibited https://www.icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://www.icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://www.icann.org/epp#serverUpdateProhibited
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: 2024-04-18T03:28:10Z <<<

Search results obtained from the RegistrarSafe, LLC WHOIS database are
provided by RegistrarSafe, 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 RegistrarSafe, 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 RegistrarSafe, LLC or
its systems. RegistrarSafe, 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.
View Raw Whois

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
0.facebook.com
0
about.facebook.com
about
api.facebook.com
api
app.facebook.com
app
apps.facebook.com
apps
All facebook.com subdomains

Similar Sites

Domain Valuation Snoop Score
blogger.com
$73,537,675 USD 5/5
ebay.com
$377,760,287 USD 5/5
flickr.com
$46,743,464 USD 5/5
friendster.com
$971 USD 1/5
google.com
$4,794,933,151 USD 5/5
All sites similar to facebook.com

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
facebook.cn
0/5
facebook.de
$4,498 USD 2/5
facebook.net
$12,553 USD 3/5
facebook.org
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
fbsbx.com
0/5
Love W3 Snoop?
Update Now

facebook.com Infographic

facebook.com by the numbers infographic

Recently Updated

computersadda.com
creepshots.org
ponyking.com
kupatana.com
mcleodgaming.com
rollyrol.com
flamecomics.com
lottele.com
ambidupdate.com
character.ai

Recently Viewed

edocourier.com
fabrictech.com
thecityoflights.net
cosmeticare.com
szbbw.net
svcic.com
anotherblink.net
tvdir.net
ziggytv.com
fgbss.com