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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms

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
Try This Iconic Steak Tips Recipe From the Upcoming ‘Eaterland’ Cookbook `div._1dm09eq1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/4/2026/04/EATER_USA_Chapter7_St...	88.9 KiB	52.1 KiB
The Weekly Fish and Chips Special That Focuses on Sustainability `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/03/EAT_FPS_088_THUMB_SYN...	55.2 KiB	51.0 KiB
Breakfast Burritos, Galbi Patty Melts, and More Dishes Chef Nyesha Arrington Tr… `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/04/EAT_PLW_025_THUMB_SYN...	53.9 KiB	49.7 KiB
A Local Pizzaiolo’s Tour of the Best Restaurants in NYC `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/04/EAT_CDO_003_THUMB_YT1...	47.5 KiB	43.3 KiB
Tapered Candles Are Bringing Serious Drip to Dining Rooms `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/01/Berenjak.UpperIndoor....	45.5 KiB	41.3 KiB
The Best Housewarming Gifts (That You’ll Want for Yourself) `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2025/07/The-Best-Housewarming...	40.7 KiB	36.9 KiB
How a Michelin-Green-Starred Restaurant Makes One of the Best Burgers in NYC `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/03/EAT_FPS_089_THUMB_SYN...	40.6 KiB	36.8 KiB
The Eater x Zwiesel Fortessa Collection Brings Restaurant-Worthy Dinnerware to … `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/02/Fortessa_Shot5_Dinner...	38.8 KiB	35.1 KiB
This New Chicago Restaurant Has Something for Every Type of Night Out `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2026/04/EAT_NOW_001_THUMB_SYN...	29.8 KiB	27.0 KiB
The Best Condiments for Giving as Delicious Gifts `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2025/12/condiments-as-gifts-c...	27.1 KiB	24.5 KiB
A Food Lover’s Guide to Building a Wedding Registry `div._1r4m1yk1 > div.duet--content-cards--content-card > div._33xzbx7 > img._1u5z0xk0`	/wp-content/uploads/sites/2/2023/05/Wedding-Registry-Gift...	21.7 KiB	19.7 KiB

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

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
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js	3600.0 s	104.3 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.9 KiB
cdn.cookielaw.org/scripttemplates/202602.1.0/otBannerSdk.js	86400.0 s	129.0 KiB
btloader.com/tag?o=6315858775244800&upapi=true	300.0 s	36.9 KiB
pub.doubleverify.com/dvtag/21236410/DV464041/pub.js	900.0 s	33.6 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js	900.0 s	21.7 KiB
cdn.cookielaw.org/scripttemplates/202602.1.0/otTCF.js	86400.0 s	17.7 KiB
cdn.concert.io/lib/concert-concierge.2.10.1.min.js	86400.0 s	16.6 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
config.aps.amazon-adsystem.com/configs/3176	3600.0 s	4.5 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js	86400.0 s	6.7 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.7 KiB
/logos/451d8686-ff0b-4065-9afa-6289c6cb87c3/8a5fede8-de4c...	86400.0 s	2.2 KiB
apps.voxmedia.com/ad-block-detect/test_ads_prebid_blocker.js	0.0 ms	378 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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.

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

URL	Time Spent
eater.com/	241 ms
www.eater.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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 761.9 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.0 KiB
www.eater.com/_next/static/chunks/pages/_app-00464cad4eea785f.js	448.0 KiB	176.8 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	128.8 KiB
www.googletagmanager.com/gtag/destination?id=AW-926030959&cx=c&gtm=4e64h1	137.6 KiB	67.1 KiB
www.googletagmanager.com/gtag/js?id=G-GMSWCRTSTY&cx=c&gtm=4e64h1	150.1 KiB	60.7 KiB
cdn.cookielaw.org/scripttemplates/202602.1.0/otBannerSdk.js	128.8 KiB	60.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WQ5FM5W	184.9 KiB	53.3 KiB
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js	72.0 KiB	37.6 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.eater.com/_next/static/chunks/pages/_app-00464cad4eea785f.js	389 ms	280 ms	79 ms
www.googletagmanager.com/gtm.js?id=GTM-WQ5FM5W	328 ms	292 ms	17 ms
Unattributable	282 ms	48 ms	0.0 ms
www.eater.com/	233 ms	6.0 ms	0.3 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	188 ms	146 ms	17 ms
www.eater.com/_next/static/chunks/framework-42f3b70da36e8d96.js	157 ms	150 ms	3.6 ms
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js	137 ms	114 ms	11 ms
cdn.cookielaw.org/scripttemplates/202602.1.0/otBannerSdk.js	88 ms	50 ms	14 ms
www.googletagmanager.com/gtag/js?id=G-GMSWCRTSTY&cx=c&gtm=4e64h1	56 ms	48 ms	8.2 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	53 ms	34 ms	17 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.4 s
Other	326 ms
Script Parsing & Compilation	207 ms
Style & Layout	113 ms
Rendering	75 ms
Garbage Collection	56 ms
Parse HTML & CSS	39 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

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 36.3 KiB

URL	Transfer Size	Est Savings
	23.5 KiB	20.0 KiB
www.eater.com/_next/static/css/9e8ea2150808f57b.css	19.1 KiB	16.3 KiB

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
www.eater.com/_next/static/chunks/pages/_app-00464cad4eea785f.js	448.5 KiB
/wp-content/uploads/sites/4/2026/04/EATER_USA_Chapter7_St...	392.9 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-WQ5FM5W	185.2 KiB
/wp-content/uploads/sites/2/2026/04/Animae-Spring-2023-05...	163.6 KiB
www.googletagmanager.com/gtag/js?id=G-GMSWCRTSTY&cx=c&gtm=4e64h1	150.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-926030959&cx=c&gtm=4e64h1	137.9 KiB
www.eater.com/_next/static/media/d898aba7fdeb12ea-s.p.woff2	129.3 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 18 user timings

●Avoid long main-thread tasks 6 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Network Requests

●Network Round Trip Times 60 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 0 ms

●Avoid large layout shifts 7 layout shifts found

○INP breakdown

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

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.tzi1w98 > ul.wovzix0 > li > a.wovzix1 `div.tzi1w98 > ul.wovzix0 > li > a.wovzix1`

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.

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
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●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

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

○Identical links have the same purpose.

○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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
www.eater.com/_next/static/chunks/pages/_app-00464cad4eea785f.js
cdnjs.cloudflare.com/ajax/libs/blueimp-md5/2.19.0/js/md5.min.js	cdnjs.cloudflare.com/ajax/libs/blueimp-md5/2.19.0/js/md5.min.js.map
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js	cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js.map

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.eater.com/video	More
www.eater.com/add-to-cart	More
www.eater.com/video	More
www.eater.com/add-to-cart	More

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`