Facebook - Log In or Sign Up

Overview

Snoop Summary for facebook.co

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

About facebook.co

Site Preview:
Title:	Facebook - Log In or Sign Up
Description:	Log into Facebook to start sharing and connecting with your friends, family, and people you know.
Keywords and Tags:	entertainment, popular
Related Terms:	24 energa log, aqu log..., bankia log in, bicupid com log in, cbs log, crontab log, edsby log in, fuegodevida com log in, kinnser log in, moodle log in
Fav Icon:
Age:	Over 14 years old
Domain Created:	23rd April, 2010
Domain Updated:	27th May, 2020
Domain Expires:	22nd April, 2022

Review

Snoop Score

2/5

Valuation

$959 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	1,847,279
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	456
Monthly Visitors:	13,879
Yearly Visitors:	166,440

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$1 USD
Monthly Revenue:	$40 USD
Yearly Revenue:	$474 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	facebook.co	11
Domain Name:	facebook	8
Extension (TLD):	co	2

Expiry Check:

Page Speed Analysis

Average Load Time:	1.54 seconds
Load Time Comparison:	Faster than 55% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://www.facebook.com/

Updated: 15th July, 2021

4.30 seconds

First Contentful Paint (FCP)

22%

33%

45%

0.02 seconds

First Input Delay (FID)

93%

5%

2%

Simulate loading on desktop

Performance

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

Passing (54)
Average (1)

Metrics

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

Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.

Time to Interactive — 0.6 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

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

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://facebook.co/	http/1.1	0	157.52100001555	400	0	302	text/html
https://www.facebook.com/	h2	158.08399999514	270.66299994476	36732	208845	200	text/html	Document
https://www.facebook.com/rsrc.php/v3/ya/l/0,cross/ZKjjBRnUnqR.css?_nc_x=Ij3Wp8lg5Kz	h2	403.48400000948	419.59599999245	2913	7962	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yK/l/0,cross/vtkeWlq4t3O.css?_nc_x=Ij3Wp8lg5Kz	h2	403.75499997754	419.27499999292	4271	16294	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yn/l/0,cross/7PuAvGOfOz2.css?_nc_x=Ij3Wp8lg5Kz	h2	404.05100001954	418.91200002283	1600	3387	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yt/l/0,cross/GwWIBreBItq.css?_nc_x=Ij3Wp8lg5Kz	h2	404.25999998115	419.88299996592	2741	8713	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yw/l/0,cross/7YxfI2GEzk2.css?_nc_x=Ij3Wp8lg5Kz	h2	404.53900001012	494.4550000364	6764	27775	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yu/l/0,cross/ca85PsWo5h9.css?_nc_x=Ij3Wp8lg5Kz	h2	404.85799999442	496.94700003602	1130	1469	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yn/l/0,cross/5VzR7szkoof.css?_nc_x=Ij3Wp8lg5Kz	h2	405.10400000494	423.6319999909	1092	2404	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yR/l/0,cross/CnzxB_yJWWz.css?_nc_x=Ij3Wp8lg5Kz	h2	405.34199995454	420.17800000031	800	515	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yt/l/0,cross/nsoyID9cjN4.css?_nc_x=Ij3Wp8lg5Kz	h2	405.66399996169	497.24599998444	2062	8100	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yu/l/0,cross/dNU0-BAD4y4.css?_nc_x=Ij3Wp8lg5Kz	h2	406.21799998917	420.73599994183	1483	2577	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3/yj/r/Le81M57FMbd.js?_nc_x=Ij3Wp8lg5Kz	h2	406.37300000526	496.24599993695	88859	326664	200	application/x-javascript	Script
https://facebook.com/security/hsts-pixel.gif	h2	712.74999994785	895.15999995638	1583	43	200	image/gif	Image
https://www.facebook.com/rsrc.php/v3i7M54/yA/l/en_US/6d1QoB2_uVs.js?_nc_x=Ij3Wp8lg5Kz	h2	501.04200001806	517.66200002749	31715	116595	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yd/r/Nk-rM4iWJZl.js?_nc_x=Ij3Wp8lg5Kz	h2	523.75499997288	594.25600001123	7551	22621	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yj/r/IUy0P1uEqH3.js?_nc_x=Ij3Wp8lg5Kz	h2	712.17499999329	795.13400001451	14103	43858	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yv/r/GG1Y0sYc7My.js?_nc_x=Ij3Wp8lg5Kz	h2	712.28800003882	794.4959999295	2255	5365	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/ys/r/wfEyQYgW470.png	h2	793.35099994205	809.30900003295	6513	5973	200	image/png	Image
https://www.facebook.com/rsrc.php/v3/ye/r/5zeYSLLaMs7.png	h2	798.65999997128	812.09799996577	1026	504	200	image/png	Image
	data	1011.9659999618	1012.0830000378	0	0	200	text/css	Stylesheet
	data	1012.3240000103	1012.3850000091	0	78	200	text/css	Stylesheet
https://www.facebook.com/rsrc.php/v3iYXl4/yc/l/en_US/63GuVXEYA0F.js?_nc_x=Ij3Wp8lg5Kz	h2	1214.0199999558	1302.5810000254	27182	95063	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3ipVm4/yy/l/en_US/a-2elIqyU3L.js?_nc_x=Ij3Wp8lg5Kz	h2	1214.4959999714	1305.992999929	35455	136936	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yt/r/7x71UTSzUeX.js?_nc_x=Ij3Wp8lg5Kz	h2	1215.0789999869	1294.1479999572	1893	3305	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yb/r/UHlXKQHdl3t.js?_nc_x=Ij3Wp8lg5Kz	h2	1215.7209999859	1296.7329999665	17114	52442	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yn/r/CbSc1syBEUz.js?_nc_x=Ij3Wp8lg5Kz	h2	1216.4590000175	1295.6390000181	784	317	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3iLl54/yj/l/en_US/1yn8K1CVZ6m.js?_nc_x=Ij3Wp8lg5Kz	h2	1217.1659999294	1300.1679999288	6091	16966	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yz/r/lYejkzyV906.js?_nc_x=Ij3Wp8lg5Kz	h2	1217.7290000254	1297.2079999745	1028	770	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yB/r/FYIV9LyqXbP.js?_nc_x=Ij3Wp8lg5Kz	h2	1218.3410000289	1302.0549999783	1150	1006	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yf/r/xn-3wPDECjN.js?_nc_x=Ij3Wp8lg5Kz	h2	1218.9960000105	1301.1460000416	4862	11740	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3iPwL4/yR/l/en_US/RTkqPFbXKo8.js?_nc_x=Ij3Wp8lg5Kz	h2	1219.5030000294	1301.6180000268	11251	33783	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/yT/r/CiZTi5pjDe1.js?_nc_x=Ij3Wp8lg5Kz	h2	1220.0279999524	1305.1640000194	45738	152705	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3iqES4/yK/l/en_US/tpIQPRjSdgv.js?_nc_x=Ij3Wp8lg5Kz	h2	1222.5460000336	1395.1169999782	15337	46461	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/y_/r/JopZtdti8dq.js?_nc_x=Ij3Wp8lg5Kz	h2	1222.9349999689	1394.3799999543	2868	7272	200	application/x-javascript	Script
https://www.facebook.com/rsrc.php/v3/y9/r/ugD21mPGNBo.js?_nc_x=Ij3Wp8lg5Kz	h2	1223.5769999679	1393.8959999941	1170	1437	200	application/x-javascript	Script
https://www.facebook.com/ajax/bz?__a=1&__ccg=EXCELLENT&__comet_req=0&__csr=&__dyn=7xe6Fo4OQ1PyUbFuC1swgE98nwgU6C7UW3q327E2vwXx60kO4o3Bw5VCwjE3awbG782Cw8G1Qw5MKdwl8G0me2218w5uwdK0D83mwaS0zE0I6aw&__hs=18823.PHASED%3ADEFAULT.2.0.0.0&__hsi=6984954913771957061-0&__req=1&__rev=1004113046&__s=aa4hvo%3Apib8u8%3Agb5a09&__spin_b=trunk&__spin_r=1004113046&__spin_t=1626311548&__user=0&dpr=1&jazoest=2839&lsd=AVo8Kd-Gz84	h2	2718.1430000346	2811.6349999327	1499	0	200	text/html	XHR

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources — Potential savings of 120 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Facebook.co should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
https://www.facebook.com/rsrc.php/v3/yj/r/Le81M57FMbd.js?_nc_x=Ij3Wp8lg5Kz	88859	80

Show Details

Properly size images
Images can slow down the page's load time. Facebook.co should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Facebook.co should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Facebook.co should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Facebook.co should consider minifying JS files.

Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Facebook.co should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 110 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
https://www.facebook.com/	113.576

Show Details

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Facebook.co should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://facebook.co/	190
https://www.facebook.com/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Facebook.co should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers — Potential savings of 15 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

URL	Potential Savings (Bytes)
https://www.facebook.com/rsrc.php/v3/yj/r/Le81M57FMbd.js?_nc_x=Ij3Wp8lg5Kz	15732

Show Details

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 380 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://www.facebook.com/rsrc.php/v3/yj/r/Le81M57FMbd.js?_nc_x=Ij3Wp8lg5Kz	88859
https://www.facebook.com/rsrc.php/v3/yT/r/CiZTi5pjDe1.js?_nc_x=Ij3Wp8lg5Kz	45738
https://www.facebook.com/	36732
https://www.facebook.com/rsrc.php/v3ipVm4/yy/l/en_US/a-2elIqyU3L.js?_nc_x=Ij3Wp8lg5Kz	35455
https://www.facebook.com/rsrc.php/v3i7M54/yA/l/en_US/6d1QoB2_uVs.js?_nc_x=Ij3Wp8lg5Kz	31715
https://www.facebook.com/rsrc.php/v3iYXl4/yc/l/en_US/63GuVXEYA0F.js?_nc_x=Ij3Wp8lg5Kz	27182
https://www.facebook.com/rsrc.php/v3/yb/r/UHlXKQHdl3t.js?_nc_x=Ij3Wp8lg5Kz	17114
https://www.facebook.com/rsrc.php/v3iqES4/yK/l/en_US/tpIQPRjSdgv.js?_nc_x=Ij3Wp8lg5Kz	15337
https://www.facebook.com/rsrc.php/v3/yj/r/IUy0P1uEqH3.js?_nc_x=Ij3Wp8lg5Kz	14103
https://www.facebook.com/rsrc.php/v3iPwL4/yR/l/en_US/RTkqPFbXKo8.js?_nc_x=Ij3Wp8lg5Kz	11251

Show Details

Uses efficient cache policy on static assets — 0 resources found
Facebook.co 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 — 223 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		223
Maximum DOM Depth	Log In	15
Maximum Child Elements	Sign UpLog InMessengerFacebook LiteWatchPeoplePagesPage CategoriesPlacesGamesLo…	34

Show Details

Avoid chaining critical requests — 12 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Facebook.co 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	5.461
Rendering	0.076
Script Evaluation	0.021

Show Details

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 — 35 requests • 380 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	35	389015
Script	19	316406
Document	1	36732
Stylesheet	10	24856
Image	3	9122
Other	2	1899
Media	0	0
Font	0	0
Third-party	1	400

Show Details

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
There was a problem with this request. We're working on getting it fixed as soo…

Show Details

Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Reduce unused JavaScript — Potential savings of 162 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.facebook.com/rsrc.php/v3/yj/r/Le81M57FMbd.js?_nc_x=Ij3Wp8lg5Kz	88859	45227
https://www.facebook.com/rsrc.php/v3/yT/r/CiZTi5pjDe1.js?_nc_x=Ij3Wp8lg5Kz	45738	44142
https://www.facebook.com/rsrc.php/v3ipVm4/yy/l/en_US/a-2elIqyU3L.js?_nc_x=Ij3Wp8lg5Kz	35455	28238
https://www.facebook.com/rsrc.php/v3i7M54/yA/l/en_US/6d1QoB2_uVs.js?_nc_x=Ij3Wp8lg5Kz	31715	26427
https://www.facebook.com/rsrc.php/v3iYXl4/yc/l/en_US/63GuVXEYA0F.js?_nc_x=Ij3Wp8lg5Kz	27182	21867

Show Details

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

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

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Contrast

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

Failing Elements
Sign Up

Show Details

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.

Best Practices

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

Passing (16)
Failing (3)

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).

Description	Directive	Severity
Elements controlled by object-src are considered legacy features. Consider setting object-src to 'none' to prevent the injection of plugins that execute unsafe scripts.	object-src	High
Host allowlists can frequently be bypassed. Consider using 'strict-dynamic' in combination with CSP nonces or hashes.	script-src	High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.	script-src	High
No CSP configures a reporting destination. This makes it difficult to maintain the CSP over time and monitor for any breakages.	report-uri	Medium

Show Details

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

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

Insecure URL	Request Resolution
http://facebook.co/	Allowed

Show Details

Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Failing Anchors
Facebook Pay
Oculus
Portal

Show Details

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Source
SHOW DETAILS

Show Details

SEO

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

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

Blocking Directive Source
SHOW DETAILS

Show Details

Progressive Web App

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

Installable

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of facebook.co 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)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://m.facebook.com/

Updated: 15th July, 2021

2.75 seconds

First Contentful Paint (FCP)

49%

31%

20%

0.05 seconds

First Input Delay (FID)

85%

12%

3%

Simulate loading on mobile

Performance

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

Metrics

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://facebook.co/	http/1.1	0	111.84199992567	414	0	302	text/html
https://www.facebook.com/	http/1.1	112.41400009021	149.74799985066	435	0	302	text/html
https://m.facebook.com/	h2	150.24300012738	300.97399977967	16862	39604	200	text/html	Document
https://static.xx.fbcdn.net/rsrc.php/v3/yl/l/0,cross/lCOwSF5VEHI.css?_nc_x=Ij3Wp8lg5Kz	h2	344.65199988335	359.77299977094	3585	13647	200	text/css	Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yj/l/0,cross/JX8prlxil8t.css?_nc_x=Ij3Wp8lg5Kz	h2	345.04800010473	367.6569997333	19333	83481	200	text/css	Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yq/l/0,cross/4J0KODZbQc4.css?_nc_x=Ij3Wp8lg5Kz	h2	345.36000015214	360.11300003156	798	253	200	text/css	Stylesheet
https://static.xx.fbcdn.net/rsrc.php/v3/yG/r/1nQwpQIHTr-.js?_nc_x=Ij3Wp8lg5Kz	h2	345.76399996877	361.35999998078	14131	43450	200	application/x-javascript	Script
https://static.xx.fbcdn.net/rsrc.php/v3iK-b4/yW/l/en_US/mSxJypZWKGs.js?_nc_x=Ij3Wp8lg5Kz	h2	346.01699979976	363.73399989679	53932	186517	200	application/x-javascript	Script
https://static.xx.fbcdn.net/rsrc.php/v3/yT/r/yqoOogE4Q9E.js?_nc_x=Ij3Wp8lg5Kz	h2	346.18899971247	365.85499998182	41609	142120	200	application/x-javascript	Script
https://static.xx.fbcdn.net/rsrc.php/v3/yW/r/ez-beZ7dNFv.js?_nc_x=Ij3Wp8lg5Kz	h2	346.70599969104	366.67100014165	12173	36998	200	application/x-javascript	Script
https://static.xx.fbcdn.net/rsrc.php/v3/y5/r/tPMwQh_6fE0.js?_nc_x=Ij3Wp8lg5Kz	h2	346.87400003895	364.5480000414	18120	58006	200	application/x-javascript	Script
https://static.xx.fbcdn.net/rsrc.php/v3/ys/r/XFDgmlkpDQR.js?_nc_x=Ij3Wp8lg5Kz	h2	347.04799996689	362.41000005975	916	379	200	application/x-javascript	Script
https://static.xx.fbcdn.net/rsrc.php/v3/yw/r/cT9y-LnPcuR.js?_nc_x=Ij3Wp8lg5Kz	h2	348.74599985778	368.96299989894	72924	267699	200	application/x-javascript	Script
https://facebook.com/security/hsts-pixel.gif	h2	380.83399971947	444.59699979052	1573	43	200	image/gif	Image
https://static.xx.fbcdn.net/rsrc.php/v3/yP/r/f11z-pF_pHe.png	h2	417.67399990931	431.31699971855	9164	8561	200	image/png	Image
https://static.xx.fbcdn.net/rsrc.php/v3/y_/r/JopZtdti8dq.js?_nc_x=Ij3Wp8lg5Kz	h2	546.9410000369	562.22900003195	2965	7272	200	application/x-javascript	Script
https://scontent.xx.fbcdn.net/hads-ak-prn2/1487645_6012475414660_1439393861_n.png	h2	548.48599992692	586.75500005484	417	79	200	image/png	Image
https://m.facebook.com/a/bz?fb_dtsg=AQHgskC_WHXgQvY%3A0%3A0&jazoest=21555&lsd=AVqHt5sF0p0&__dyn=0wzpaBwk8aU4ifDg9ppk2m3q12wAxu13w9y1DxW0Oohx60kO4o3Bw4Ewk9E4W0om0MU0D2US0se229w6twdK0D81x82ew5fw5NyE&__csr=&__req=1&__a=AYkvPnKD11IXd1K8BgjSYMs_tP5RvFr-4B6yk_bO8AlI43jxSTwXpRu7YUx4p2wCMHShPVEec6xYERPMgtwEOpVn5FVD_vhnIi-2q2AvwZ85LQ&__user=0	http/1.1	1549.009999726	1590.6130000949	1906	0	302	application/x-javascript
https://m.facebook.com/login.php?next=https%3A%2F%2Fm.facebook.com%2Fa%2Fbz%3Ffb_dtsg%3DAQHgskC_WHXgQvY%253A0%253A0%26jazoest%3D21555%26lsd%3DAVqHt5sF0p0&refsrc=deprecated&__req=1&__a=AYkvPnKD11IXd1K8BgjSYMs_tP5RvFr-4B6yk_bO8AlI43jxSTwXpRu7YUx4p2wCMHShPVEec6xYERPMgtwEOpVn5FVD_vhnIi-2q2AvwZ85LQ&__dyn=0wzpaBwk8aU4ifDg9ppk2m3q12wAxu13w9y1DxW0Oohx60kO4o3Bw4Ewk9E4W0om0MU0D2US0se229w6twdK0D81x82ew5fw5NyE&__m_async_page__=1&fb_dtsg_ag=AQziXVNPseFcq1SdvSeqG00OTwILDK75KjzwPm1mDnX-HxG6%3A0%3A0&jazoest=24308&_rdr	h2	1591.4849997498	1639.6030001342	5274	9567	200	application/x-javascript	XHR