Tools & Wizards About Us
facebook.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

facebook.com

Log into Facebook

Page Load Speed

910 ms in total

First Response

93 ms

Resources Loaded

669 ms

Page Rendered

148 ms

facebook.com screenshot

About Website

Click here to check amazing Facebook content for United States. Otherwise, check out these important facts you probably never knew about facebook.com

Log into Facebook to start sharing and connecting with your friends, family, and people you know.

Visit facebook.com

Key Findings

We analyzed Facebook.com page load time and found that the first response time was 93 ms and then it took 817 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

facebook.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value6.7 s

57/100

10%

Network Requests Diagram

www.facebook.com

93 ms

qfACu27MZMx.css

32 ms

_Vf1AJSPkwU.css

36 ms

Xyoav1gLypl.css

39 ms

NjbrxAY96GS.css

43 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Facebook.com, 87% (27 requests) were made to Static.xx.fbcdn.net and 6% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (118 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.3 kB (64%)

Content Size

70.9 kB

After Optimization

25.6 kB

  • HTML
  • Images

In fact, the total size of Facebook.com main page is 70.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 64.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 45.3 kB

  • Original 64.0 kB
  • After minification 64.0 kB
  • After compression 18.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.3 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 6.8 kB
  • After minification 6.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Facebook images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 22 (79%)

Requests Now

28

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facebook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.facebook.com

www.facebook.com

93 ms

qfACu27MZMx.css

qfACu27MZMx.css

32 ms

_Vf1AJSPkwU.css

_Vf1AJSPkwU.css

36 ms

Xyoav1gLypl.css

Xyoav1gLypl.css

39 ms

NjbrxAY96GS.css

NjbrxAY96GS.css

43 ms

A3tiDdwKtg5.css

A3tiDdwKtg5.css

36 ms

qczqs7QMr3-.js

qczqs7QMr3-.js

49 ms

xGzxHIbkRpC.js

xGzxHIbkRpC.js

19 ms

Br6EHF-GHmg.js

Br6EHF-GHmg.js

16 ms

css;base64,

css;base64,

8 ms

css;%20charset=utf-8;base64,I2Jvb3Rsb2FkZXJfUF9tcjVWRXtoZWlnaHQ6NDJweDt9LmJvb3Rsb2FkZXJfUF9tcjVWRXtkaXNwbGF5OmJsb2NrIWltcG9ydGFudDt9

css;%20charset=utf-8;base64,I2Jvb3Rsb2FkZXJfUF9tcjVWRXtoZWlnaHQ6NDJweDt9LmJvb3Rsb2FkZXJfUF9tcjVWRXtkaXNwbGF5OmJsb2NrIWltcG9ydGFudDt9

8 ms

GIlJjyzEguQ.js

GIlJjyzEguQ.js

16 ms

4lCu2zih0ca.svg

4lCu2zih0ca.svg

19 ms

O7nelmd9XSI.png

O7nelmd9XSI.png

15 ms

Y0L6f5sxdIV.png

Y0L6f5sxdIV.png

18 ms

RKK6hMCj3R1.js

RKK6hMCj3R1.js

73 ms

6bjw9N12j0I.js

6bjw9N12j0I.js

39 ms

CbM6CZG2ZAb.js

CbM6CZG2ZAb.js

27 ms

HtdXy-2D6mm.js

HtdXy-2D6mm.js

38 ms

3FPJ9YC_wUr.js

3FPJ9YC_wUr.js

38 ms

M08arqdo_nN.js

M08arqdo_nN.js

30 ms

_BJqgRg0BU5.js

_BJqgRg0BU5.js

30 ms

sKtrEJAtiUM.js

sKtrEJAtiUM.js

34 ms

qvzskUrYlYC.js

qvzskUrYlYC.js

31 ms

lFK_RCKM9IT.js

lFK_RCKM9IT.js

32 ms

Atn6-5S2M-o.js

Atn6-5S2M-o.js

39 ms

Jn0xcQmjzFV.js

Jn0xcQmjzFV.js

35 ms

Ch_YChJCKQS.js

Ch_YChJCKQS.js

34 ms

ysfm_2i9xtW.js

ysfm_2i9xtW.js

34 ms

LDFDUeRDitE.js

LDFDUeRDitE.js

118 ms

hsts-pixel.gif

hsts-pixel.gif

17 ms

Accessibility Review

facebook.com accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

facebook.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

facebook.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facebook.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Facebook.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

facebook.com

Open Graph description is not detected on the main page of Facebook. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: