Skip to content
Audit Complete

Results for https://www.threads.net

Visit site
Spain Spain · Madrid Completed: Apr 12, 2026 14:05 UTC

No change since last audit

Compared to scan from 3 hours ago

View previous audit

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C71

Site Health

Score: 71 / 100 Same as last audit

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

No Content-Security-Policy header found

Security › Content Security Policy
3

1 link(s) with no accessible text

Accessibility › Link & Button Quality
4

No <main> landmark found

Accessibility › Landmark Structure
5

Certificate expires soon (7 days remaining)

Security › TLS & Certificates
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.threads.net)](https://beavercheck.com/results/ee718b11-8bc7-4baf-b688-eb1c29b3f403)
<a href="https://beavercheck.com/results/ee718b11-8bc7-4baf-b688-eb1c29b3f403"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.threads.net" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.threads.net

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations
UN New York
Full audit
84ms
DNS 3ms · TLS 10ms
ES Madrid
Full audit
216ms
DNS 132ms · TLS 19ms
US Santa Clara
Full audit
44ms
DNS 4ms · TLS 5ms
NL Amsterdam
Full audit
54ms
DNS 20ms · TLS 7ms
SG Singapore
Full audit
188ms
DNS 12ms · TLS 5ms
BR Sao Paulo
Full audit
175ms
DNS 4ms · TLS 5ms
CDN: No CDN · Avg TTFB: 127ms · Cache: No cache headers
Recent Trends
Performance degrading ↓
36
TTFB degrading ↓
175ms
FCP stable →
3.7s
LCP degrading ↓
13.3s

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

49 -2
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87 +2
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73 -4
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.41 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

13.01 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

582 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.032

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

5.57 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

13.67 s

Detailed Report

Audit breakdown by category with detailed findings.

49

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
China's eel farmers face plummeting prices after extensive 2025 catch div.x1e56ztr > a.x1i10hfl > div.x9f619 > img.xl1xv1r
/emg1/v/t13/5581030892672558312?stp=dst-src&url=https%3A%...214.6 KiB202.6 KiB
Photo by Shithousery HQ on April 11, 2026. May be an image of poster, bottle an… div.x6ikm8r > div.x5yr21d > picture.x87ps6o > img.xl1xv1r
/v/t51.82787-15/670989314_18109072259504030_4850332597794...51.8 KiB20.4 KiB
Photo by Shithousery HQ on April 11, 2026. May be an image of football, soccer,… div.x6ikm8r > div.x5yr21d > picture.x87ps6o > img.xl1xv1r
/v/t51.82787-15/669997995_18109072250504030_3024506598760...45.8 KiB15.2 KiB
A Threads user's profile picture div.x6s0dn4 > div.x1rg5ohu > div.html-div > img.xl1xv1r
/v/t51.2885-19/461390512_3856137064629654_891041708407959...6.0 KiB5.9 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-2-IMG
nodeLabel: Photo by Shithousery HQ on April 11, 2026. May be an image of football, soccer,…
path: 1,HTML,1,BODY,40,DIV,2,DIV,1,DIV,3,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,0,IMG
selector: div.x6ikm8r > div.x5yr21d > picture.x87ps6o > img.xl1xv1r
snippet: <img draggable="false" height="1350" width="1080" class="xl1xv1r x9f619 x1lliihq xmz0i5r x193iq5w xp3xoqj x1g40iwv x47corl x87ps6o …" alt="Photo by Shithousery HQ on April 11, 2026. May be an image of football, so…" referrerpolicy="origin-when-cross-origin" sizes="224px" srcset="https://scontent-cdg4-2.cdninstagram.com/v/t51.82787-15/669997995_18109072…" src="https://scontent-cdg4-2.cdninstagram.com/v/t51.82787-15/669997995_18109072…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 789 ms
URLTime Spent
www.threads.net/789 ms
www.threads.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation2.3 s
Other895 ms
Script Parsing & Compilation470 ms
Style & Layout368 ms
Garbage Collection130 ms
Parse HTML & CSS85 ms
Rendering69 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,298 KiB
User Timing marks and measures 84 user timings
Avoid long main-thread tasks 18 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 70 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
87

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Failing Elements
Get the full app experience Unlock more features and see what people are talkin… div.x1uvtmcs > div.__fb-light-mode > div.x1cy8zhl > div.x1n2onr6

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
11h time.x1rg5ohu > span.html-span > abbr > span
16h time.x1rg5ohu > span.html-span > abbr > span
16h time.x1rg5ohu > span.html-span > abbr > span
Replying to @authorlmbennett div > div.x1gslohp > span.x1lliihq > span.x1lliihq
@authorlmbennett div.x1gslohp > span.x1lliihq > span.x1lliihq > span
asia.nikkei.com div.xcrlgei > div.x6s0dn4 > span.x1lliihq > span.x1lliihq
Unlock more features and see what people are talking about right now. div.x1qjc9v5 > div.x1fmog5m > div.x6s0dn4 > span.x1lliihq

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Failing Elements
head > meta#viewport head > meta#viewport

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

Browser Compatibility

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
ErrorUtils caught an error: Non-error thrown: [object Object], keys: ["componentStack"] Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. [object Object]
Object
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

91
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.10 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.15 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.052

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.22 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.95 s

Detailed Report

Audit breakdown by category with detailed findings.

91

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Spurs expected team vs Sunderland - De Zerbi names surprising first starting XI div.x1e56ztr > a.x1i10hfl > div.x9f619 > img.xl1xv1r
/emg1/v/t13/419216660759111508?stp=dst-src&url=https%3A%2...92.9 KiB81.3 KiB
div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao
/v/t51.71878-15/670478452_1719532942548951_67558293154551...55.5 KiB47.5 KiB
div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao
/v/t51.71878-15/669931931_1832805940735855_72832594345629...48.6 KiB41.6 KiB
lfctom85's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.2885-19/358971250_1633768693782279_370103761700880...7.3 KiB7.1 KiB
sierracascadia's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.82787-19/543838986_17921959785114712_4668842227456...7.0 KiB6.7 KiB
thetanyahayles's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.82787-19/657852817_17957027484099024_3168018321513...5.9 KiB5.7 KiB
timkellysports's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.2885-19/358176105_788420596149146_2435736786723767...5.8 KiB5.6 KiB
mediumboi's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.82787-19/583245539_18540205762054768_6110810315065...5.8 KiB5.6 KiB
alasdair_gold's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.2885-19/357843450_757778799379341_5880178114668195...5.2 KiB5.0 KiB
mattlombardonfl's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.82787-19/624540477_18346471657230128_8728454440543...4.8 KiB4.6 KiB
joepraino's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.82787-19/571484442_17926060806115423_8373266477100...4.6 KiB4.4 KiB
authorarianastclaire's profile picture div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r
/v/t51.82787-19/504562246_17916111966118032_7819049696996...4.4 KiB4.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 256 ms
URLTime Spent
www.threads.net/256 ms
www.threads.com/0.0 ms
Time to Interactive 2.0 s
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,775 KiB
User Timing marks and measures 84 user timings
JavaScript execution time 0.7 s
Minimizes main-thread work 1.2 s
Avoid long main-thread tasks 1 long task found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 90 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 110 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Failing Elements
Say more with Threads Join Threads to share thoughts, find out what's going on,… div.x1uvtmcs > div.__fb-light-mode > div.x1cy8zhl > div.x1n2onr6

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
16h time.x1rg5ohu > span.html-span > abbr > span
17h time.x1rg5ohu > span.html-span > abbr > span
@jirkaprochazka span.xjp7ctv > div > a.x1i10hfl > span
@dougdoesfights span.xjp7ctv > div > a.x1i10hfl > span
22h time.x1rg5ohu > span.html-span > abbr > span
15h time.x1rg5ohu > span.html-span > abbr > span
16h time.x1rg5ohu > span.html-span > abbr > span
football.london div.xcrlgei > div.x6s0dn4 > span.x1lliihq > span.x1lliihq
Join Threads to share thoughts, find out what's going on, follow your people an… div.xr1yuqi > div.x78zum5 > div.xr1yuqi > span.x1lliihq

These are opportunities to improve the legibility of your content.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

Browser Compatibility

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
ErrorUtils caught an error: Non-error thrown: [object Object], keys: ["componentStack"] Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. [object Object]
Object
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Send Feedback