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.

100

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.

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
Alden Unlined LHS in Shell: Simply the Best? `div.post-wrap > div.post-media > a.post-thumbnail > img.full-image`	100wears.com/wp-content/uploads/2020/10/Alden-Shell-Loafer-1.4-1536x1152.jpg	385.9 KiB	317.3 KiB
div.container > div.logo > a.custom-logo-link > img.custom-logo `div.container > div.logo > a.custom-logo-link > img.custom-logo`	100wears.com/wp-content/uploads/2020/10/cropped-White-Small-1536x580.jpg	43.8 KiB	41.3 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-2-IMG

nodeLabel: Adidas Flat Earther Review: A Flop That Actually Works

path: 1,HTML,1,BODY,34,DIV,1,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,MAIN,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,A,0,IMG

selector: div.post-wrap > div.post-media > a.post-thumbnail > img.full-image

snippet: <img width="850" height="640" src="https://100wears.com/wp-content/uploads/2026/05/PXL_20260427_183516995.avif" class="full-image not-transparent wp-post-image entered lazyloaded" alt="Adidas Flat Earther Review: A Flop That Actually Works" decoding="async" data-lazy-srcset="https://100wears.com/wp-content/uploads/2026/05/PXL_20260427_183516995.avi…" data-lazy-sizes="(max-width: 850px) 100vw, 850px" data-has-transparency="false" data-dominant-color="93938d" style="--dominant-color: #93938d;" data-lazy-src="https://100wears.com/wp-content/uploads/2026/05/PXL_20260427_183516995.avif" …>

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

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.5 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 630 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 10 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 110 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Adidas Flat Earther Review: A Flop That Actually Works `article#post-6804 > div.post-wrap > div.post-media > a.post-thumbnail`
Alden Unlined LHS in Shell: Simply the Best? `article#post-375 > div.post-wrap > div.post-media > a.post-thumbnail`
Jordan 1 Union x Fragment Review: Sizing, Comfort, and Value `article#post-6770 > div.post-wrap > div.post-media > a.post-thumbnail`
Amberjack The Original: Built for a Purpose `article#post-5031 > div.post-wrap > div.post-media > a.post-thumbnail`
Allen Edmonds Park Ave: 12 Years Later (2026) `article#post-81 > div.post-wrap > div.post-media > a.post-thumbnail`
Adidas UltraBoost 1 vs. UltraBoost 5x: Comparison and Review `article#post-6293 > div.post-wrap > div.post-media > a.post-thumbnail`
Grant Stone Tassel Loafer: Still in Love `article#post-3623 > div.post-wrap > div.post-media > a.post-thumbnail`
Amberjack The Atlas Review: A Comfort-First Take on GAT Sneakers `article#post-6749 > div.post-wrap > div.post-media > a.post-thumbnail`
What’s the Best Oxford for Your Budget? (2026) `article#post-1698 > div.post-wrap > div.post-media > a.post-thumbnail`
Amberjack The Low Top: Does it Deliver on Comfort? `article#post-6730 > div.post-wrap > div.post-media > a.post-thumbnail`

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
May 10, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
6 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
April 26, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
12 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
April 19, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
9 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
April 11, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
13 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
April 11, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
9 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
April 4, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
6 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
April 3, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
10 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
March 22, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
7 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
March 8, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
8 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
March 1, 2026 `div.entry-meta > span.posted-on > a > time.entry-date`
8 Min Reading `div.post-meta > div.post-date > div.entry-meta > span.min-read`
div.footer-top-box > section#search-5 > form.search-form > input.search-submit `div.footer-top-box > section#search-5 > form.search-form > input.search-submit`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.head_one > div.container > div.logo > a.custom-logo-link `div.head_one > div.container > div.logo > a.custom-logo-link`
div.container > div.logo > h1.site-title > a `div.container > div.logo > h1.site-title > a`
div#primary > main#main > div.pagination > a.next `div#primary > main#main > div.pagination > a.next`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

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

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

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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○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

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
100wears.com/favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`
100wears.com/ line 298, col 38	`SyntaxError: Identifier 'rocket_pairs' has already been declared`

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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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`