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.

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

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/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader...	2875.0 s	4.4 KiB
www.etymonline.com/images/logo/legacy.svg?w=1920&q=75	259200.0 s	11.4 KiB
www.etymonline.com/images/logo/legacy-white.svg?w=1920&q=75	259200.0 s	11.4 KiB
www.etymonline.com/images/logo/horizontal-full.svg?w=256&q=75	259200.0 s	8.6 KiB
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....	2875.0 s	1.0 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
Kid Gloving `div.container > a.flex > div.flex > img.relative`	cdn.etymonline.com/pictures/f99daac125faa693dd6f8d94bdd99857.png	605.0 KiB	584.4 KiB
Book Nerd Rock and Roll `div.container > a.flex > div.flex > img.relative`	cdn.etymonline.com/pictures/f546a5ea44548769e4555bc41ab7d0a8.jpeg	295.0 KiB	282.9 KiB
Magic Words that Will Eat Your Soul `div.container > a.flex > div.flex > img.relative`	cdn.etymonline.com/pictures/af5a07c70ba4aa43f164fb487eff51d3.jpeg	56.0 KiB	40.5 KiB
talia `div.p-3 > div.flex > div.flex-shrink-0 > img.w-6`	cdn2.etymonline.com/user_avatar/forum.etymonline.com/talia/144/809_2.png	9.7 KiB	9.7 KiB
doug `div.p-3 > div.flex > div.flex-shrink-0 > img.w-6`	cdn2.etymonline.com/user_avatar/forum.etymonline.com/doug/144/505_2.png	4.7 KiB	4.6 KiB

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
www.etymonline.com/_next/static/css/08e96c478b1a5956.css	34.7 KiB	136 ms

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

URL	Time Spent
etymonline.com/	380 ms
www.etymonline.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 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: 60 ms 353.6 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	144.0 KiB
www.etymonline.com/_next/static/chunks/f39be7fe-d7468c1f4703ff48.js	97.9 KiB	69.3 KiB
www.googletagmanager.com/gtag/js?id=G-YGHSRMYRTV	165.9 KiB	66.1 KiB
www.google.com/adsense/search/ads.js	43.2 KiB	31.6 KiB
www.etymonline.com/_next/static/chunks/2165-37404638fe84be7b.js	31.8 KiB	21.5 KiB
www.etymonline.com/_next/static/chunks/6259-a8f47333dfff7756.js	48.3 KiB	21.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
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

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: 0.0 ms 31.4 KiB

URL	Transfer Size	Est Savings
www.etymonline.com/_next/static/css/08e96c478b1a5956.css	34.2 KiB	31.4 KiB

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,160 KiB

●User Timing marks and measures 10 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 1 long task found

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

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.h-full > div.relative > div.inline-flex > button.z-0 `div.h-full > div.relative > div.inline-flex > button.z-0`

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.

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
Get your speakers ready, because this will be much easier and more enjoyable if… `a.flex > div.relative > section.text-davis-gray/80 > span`
Mar 5 `a.flex > div.p-3 > div.flex > time.text-xs`
How to make anything sound scary for fun and profit `a.flex > div.relative > section.text-davis-gray/80 > span`
Feb 21 `a.flex > div.p-3 > div.flex > time.text-xs`
A few of the faces glimpsed from the time-travel train while researching "handl… `a.flex > div.relative > section.text-davis-gray/80 > span`
Feb 10 `a.flex > div.p-3 > div.flex > time.text-xs`
Quick and reliable accounts of the origin and history of English words. Scholar… `div.-mx-4 > div.w-full > div.mb-12 > p.mb-9`
Who Did This `div.mb-12 > ul > li > a.mb-4`
Sources `div.mb-12 > ul > li > a.mb-4`
Introduction `div.mb-12 > ul > li > a.mb-4`
Links `div.mb-12 > ul > li > a.mb-4`
Premium `div.mb-12 > ul > li > a.mb-4`
Patreon `div.mb-12 > ul > li > a.mb-4`
Donate with PayPal `div.mb-12 > ul > li > a.mb-4`
Merch `div.mb-12 > ul > li > a.mb-4`
Dark `div.inline-flex > div#react-aria-:RlnnrrimdfbH1: > button#react-aria-:RlnnrrimdfbH1:-tab-dark > div.relative`
Auto `div.inline-flex > div#react-aria-:RlnnrrimdfbH1: > button#react-aria-:RlnnrrimdfbH1:-tab-system > div.relative`
Terms of Services `div.flex > div.flex > div.flex > a.link-hover`
Privacy Policy `div.flex > div.flex > div.flex > a.link-hover`
English (English) `div.flex > div.flex > div > button#react-aria-:Rtnnrrimdfb:`
© 2001 - 2026 Douglas Harper `div.flex > div.flex > div.text-sm > a.text-battleship-gray`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get Chrome Extension Get iOS App Get Android App `div.-mx-4 > div.w-full > div.mb-12 > ul`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Auto `div.bg-battleship-gray > div.inline-flex > div#react-aria-:RlnnrrimdfbH1: > button#react-aria-:RlnnrrimdfbH1:-tab-system`

○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

●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

●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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

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

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

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

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.etymonline.com/columns/post/sources	here
www.etymonline.com/columns/post/abbr	here

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`