C — https://www.threads.net | BeaverCheck Audit

Site Health

Score: 71 / 100

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)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 link(s) with no accessible text

Accessibility › Link & Button Quality

No <main> landmark found

Accessibility › Landmark Structure

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility › 404 Error Page

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.threads.net)](https://beavercheck.com/results/20fecd4d-e942-4e44-8a3c-0bfc5af9ac7f)

HTML

<a href="https://beavercheck.com/results/20fecd4d-e942-4e44-8a3c-0bfc5af9ac7f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.threads.net" alt="BeaverCheck Score"></a>

Image URL

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 ↓

TTFB degrading ↓

175ms

FCP stable →

3.7s

LCP degrading ↓

13.3s

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

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.44 s

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

4.28 s

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

964 ms

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

0.000

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

6.75 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.

14.33 s

Detailed Report

Audit breakdown by category with detailed findings.

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

	URL	Resource Size	Est Savings
Berdoulat’s Patrick Williams launches his interior design manifesto `div.x1e56ztr > a.x1i10hfl > div.x9f619 > img.xl1xv1r`	/emg1/v/t13/10096109727007863660?stp=dst-src&url=https%3A...	135.3 KiB	102.9 KiB
div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao `div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao`	/v/t51.71878-15/670600323_935206582616361_639464701228137...	33.3 KiB	18.7 KiB

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

lhId: page-1-IMG

nodeLabel: div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao

path: 1,HTML,1,BODY,55,DIV,2,DIV,1,DIV,4,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,1,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,0,DIV,0,DIV,0,IMG

selector: div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao

snippet: <img height="100%" width="100%" class="x15mokao x1ga7v0g x16uus16 xbiv7yw x1ey2m1c xtijo5x x1o0tod x10l6tqk x13vi…" alt="" referrerpolicy="origin-when-cross-origin" src="https://scontent.cdninstagram.com/v/t51.71878-15/670600323_935206582616361…">

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.

URL	Transfer Size	Duration
/rsrc.php/v5/ym/l/0,cross/KcC90Uq_Eah4zT1_TfPE9cfgQe914ii...	61.2 KiB	1.1 s

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

Request	Cache TTL	Transfer Size
/o1/v/t2/f2/m86/AQNz3FF6wryaX0yBKeFXxaDQTVQcHJfs8GFWAiBCl...	0.0 ms	768.6 KiB
/v/t51.82787-15/671152199_17954051034111412_3283432386403...	1209600.0 s	592.5 KiB
/emg1/v/t13/10096109727007863660?stp=dst-src&url=https%3A...	1209600.0 s	135.4 KiB
/v/t51.82787-15/671152199_17954051034111412_3283432386403...	1209600.0 s	70.8 KiB
/v/t51.71878-15/670600323_935206582616361_639464701228137...	1209600.0 s	33.3 KiB
/v/t51.2885-19/464753299_519189074353773_5030948084087127...	1209600.0 s	4.2 KiB
/v/t51.82787-19/650388398_17950386441108030_7040681005461...	1209600.0 s	3.4 KiB
/v/t51.82787-19/589083289_17933432457111412_7699004717793...	1209600.0 s	3.0 KiB
/v/t51.2885-19/361122376_1405628516836194_433038716766496...	1209600.0 s	2.6 KiB
/emg1/v/t13/9057498830920120198?url=https%3A%2F%2Fwww.wor...	1209600.0 s	746 B

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: 806 ms

URL	Time Spent
www.threads.net/	806 ms
www.threads.com/	0.0 ms

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.

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

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.

Estimated savings: 190 ms 67.0 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/ym/l/0,cross/KcC90Uq_Eah4zT1_TfPE9cfgQe914ii...	61.0 KiB	56.3 KiB
:root, .__fb-light-mode:root, .__fb-light-mode {--fds-black:#000000;--fds-black-alpha-05:rgba(0, 0,…	16.1 KiB	10.7 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
static.cdninstagram.com/rsrc.php/v4/yA/r/DW7-1bEC0OV.js	3.0 s	2.6 s	80 ms
www.threads.com/	639 ms	33 ms	0.6 ms
Unattributable	555 ms	31 ms	0.0 ms
static.cdninstagram.com/rsrc.php/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js	284 ms	123 ms	97 ms
static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js	219 ms	78 ms	119 ms
static.cdninstagram.com/rsrc.php/v4iYwz4/ya/l/en_US-j/WPt8LwgsxrM.js	122 ms	10 ms	111 ms
/rsrc.php/v4iDeJ4/yn/l/en_US-j/-FRlI3fWEL-H8LGx-iC5ORlBK6...	118 ms	12 ms	99 ms
static.cdninstagram.com/rsrc.php/v4i_Lc4/y7/l/en_US-j/fImsRrfQN-B.js	77 ms	8.3 ms	66 ms

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

Category	Time Spent
Script Evaluation	3.0 s
Other	811 ms
Script Parsing & Compilation	733 ms
Style & Layout	372 ms
Garbage Collection	172 ms
Parse HTML & CSS	126 ms
Rendering	68 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 reason	Failure type
The page has an unload handler in the main frame.	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

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 0.0 ms 652.1 KiB

URL	Transfer Size	Est Savings
static.cdninstagram.com/rsrc.php/v4i_Lc4/y7/l/en_US-j/fImsRrfQN-B.js	126.1 KiB	104.5 KiB
static.cdninstagram.com/rsrc.php/v4iYwz4/ya/l/en_US-j/WPt8LwgsxrM.js	183.6 KiB	104.1 KiB
static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js	234.2 KiB	99.5 KiB
/rsrc.php/v4iDeJ4/yn/l/en_US-j/-FRlI3fWEL-H8LGx-iC5ORlBK6...	186.8 KiB	96.3 KiB
static.cdninstagram.com/rsrc.php/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js	188.2 KiB	91.6 KiB
static.cdninstagram.com/rsrc.php/v4/yA/r/DW7-1bEC0OV.js	73.9 KiB	38.1 KiB
static.cdninstagram.com/rsrc.php/v4i6pM4/yn/l/en_US-j/Rwn7y3YOgnB.js	77.8 KiB	37.5 KiB
static.cdninstagram.com/rsrc.php/v4ib1W4/yf/l/en_US-j/mgQdedE4AZ_.js	39.0 KiB	33.9 KiB
static.cdninstagram.com/rsrc.php/v4iaMz4/ys/l/en_US-j/a1fYfLgOBoT.js	29.3 KiB	23.8 KiB
static.cdninstagram.com/rsrc.php/v4iEOb4/ys/l/en_US-j/6W0RX_TG6FA.js	38.5 KiB	22.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
/o1/v/t2/f2/m86/AQNz3FF6wryaX0yBKeFXxaDQTVQcHJfs8GFWAiBCl...	768.6 KiB
/v/t51.82787-15/671152199_17954051034111412_3283432386403...	592.5 KiB
static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js	234.4 KiB
static.cdninstagram.com/rsrc.php/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js	188.3 KiB
/rsrc.php/v4iDeJ4/yn/l/en_US-j/-FRlI3fWEL-H8LGx-iC5ORlBK6...	186.9 KiB
static.cdninstagram.com/rsrc.php/v4iYwz4/ya/l/en_US-j/WPt8LwgsxrM.js	183.8 KiB
/emg1/v/t13/10096109727007863660?stp=dst-src&url=https%3A...	135.4 KiB
static.cdninstagram.com/rsrc.php/v4i_Lc4/y7/l/en_US-j/fImsRrfQN-B.js	126.3 KiB
www.threads.com/	125.6 KiB
static.cdninstagram.com/rsrc.php/v4i6pM4/yn/l/en_US-j/Rwn7y3YOgnB.js	77.9 KiB

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

●User Timing marks and measures 84 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 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 100 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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
16h `time.x1rg5ohu > span.html-span > abbr > span`
worldofinteriors.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 have a discernible name

●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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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.

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	static.cdninstagram.com/rsrc.php/v4/yA/r/DW7-1bEC0OV.js line 251, col 362

●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 browser errors logged to the console

●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

Performance

Accessibility

Best Practices

100

SEO

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.

990 ms

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

2.82 s

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

31 ms

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

0.000

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

1.87 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.

2.82 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

	URL	Resource Size	Est Savings
Eagles player review: WR Dontayvion Wicks edition `div.x1e56ztr > a.x1i10hfl > div.x9f619 > img.xl1xv1r`	/emg1/v/t13/6774413379298184761?stp=dst-src&url=https%3A%...	147.7 KiB	134.1 KiB
div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao `div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao`	/v/t51.82787-15/670473506_17968219848022309_7761811395645...	102.8 KiB	91.2 KiB
covie_93's profile picture `div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r`	/v/t51.2885-19/358528981_1229914251044716_441780462984622...	5.1 KiB	4.9 KiB

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

lhId: page-1-IMG

nodeLabel: div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao

path: 1,HTML,1,BODY,40,DIV,2,DIV,1,DIV,3,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,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,0,DIV,0,DIV,0,IMG

selector: div.xrvj5dj > div.x5yr21d > div.x9f619 > img.x15mokao

snippet: <img height="100%" width="100%" class="x15mokao x1ga7v0g x16uus16 xbiv7yw x1ey2m1c xtijo5x x1o0tod x10l6tqk x13vi…" alt="" referrerpolicy="origin-when-cross-origin" src="https://scontent-lga3-2.cdninstagram.com/v/t51.82787-15/670473506_17968219…">

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.

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.

URL	Transfer Size	Duration
/rsrc.php/v5/ym/l/0,cross/KcC90Uq_Eah4zT1_TfPE9cfgQe914ii...	61.2 KiB	294 ms

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

Request	Cache TTL	Transfer Size
/emg1/v/t13/6774413379298184761?stp=dst-src&url=https%3A%...	1209600.0 s	147.8 KiB
/v/t51.82787-15/670473506_17968219848022309_7761811395645...	1209600.0 s	102.9 KiB
/v/t51.2885-19/358528981_1229914251044716_441780462984622...	1209600.0 s	5.1 KiB
/v/t51.82787-19/540408199_17924240748101567_5041515082578...	1209600.0 s	4.2 KiB
/v/t51.2885-19/358042709_3567052426909549_665180334393961...	1209600.0 s	2.9 KiB
/emg1/v/t13/741800767961104736?url=https%3A%2F%2Fmedia.ph...	1209600.0 s	1.7 KiB
/o1/v/t2/f2/m86/AQMoDTw2GgbEJL5M4Tif_mbY2N13Klpmv61IzW4Fz...	0.0 ms	0 B

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: 244 ms

URL	Time Spent
www.threads.net/	244 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

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.

Estimated savings: 10 ms 67.3 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/ym/l/0,cross/KcC90Uq_Eah4zT1_TfPE9cfgQe914ii...	61.0 KiB	56.0 KiB
:root, .__fb-light-mode:root, .__fb-light-mode {--fds-black:#000000;--fds-black-alpha-05:rgba(0, 0,…	17.1 KiB	11.4 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 620 ms 644.2 KiB

URL	Transfer Size	Est Savings
static.cdninstagram.com/rsrc.php/v4iYwz4/ya/l/en_US-j/WPt8LwgsxrM.js	183.6 KiB	107.9 KiB
static.cdninstagram.com/rsrc.php/v4i_Lc4/y7/l/en_US-j/fImsRrfQN-B.js	126.1 KiB	105.5 KiB
static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js	234.2 KiB	102.3 KiB
static.cdninstagram.com/rsrc.php/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js	188.2 KiB	87.4 KiB
/rsrc.php/v4i5wH4/y_/l/en_US-j/-FRlI3fWEL-H8LGx-iC5ORlBK6...	185.4 KiB	86.9 KiB
static.cdninstagram.com/rsrc.php/v4i6pM4/yn/l/en_US-j/Rwn7y3YOgnB.js	77.8 KiB	37.5 KiB
static.cdninstagram.com/rsrc.php/v4/yA/r/DW7-1bEC0OV.js	73.9 KiB	36.3 KiB
static.cdninstagram.com/rsrc.php/v4ib1W4/yf/l/en_US-j/mgQdedE4AZ_.js	39.0 KiB	32.9 KiB
static.cdninstagram.com/rsrc.php/v4iEOb4/ys/l/en_US-j/6W0RX_TG6FA.js	38.5 KiB	23.9 KiB
static.cdninstagram.com/rsrc.php/v4iaMz4/ys/l/en_US-j/a1fYfLgOBoT.js	29.3 KiB	23.4 KiB

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 reason	Failure 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

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
/o1/v/t2/f2/m86/AQMoDTw2GgbEJL5M4Tif_mbY2N13Klpmv61IzW4Fz...	3.1 MiB
static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js	234.4 KiB
static.cdninstagram.com/rsrc.php/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js	188.3 KiB
/rsrc.php/v4i5wH4/y_/l/en_US-j/-FRlI3fWEL-H8LGx-iC5ORlBK6...	185.5 KiB
static.cdninstagram.com/rsrc.php/v4iYwz4/ya/l/en_US-j/WPt8LwgsxrM.js	183.8 KiB
/emg1/v/t13/6774413379298184761?stp=dst-src&url=https%3A%...	147.8 KiB
static.cdninstagram.com/rsrc.php/v4i_Lc4/y7/l/en_US-j/fImsRrfQN-B.js	126.3 KiB
www.threads.com/	121.6 KiB
/v/t51.82787-15/670473506_17968219848022309_7761811395645...	102.9 KiB
static.cdninstagram.com/rsrc.php/v4i6pM4/yn/l/en_US-j/Rwn7y3YOgnB.js	77.9 KiB

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

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 84 user timings

●JavaScript execution time 0.8 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 3 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 80 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

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
21h `time.x1rg5ohu > span.html-span > abbr > span`
16h `time.x1rg5ohu > span.html-span > abbr > span`
phillyvoice.com `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 have a discernible name

●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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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.

Best Practices

Browser Compatibility

General

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

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.cdninstagram.com/rsrc.php/v4/yA/r/DW7-1bEC0OV.js line 251, col 362

●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 browser errors logged to the console

●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

○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

Browse & Analyze

Learn

Results for https://www.threads.net

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best practices

Best Practices

Browser Compatibility

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best Practices

Browser Compatibility

General

SEO

Keyboard Shortcuts