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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:103.868 source:map[type:text value:[unattributed]]]]

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
Sample skin photo `div.hidden > div.relative > div.relative > img.pointer-events-none`	trystencil.org/examples/skin-forearm.jpg	196.5 KiB	196.1 KiB
Geometric rose mandala previewed on a upper arm (AI-generated preview) `div.relative > div.relative > div.relative > img.absolute`	trystencil.org/examples/mandala-rose-skin.jpg	137.8 KiB	105.0 KiB
Fine line butterfly transfer stencil at 6 cm wide `div.relative > div.absolute > div.relative > img.absolute`	trystencil.org/examples/butterfly-stencil.png	108.3 KiB	101.3 KiB
“amor fati” in script previewed on a collarbone (AI-generated preview) `div.relative > div.relative > div.relative > img.absolute`	trystencil.org/examples/amor-fati-script-skin.jpg	127.6 KiB	97.2 KiB
Geometric rose mandala transfer stencil at 9 cm wide `div.relative > div.absolute > div.relative > img.absolute`	trystencil.org/examples/mandala-rose-stencil.png	104.1 KiB	97.2 KiB
Fine line butterfly `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/butterfly-design.png	91.6 KiB	90.9 KiB
Minimal wave & sun previewed on a ankle (AI-generated preview) `div.relative > div.relative > div.relative > img.absolute`	trystencil.org/examples/wave-skin.jpg	116.2 KiB	88.5 KiB
Fine line swallow with lavender previewed on a wrist (AI-generated preview) `div.relative > div.relative > div.relative > img.absolute`	trystencil.org/examples/swallow-skin.jpg	115.1 KiB	87.7 KiB
Fine line butterfly previewed on a forearm (AI-generated preview) `div.relative > div.relative > div.relative > img.absolute`	trystencil.org/examples/butterfly-skin.jpg	110.8 KiB	84.4 KiB
Rose mandala `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/mandala-rose-design.png	77.9 KiB	77.3 KiB
Snake & peony `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/snake-peony-design.png	73.7 KiB	73.1 KiB
Japanese koi `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/koi-design.png	73.3 KiB	72.7 KiB
Crescent moon & stars previewed on a inner forearm (AI-generated preview) `div.relative > div.relative > div.relative > img.absolute`	trystencil.org/examples/moon-stars-skin.jpg	88.9 KiB	67.8 KiB
Fine line swallow with lavender transfer stencil at 7 cm wide `div.relative > div.absolute > div.relative > img.absolute`	trystencil.org/examples/swallow-stencil.png	58.1 KiB	54.0 KiB
Rose & dagger `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/rose-dagger-design.png	50.8 KiB	50.4 KiB
Swallow & lavender `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/swallow-design.png	46.0 KiB	45.6 KiB
“amor fati” in script transfer stencil at 10 cm wide `div.relative > div.absolute > div.relative > img.absolute`	trystencil.org/examples/amor-fati-script-stencil.png	37.1 KiB	34.5 KiB
“amor fati” script `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/amor-fati-script-design.png	32.2 KiB	32.0 KiB
Crescent moon design `div.grid > div.col-span-2 > div.flex-1 > img.h-full`	trystencil.org/examples/moon-stars-design.png	29.8 KiB	28.6 KiB
Minimal wave & sun transfer stencil at 8 cm wide `div.relative > div.absolute > div.relative > img.absolute`	trystencil.org/examples/wave-stencil.png	26.3 KiB	24.4 KiB
Wave & sun `div.mt-4 > div.-mx-1 > button.relative > img.h-full`	trystencil.org/examples/wave-design.png	22.6 KiB	22.4 KiB
Crescent moon & stars transfer stencil at 5 cm wide `div.relative > div.absolute > div.relative > img.absolute`	trystencil.org/examples/moon-stars-stencil.png	22.8 KiB	21.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-8-IMG

nodeLabel: Fine line butterfly previewed on a forearm (AI-generated preview)

path: 1,HTML,1,BODY,6,DIV,2,MAIN,0,DIV,1,SECTION,0,DIV,1,DIV,0,DIV,2,DIV,0,DIV,0,IMG

selector: div.relative > div.relative > div.relative > img.absolute

snippet: <img src="/examples/butterfly-skin.jpg" alt="Fine line butterfly previewed on a forearm (AI-generated preview)" loading="eager" class="absolute inset-0 size-full object-cover transition-opacity duration-700 op…">

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
trystencil.org/_next/static/chunks/5c7dacfa177ec8b6.css	2.5 KiB	82 ms
trystencil.org/_next/static/chunks/296a32e452801729.css	41.7 KiB	306 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
/beacon.min.js/v4bc70e2c01a94c73b74392e423484066179121581...	86400.0 s	10.2 KiB

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

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 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: 120 ms 182.5 KiB

URL	Transfer Size	Est Savings
trystencil.org/_next/static/chunks/e0c25548b612ef82.js	83.4 KiB	63.5 KiB
trystencil.org/_next/static/chunks/b9b9bb0b2d1bc7a4.js	54.8 KiB	49.5 KiB
trystencil.org/_next/static/chunks/47e74b3ca15ea91f.js	56.1 KiB	48.7 KiB
trystencil.org/_next/static/chunks/30c3f2be920d33a3.js	70.0 KiB	20.7 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
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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
trystencil.org/examples/skin-forearm.jpg	197.0 KiB
trystencil.org/examples/mandala-rose-skin.jpg	138.3 KiB
trystencil.org/examples/amor-fati-script-skin.jpg	128.1 KiB
trystencil.org/examples/wave-skin.jpg	116.7 KiB
trystencil.org/examples/swallow-skin.jpg	115.6 KiB
trystencil.org/examples/butterfly-skin.jpg	111.3 KiB
trystencil.org/examples/butterfly-stencil.png	108.8 KiB
trystencil.org/examples/mandala-rose-stencil.png	104.7 KiB
trystencil.org/_next/static/chunks/9a4e53e93baea317.js	94.2 KiB
trystencil.org/examples/butterfly-design.png	92.1 KiB

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.5 s

●Avoid long main-thread tasks 5 long tasks found

●Avoid non-composited animations 2 animated elements 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

●Avoid multiple page redirects

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

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○User Timing marks and measures

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Fine line butterfly `div.relative > div.absolute > div.flex > button.h-1.5`
Geometric rose mandala `div.relative > div.absolute > div.flex > button.h-1.5`
Crescent moon & stars `div.relative > div.absolute > div.flex > button.h-1.5`
Minimal wave & sun `div.relative > div.absolute > div.flex > button.h-1.5`
“amor fati” in script `div.relative > div.absolute > div.flex > button.h-1.5`
Fine line swallow with lavender `div.relative > div.absolute > div.flex > button.h-1.5`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TRYSTENCIL SCREENSHOTS + GUESSWORK Size on the body Calibrated in cm against … `div.mx-auto > div.overflow-hidden > div.overflow-x-auto > table.w-full`

○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

●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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●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

●Background and foreground colors have a sufficient contrast ratio

●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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○The page contains a heading, skip link, or landmark region

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`