Skip to content
Audit Complete

Results for https://gizmodo.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 15, 2026 23:23 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
B80

Site Health

Score: 80 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

WordPress sites average 75
At average
Better than 85% of WordPress sites See full WordPress benchmark →
Apple sites average 73
+7 above average
Better than 92% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
2

5 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
3

8 image-only link(s) without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
4

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
5

70 third-party resources (80% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fgizmodo.com)](https://beavercheck.com/results/d2c0071d-2fb8-4b0f-a1de-f5930c1693b6)
<a href="https://beavercheck.com/results/d2c0071d-2fb8-4b0f-a1de-f5930c1693b6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgizmodo.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fgizmodo.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.5s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your audience reach.

3 accessibility issues exclude users who rely on assistive technology.
Your LCP is 4.5s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Return on Investment

$850 investment → $3,206/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +4426%

Investment

$850

8h · 5 findings

Monthly returns

$3,206 /mo

~$38,471 / year

  • Conversions recovered $3,205
  • Bandwidth savings $0.83

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$850

8.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,510 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • 3 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 1 of 2 <nav> elements are unlabeled
    ADA Title III: USD 25,000 – USD 150,000
  • 1 control(s) without accessible label
    ADA Title III: USD 25,000 – USD 150,000

+1 more

Bandwidth Waste

$0.83 /mo

10332.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.0 MB per page load
    Saves $0.83/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

43
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
85
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.43 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.48 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.52 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.026

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.05 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

20.71 s

Detailed Report

Audit breakdown by category with detailed findings.

43

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:12.918 source:map[column:135495 line:3 type:source-location url:https://scripts.opti-digital.com/lib/?site=gizmodo&lib=launcher&v=5.2.89 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:31.055 source:map[type:text value:[unattributed]]] map[reflowTime:4.815 source:map[column:192324 line:2 type:source-location url:https://scripts.opti-digital.com/lib/?site=gizmodo&lib=launcher&v=5.2.89 urlProvider:network]] map[reflowTime:2.89 source:map[column:186496 line:1 type:source-location url:https://cache.consentframework.com/js/pa/41707/c/V2Sw7/cmp urlProvider:network]] map[reflowTime:44.521 source:map[column:174464 line:1 type:source-location url:https://cache.consentframework.com/js/pa/41707/c/V2Sw7/cmp urlProvider:network]] map[reflowTime:10.674 source:map[column:135588 line:2 type:source-location url:https://scripts.opti-digital.com/lib/?site=gizmodo&lib=launcher&v=5.2.89 urlProvider:network]] map[reflowTime:2.244 source:map[column:135634 line:2 type:source-location url:https://scripts.opti-digital.com/lib/?site=gizmodo&lib=launcher&v=5.2.89 urlProvider:network]] map[reflowTime:1.177 source:map[column:142813 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:0.445 source:map[column:141171 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:22.431 source:map[column:90935 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:3.052 source:map[column:152770 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:1.561 source:map[column:118143 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:0.312 source:map[column:115111 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:1.364 source:map[column:28004 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:4.13 source:map[column:196989 line:0 type:source-location url:https://cds.connatix.com/p/309170447/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=92b7b46b-43ed-4e0e-b21b-2c999302d9d7 urlProvider:network]] map[reflowTime:2.16 source:map[column:505011 line:0 type:source-location url:https://cds.connatix.com/p/309170447/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=92b7b46b-43ed-4e0e-b21b-2c999302d9d7 urlProvider:network]] map[reflowTime:3.66 source:map[column:341949 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.ads.js urlProvider:network]] map[reflowTime:4.445 source:map[column:84973 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:5.725 source:map[column:126704 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]]]

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

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.

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.

URLResource SizeEst Savings
Thenextinterface div.grid > a.block > figure > img.w-full
gizmodo.com/app/uploads/2026/04/TheNextInterface-672x448.jpg69.5 KiB20.5 KiB
Anime collage of key visuals from Violet Evergarden, 86 Eighty-Six, and Vivy- F… div.flex > a.flex > figure.flex-none > img.w-full
/app/uploads/2026/04/violet-evergarden-86-eighty-six-vivy...58.4 KiB9.4 KiB
div.flex > a.flex > figure.flex-none > img.w-full div.flex > a.flex > figure.flex-none > img.w-full
gizmodo.com/app/uploads/2023/08/464b7c51ee01aeed4d5bc151bae864da-680x383.jpg41.3 KiB5.4 KiB

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

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.

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: 0.0 ms 35.4 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

URLTotal CPU TimeScript EvaluationScript Parse
gizmodo.com/1.6 s84 ms25 ms
/p/309170447/connatix.player.js?cid=872d12ce-453b-4870-84...1.5 s1.1 s93 ms
Unattributable1.2 s289 ms0.0 ms
cache.consentframework.com/js/pa/41707/c/V2Sw7/cmp1.1 s649 ms216 ms
cds.connatix.com/p/309170447/player.lit.ui.js888 ms669 ms26 ms
imasdk.googleapis.com/js/sdkloader/ima3.js794 ms683 ms76 ms
cdn.confiant-integrations.net/video/202603241056/wrap.js726 ms599 ms51 ms
cds.connatix.com/p/309170447/player.user.manager.service.js704 ms612 ms11 ms
scripts.opti-digital.com/lib/?site=gizmodo&lib=launcher&v=5.2.89404 ms220 ms2.8 ms
www.googletagmanager.com/gtag/js?id=G-EYNXLD4983&cx=c&gtm=4e64e1394 ms320 ms70 ms
cds.connatix.com/p/309170447/player.hls.js371 ms292 ms42 ms
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js343 ms316 ms19 ms
cache.consentframework.com/js/pa/41707/c/V2Sw7/stub342 ms292 ms1.5 ms
/pagead/managed/js/gpt/m202604130101/pubads_impl.js?cb=31...295 ms199 ms89 ms
www.googletagmanager.com/gtm.js?id=GTM-W5PBFP3X267 ms213 ms51 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=6017237 ms193 ms2.0 ms
securepubads.g.doubleclick.net/tag/js/gpt.js168 ms141 ms24 ms
cds.connatix.com/p/309170447/player.renderer.js140 ms56 ms30 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...138 ms96 ms8.5 ms
cdn.sirdata.eu/youtube-iframe.js131 ms121 ms1.8 ms
gizmodo.com/app/themes/gizmodo/public/vendor/app.9e12ed.js120 ms83 ms2.5 ms
cds.connatix.com/p/plugins/connatix.omsdk.service-web-1.4.13-compressed.js119 ms94 ms7.0 ms
cds.connatix.com/p/309170447/player.ads.js110 ms42 ms52 ms
cdn.confiant-integrations.net/33CYnLkVKFSMCUwC1MMcR-L4HeU/video/config.js87 ms29 ms57 ms
gizmodo.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.179 ms62 ms14 ms
cds.connatix.com/p/309170447/player.floating.js58 ms51 ms2.2 ms
s0.2mdn.net/instream/video/client.js57 ms26 ms29 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.

CategoryTime Spent
Script Evaluation7.7 s
Other1.6 s
Style & Layout1.4 s
Script Parsing & Compilation1.0 s
Parse HTML & CSS371 ms
Rendering261 ms
Garbage Collection172 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 reasonFailure 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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.7 KiB
URLTransfer SizeEst Savings
scripts.opti-digital.com/modules/?site=gizmodo8.2 KiB3.7 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

AutoHotkey div.mt-12 > div.grid > a.flex > img.flex-none
Tayasui Sketches div.mt-12 > div.grid > a.flex > img.flex-none
Adobe Acrobat Online div.mt-12 > div.grid > a.flex > img.flex-none
AppControl div.mt-12 > div.grid > a.flex > img.flex-none
Dictionary - Merriam-Webster div.mt-12 > div.grid > a.flex > img.flex-none
XAPK Extractor & App Analyzer div.mt-12 > div.grid > a.flex > img.flex-none
Tapestry by Iconfactory div.mt-12 > div.grid > a.flex > img.flex-none
LM Studio div.mt-12 > div.grid > a.flex > img.flex-none
Winslopr (Windows Slop Remover) div.mt-12 > div.grid > a.flex > img.flex-none
Google Play Store div.mt-12 > div.grid > a.flex > img.flex-none
Minecraft - Pocket Edition div.mt-12 > div.grid > a.flex > img.flex-none
YouTube div.mt-12 > div.grid > a.flex > img.flex-none
JumpJumpVPN div.mt-12 > div.grid > a.flex > img.flex-none
EA Sports FC 26 div.mt-12 > div.grid > a.flex > img.flex-none
Proton VPN (ProtonVPN) div.mt-12 > div.grid > a.flex > img.flex-none
WhatsApp div.mt-12 > div.grid > a.flex > img.flex-none
Among Us div.mt-12 > div.grid > a.flex > img.flex-none
TikTok div.mt-12 > div.grid > a.flex > img.flex-none

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 140 ms
Server Backend Latencies 60 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 90 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
85

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.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none
div.grid > a.flex > div.flex-1 > button.flex-none div.grid > a.flex > div.flex-1 > button.flex-none

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.relative > div.mx-auto > div.relative > a.absolute div.relative > div.mx-auto > div.relative > a.absolute
div.flex > div.fly-overflow > div.flex > a.inline-block div.flex > div.fly-overflow > div.flex > a.inline-block

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
APR 15 a.block > div.relative > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
CORPORATE CULTURE div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 15 div.flex > a.block > p.flex-none > span.flex-none
APR 14 div.flex > a.block > p.flex-none > span.flex-none
APR 14 div.flex > a.block > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 8 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 7 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 7 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 7 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 13 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 13 div.flex > a.block > p.flex-none > span.flex-none
APR 12 div.flex > a.block > p.flex-none > span.flex-none
APR 11 div.flex > a.block > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 13 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 12 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 15 a.block > div.relative > p.flex > span.flex-none
MAR 31 a.flex > div > p.flex > span.flex-none
MAR 22 a.flex > div > p.flex > span.flex-none
MAR 10 a.flex > div > p.flex > span.flex-none
MAR 26 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
MOVIES div.relative > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.block > div.relative > p.flex > span.flex-none
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
CORPORATE CULTURE div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
THEME PARKS & DESTINATIONS div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
TELEVISION div.self-end > div.mb-5 > span.giz-tag-io9 > span.inline-flex
APR 15 a.block > div.relative > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 14 a.flex > div > p.flex > span.flex-none
APR 14 a.flex > div > p.flex > span.flex-none

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
div.nav-fly > ul.menu > li.menu-item > ul.sub-menu div.nav-fly > ul.menu > li.menu-item > ul.sub-menu

These are opportunities to improve the experience of reading tabular or list data using 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
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.
`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
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.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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.
96

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.

SourceDescription
Uncaught TypeError: Cannot read properties of null (reading 'match')
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Software div.nav-fly > ul#menu-fly-menu-rocket > li#menu-item-2000721573 > a

To appear in search results, crawlers need access to your app.

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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

78
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

952 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.23 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

320 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.008

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.15 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.11 s

Detailed Report

Audit breakdown by category with detailed findings.

78

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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:7.942 source:map[column:204 line:1 type:source-location url:https://gizmodo.com/app/themes/gizmodo/public/vendor/app.9e12ed.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:51.808 source:map[column:5459 line:2500 type:source-location url:https://scripts.opti-digital.com/modules/?site=gizmodo urlProvider:network]] map[reflowTime:22.417 source:map[type:text value:[unattributed]]] map[reflowTime:2.8 source:map[column:23662 line:0 type:source-location url:https://cds.connatix.com/p/309170447/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=92b7b46b-43ed-4e0e-b21b-2c999302d9d7 urlProvider:network]] map[reflowTime:7.942 source:map[column:21733 line:0 type:source-location url:https://gizmodo.com/app/themes/gizmodo/public/app.5ff665.js urlProvider:network]] map[reflowTime:4.717 source:map[column:217367 line:2 type:source-location url:https://scripts.opti-digital.com/lib/?site=gizmodo&lib=launcher&v=5.2.89 urlProvider:network]] map[reflowTime:50.824 source:map[column:174464 line:1 type:source-location url:https://cache.consentframework.com/js/pa/41707/c/V2Sw7/cmp urlProvider:network]] map[reflowTime:5.876 source:map[column:142813 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:0.343 source:map[column:141171 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:18.968 source:map[column:90935 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:3.003 source:map[column:152770 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:1.55 source:map[column:118143 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:0.206 source:map[column:115111 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]] map[reflowTime:1.078 source:map[column:28004 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:4.617 source:map[column:196989 line:0 type:source-location url:https://cds.connatix.com/p/309170447/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=92b7b46b-43ed-4e0e-b21b-2c999302d9d7 urlProvider:network]] map[reflowTime:3.056 source:map[column:505011 line:0 type:source-location url:https://cds.connatix.com/p/309170447/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=92b7b46b-43ed-4e0e-b21b-2c999302d9d7 urlProvider:network]] map[reflowTime:0.158 source:map[column:98387 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:1.068 source:map[column:100240 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:2.629 source:map[column:341949 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.ads.js urlProvider:network]] map[reflowTime:4.809 source:map[column:84973 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:6.955 source:map[column:126704 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.renderer.js urlProvider:network]] map[reflowTime:4.915 source:map[column:87921 line:0 type:source-location url:https://cds.connatix.com/p/309170447/player.lit.ui.js urlProvider:network]]]

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

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.

URLResource SizeEst Savings
Thenextinterface div.grid > a.block > figure > img.w-full
gizmodo.com/app/uploads/2026/04/TheNextInterface-672x448.jpg69.5 KiB31.6 KiB
Anime collage of key visuals from Violet Evergarden, 86 Eighty-Six, and Vivy- F… div.flex > a.flex > figure.flex-none > img.w-full
/app/uploads/2026/04/violet-evergarden-86-eighty-six-vivy...20.0 KiB7.7 KiB
Uber Lucid Nuro Robotaxi div.mt-8 > a.flex > figure.flex-none > img.w-28
gizmodo.com/app/uploads/2026/01/Uber-Lucid-Nuro-Robotaxi-336x224.jpg15.7 KiB7.5 KiB
A man carries belongings in the aftermath of a US-Israeli strike on a residenti… div.mt-8 > a.flex > figure.flex-none > img.w-28
gizmodo.com/app/uploads/2026/04/iran-attack-336x224.jpg15.3 KiB7.1 KiB
div.flex > a.flex > figure.flex-none > img.w-full div.flex > a.flex > figure.flex-none > img.w-full
gizmodo.com/app/uploads/2023/08/464b7c51ee01aeed4d5bc151bae864da-300x169.jpg13.3 KiB6.4 KiB
The Mercedes-Benz EQS is seen on the street from the side. div.mt-8 > a.flex > figure.flex-none > img.w-28
gizmodo.com/app/uploads/2026/04/mercedes_EQS_lede-336x224.jpg12.5 KiB4.3 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

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.7 KiB
URLTransfer SizeEst Savings
scripts.opti-digital.com/modules/?site=gizmodo8.2 KiB3.7 KiB

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: 50 ms 33.8 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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.

CategoryTime Spent
Script Evaluation1.9 s
Other498 ms
Style & Layout424 ms
Script Parsing & Compilation255 ms
Parse HTML & CSS111 ms
Rendering91 ms
Garbage Collection52 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 reasonFailure 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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

AutoHotkey div.mt-12 > div.grid > a.flex > img.flex-none
Tayasui Sketches div.mt-12 > div.grid > a.flex > img.flex-none
Adobe Acrobat Online div.mt-12 > div.grid > a.flex > img.flex-none
AppControl div.mt-12 > div.grid > a.flex > img.flex-none
Dictionary - Merriam-Webster div.mt-12 > div.grid > a.flex > img.flex-none
XAPK Extractor & App Analyzer div.mt-12 > div.grid > a.flex > img.flex-none
Tapestry by Iconfactory div.mt-12 > div.grid > a.flex > img.flex-none
LM Studio div.mt-12 > div.grid > a.flex > img.flex-none
Winslopr (Windows Slop Remover) div.mt-12 > div.grid > a.flex > img.flex-none
Google Play Store div.mt-12 > div.grid > a.flex > img.flex-none
Minecraft - Pocket Edition div.mt-12 > div.grid > a.flex > img.flex-none
YouTube div.mt-12 > div.grid > a.flex > img.flex-none

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 7 long tasks found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 110 ms
Server Backend Latencies 50 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 170 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
90

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.

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
APR 15 a.block > div.relative > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
CORPORATE CULTURE div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 15 div.flex > a.block > p.flex-none > span.flex-none
APR 14 div.flex > a.block > p.flex-none > span.flex-none
APR 14 div.flex > a.block > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 8 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 7 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 13 a.flex > div.xl:flex-1 > p.flex > span.flex-none
APR 13 div.flex > a.block > p.flex-none > span.flex-none
APR 12 div.flex > a.block > p.flex-none > span.flex-none
APR 11 div.flex > a.block > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 14 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 15 a.block > div.relative > p.flex > span.flex-none
MAR 31 a.flex > div > p.flex > span.flex-none
MAR 10 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
APR 15 a.flex > div.flex-1 > p.flex-none > span.flex-none
MOVIES div.relative > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.block > div.relative > p.flex > span.flex-none
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
CORPORATE CULTURE div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
THEME PARKS & DESTINATIONS div > p.flex > span.giz-tag-io9 > span.inline-flex
TELEVISION div > p.flex > span.giz-tag-io9 > span.inline-flex
APR 15 a.flex > div > p.flex > span.flex-none
TELEVISION div.self-end > div.mb-5 > span.giz-tag-io9 > span.inline-flex
APR 15 a.block > div.relative > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 15 a.flex > div > p.flex > span.flex-none
APR 14 a.flex > div > p.flex > span.flex-none
𝕏 div.hidden > ul#menu-social-2 > li.menu-item > a

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.relative > div.mx-auto > div.relative > a.absolute div.relative > div.mx-auto > div.relative > a.absolute

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.

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
div.nav-fly > ul.menu > li.menu-item > ul.sub-menu div.nav-fly > ul.menu > li.menu-item > ul.sub-menu

These are opportunities to improve the experience of reading tabular or list data using 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
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.
`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
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.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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.
96

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.

SourceDescription
Uncaught TypeError: Cannot read properties of null (reading 'match')
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
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Software div.nav-fly > ul#menu-fly-menu-rocket > li#menu-item-2000721573 > a

To appear in search results, crawlers need access to your app.

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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback