Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:36.53 source:map[column:1634 line:245 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4/yA/r/DW7-1bEC0OV.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:17.507 source:map[column:2539 line:361 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js urlProvider:network]] map[reflowTime:19.032 source:map[column:2955 line:465 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js urlProvider:network]] map[reflowTime:0.277 source:map[column:214 line:481 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js urlProvider:network]] map[reflowTime:3.169 source:map[column:117032 line:369 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js urlProvider:network]] map[reflowTime:0.303 source:map[column:4729 line:509 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js urlProvider:network]] map[reflowTime:0.139 source:map[column:5072 line:509 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:299.448 label:Time to first byte subpart:timeToFirstByte] map[duration:2309.444 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-SPAN

nodeLabel: When you finally get a book sale and they immediately return it for a refund 🙈

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,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,SPAN

selector: div > div.x1a6qonq > div.xat24cr > span.x1lliihq

snippet: <span class="x1lliihq x1plvlek xryxfnj x1n2onr6 xyejjpt x15dsfln xi7mnp6 x193iq5w xeuug…" dir="auto" style="--x---base-line-clamp-line-height: calc(1.4 * 1em); --x-lineHeight: calc(1…;">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/v/t51.2885-19/413250332_6816203275157481_755470974942973...	1209600.0 s	5.8 KiB
/v/t51.2885-19/460468178_8049864638444488_200450716409260...	1209600.0 s	4.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
indiebook_spotlight's profile picture `div.x1ywlc9c > a.x1i10hfl > div.html-div > img.xl1xv1r`	/v/t51.2885-19/413250332_6816203275157481_755470974942973...	5.7 KiB	5.5 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 301 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 67.6 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.9 KiB	11.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 560 ms 693.2 KiB

URL	Transfer Size	Est Savings
static.cdninstagram.com/rsrc.php/v4iYwz4/ya/l/en_US-j/WPt8LwgsxrM.js	183.6 KiB	115.2 KiB
static.cdninstagram.com/rsrc.php/v4iF2A4/y9/l/en_US-j/tGoAngMWAex.js	234.2 KiB	106.0 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/v4iMRr4/yk/l/en_US-j/BxWsmc26SVx.js	188.2 KiB	88.9 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	72.4 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	35.2 KiB
static.cdninstagram.com/rsrc.php/v4iaMz4/ys/l/en_US-j/a1fYfLgOBoT.js	29.3 KiB	23.4 KiB
static.cdninstagram.com/rsrc.php/v4iEOb4/ys/l/en_US-j/6W0RX_TG6FA.js	38.5 KiB	23.2 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,494 KiB

●User Timing marks and measures 84 user timings

●JavaScript execution time 1.1 s

●Minimizes main-thread work 1.8 s

●Avoid long main-thread tasks 4 long tasks found

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

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
20h `time.x1rg5ohu > span.html-span > abbr > span`
12h `time.x1rg5ohu > span.html-span > abbr > span`
15h `time.x1rg5ohu > span.html-span > abbr > span`

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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