Skip to content
Audit Complete

Results for https://theringer.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 23:11 UTC
Share card preview
Share on X Share on LinkedIn Share on Reddit Share on Hacker News Share via Email Download share image Embed Badge
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)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Room to improve — your 15.1s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Strong compliance posture across regulations.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

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

Apollo · 44 peers
You 69
·
Avg 72
At average
0 50 100
Better than 6% of Apollo sites See full Apollo benchmark →
Framer Motion · 87 peers
You 69
·
Avg 73
At average
0 50 100
Better than 1% of Framer Motion sites See full Framer Motion benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 14.6 MB (4.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

236 link(s) with no accessible text

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

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Ftheringer.com)](https://beavercheck.com/results/603e83df-9877-4114-8f2d-de4246945555)
<a href="https://beavercheck.com/results/603e83df-9877-4114-8f2d-de4246945555"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftheringer.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ftheringer.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 15.1s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 15.1s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~27%.

Speed (2)

Page takes 15.1s to load

+12% bounce

Users abandon at ~3s — you're 12.6s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 3.6s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (2)

236 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€425 investment → €1.02/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

€425

5h · 5 findings

Monthly returns

€1.02 /mo

~€12 / year

  • Bandwidth savings €1.02

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€128 — in quick wins — start here for the fastest payback

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

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

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

€10,041,668 / month at risk

~€120,500,012 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+4 more

Bandwidth Waste

€1.02 /mo

13715.2 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.4 MB per page load
    Saves €1.02/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 5 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.

34
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.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

2.47 s

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

15.15 s

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

3.65 s

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

0.000

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

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

29.19 s

Detailed Report

Audit breakdown by category with detailed findings.

34

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

RequestCache TTLTransfer Size
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...3600.0 s888.5 KiB
www.theringer.com/_next/static/media/af780a379cdeea63-s.p.woff23600.0 s113.5 KiB
www.theringer.com/_next/static/media/77f9cf24d40ba9ac-s.p.woff23600.0 s106.5 KiB
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js3600.0 s104.0 KiB
www.theringer.com/_next/static/media/005497315cf9acf0-s.p.woff23600.0 s100.6 KiB
www.theringer.com/_next/static/media/35c02c0f3907609f-s.p.woff23600.0 s99.1 KiB
www.theringer.com/_next/static/media/175a77cc9db9a24c-s.p.woff23600.0 s96.7 KiB
www.theringer.com/_next/static/media/4e28d8537bc72037-s.p.woff23600.0 s91.8 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
www.theringer.com/_next/static/media/bda8101939848cfd-s.p.otf3600.0 s85.7 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
www.theringer.com/_next/static/media/f1c33117647e1241-s.p.woff23600.0 s56.2 KiB
www.theringer.com/_next/static/media/3582f3c0309ef02d-s.p.woff23600.0 s56.0 KiB
www.theringer.com/_next/static/media/d2f736b85ce1753d-s.p.woff23600.0 s54.4 KiB
www.theringer.com/_next/static/media/07ac3fb93eb1994c-s.p.woff23600.0 s48.4 KiB
www.theringer.com/_next/static/media/9c177ba8760f9e4d-s.p.woff23600.0 s45.4 KiB
/_next/static/chunks/framework-48bf801e6e8f0470.js?dpl=c8...3600.0 s42.7 KiB
/_next/static/css/2148c686b2e2b82e.css?dpl=c8a36f4e5aecd4...3600.0 s40.3 KiB
/_next/static/chunks/main-3f5a3e7ed442262d.js?dpl=c8a36f4...3600.0 s36.8 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
images.mediago.io/ML/d1011902867a98c1f96049dbd5f19771__scv1__622x368.webp3600.0 s16.8 KiB
static.chartbeat.com/js/chartbeat.js7200.0 s16.1 KiB
static.chartbeat.com/js/chartbeat_mab.js7200.0 s10.1 KiB
cdn.concert.io/lib/concert-concierge.2.10.1.min.js86400.0 s17.0 KiB
config.aps.amazon-adsystem.com/configs/31763600.0 s4.4 KiB
/_next/static/chunks/6323.6cfa8ea6e87ec2f4.js?dpl=c8a36f4...3600.0 s3.7 KiB
/_next/static/chunks/webpack-05a9c13c525df01f.js?dpl=c8a3...3600.0 s3.5 KiB
/_next/static/chunks/8366.d44cd9e274f096d6.js?dpl=c8a36f4...3600.0 s1.7 KiB
images.mediago.io/js/mediago/style/style_banner_a02e55.css3600.0 s1.7 KiB
open.spotify.com/embed/iframe-api/v10.0 ms1.3 KiB
/_next/static/chunks/8889.c764b191e90cc939.js?dpl=c8a36f4...3600.0 s1.2 KiB
/_next/static/chunks/5112.29b6cc2c6bed70ac.js?dpl=c8a36f4...3600.0 s1.2 KiB
/_next/static/chunks/8039.054821cf2c869355.js?dpl=c8a36f4...3600.0 s1.1 KiB
/_next/static/chunks/pages/index-9e0928ac59586ac9.js?dpl=...3600.0 s1.1 KiB
/_next/static/chunks/7736.19c9402df3e5b6d8.js?dpl=c8a36f4...3600.0 s1.1 KiB
/pagead/js/r20260421/r20110914/client/qs_click_protection...1209600.0 s8.5 KiB
/_next/static/c8a36f4e5aecd402ee36208bf365aa55021c19c7/_b...3600.0 s950 B
/_next/static/chunks/9068.b620888aa4fb3df5.js?dpl=c8a36f4...3600.0 s800 B
/_next/static/chunks/3796.599ba5fb4f8f954f.js?dpl=c8a36f4...3600.0 s745 B
/_next/static/chunks/8157.bf32a5a163733b3a.js?dpl=c8a36f4...3600.0 s592 B
apps.voxmedia.com/ad-block-detect/test_ads_prebid_blocker.js0.0 ms378 B
/_next/static/c8a36f4e5aecd402ee36208bf365aa55021c19c7/_s...3600.0 s365 B
/pagead/js/r20260421/r20110914/client/window_focus_fy2021.js1209600.0 s1.2 KiB
/_next/static/chunks/pages/search-140eedacdf5d6623.js?dpl...3600.0 s0 B
/_next/static/chunks/pages/[...wordpressNode]-8bd98f619fc...3600.0 s0 B

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.

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:90.028 source:map[column:138339 line:1 type:source-location url:https://www.theringer.com/_next/static/chunks/framework-48bf801e6e8f0470.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 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:59.912 source:map[type:text value:[unattributed]]] map[reflowTime:1.485 source:map[column:62205 line:464 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.208 source:map[column:216764 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:22.286 source:map[column:57614 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:4.359 source:map[column:36529 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:2.68 source:map[column:87785 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.586 source:map[column:59846 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.65 source:map[column:344544 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.454 source:map[column:65800 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:8.06 source:map[column:50732 line:28 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.312 source:map[column:111523 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.05 source:map[column:8921 line:464 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.61 source:map[column:206580 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.266 source:map[column:7625 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.748 source:map[column:77291 line:28 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.671 source:map[column:54350 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.918 source:map[column:286403 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:47.201 source:map[column:84572 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:8.775 source:map[column:84737 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.098 source:map[column:84685 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]]]

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
div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...74.6 KiB51.8 KiB
div.[@media(min-width:1920px)]:!ui-ml-0 > div.ui-relative > a.ui-absolute > img.ui-object-cover div.[@media(min-width:1920px)]:!ui-ml-0 > div.ui-relative > a.ui-absolute > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...78.7 KiB32.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover
path: 1,HTML,1,BODY,0,DIV,2,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,IMG
selector: div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover
snippet: <img alt="" data-sentry-element="Image" data-sentry-source-file="contained.tsx" loading="eager" decoding="async" data-nimg="fill" class="ui-object-cover ui-select-none" sizes="(max-width: 1024px) 100vw, (max-width: 1920px) 50vw, 960px" srcset="/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-content%2Fuploads%2F2…" src="https://www.theringer.com/_next/image?url=https%3A%2F%2Fwp.theringer.com%2…" style="position: absolute; height: 100%; width: 100%; inset: 0px;" pinger-seen="true">

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

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

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: 912 ms
URLTime Spent
theringer.com/912 ms
www.theringer.com/0.0 ms

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 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 34.4 KiB
URLTransfer SizeEst Savings
/_next/static/css/2148c686b2e2b82e.css?dpl=c8a36f4e5aecd4...39.9 KiB34.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

Estimated savings: 2.5 s 1.3 MiB
URLTransfer SizeEst Savings
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...885.5 KiB522.9 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB242.9 KiB
www.googletagmanager.com/gtag/js?id=G-BJM043QM72&cx=c&gtm=4e64k1156.9 KiB109.9 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB95.4 KiB
micro.rubiconproject.com/prebid/dynamic/7470.js156.8 KiB90.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J130.9 KiB67.2 KiB
www.googletagmanager.com/gtag/js?id=G-BJM043QM72156.9 KiB66.6 KiB
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js103.8 KiB52.5 KiB
c.amazon-adsystem.com/aax2/apstag.js90.5 KiB37.4 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.

URLTotal CPU TimeScript EvaluationScript Parse
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...3.5 s2.4 s296 ms
/_next/static/chunks/framework-48bf801e6e8f0470.js?dpl=c8...3.3 s2.7 s15 ms
Unattributable949 ms201 ms0.0 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js628 ms558 ms44 ms
www.theringer.com/609 ms27 ms0.6 ms
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js498 ms436 ms36 ms
micro.rubiconproject.com/prebid/dynamic/7470.js300 ms259 ms39 ms
www.googletagmanager.com/gtag/js?id=G-BJM043QM72255 ms219 ms35 ms
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J158 ms119 ms32 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js151 ms82 ms69 ms
config.aps.amazon-adsystem.com/configs/3176125 ms120 ms2.4 ms
static.chartbeat.com/js/chartbeat_mab.js112 ms39 ms2.1 ms
c.amazon-adsystem.com/aax2/apstag.js98 ms69 ms28 ms
static.chartbeat.com/js/chartbeat.js97 ms92 ms2.9 ms
www.googletagservices.com/tag/js/gpt.js71 ms60 ms10 ms
/_next/static/chunks/main-3f5a3e7ed442262d.js?dpl=c8a36f4...65 ms54 ms10.0 ms
embed-cdn.spotifycdn.com/_next/static/iframe_api.f8de525e2d635f3dc09d.js58 ms41 ms16 ms
www.googletagmanager.com/gtag/js?id=G-BJM043QM72&cx=c&gtm=4e64k156 ms22 ms34 ms
ep2.adtrafficquality.google/sodar/sodar2.js52 ms48 ms1.8 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.8 s
Other1.4 s
Style & Layout778 ms
Script Parsing & Compilation691 ms
Garbage Collection325 ms
Rendering223 ms
Parse HTML & CSS136 ms

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.

URLTransfer Size
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...888.5 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js362.4 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB
micro.rubiconproject.com/prebid/dynamic/7470.js157.0 KiB
www.googletagmanager.com/gtag/js?id=G-BJM043QM72&cx=c&gtm=4e64k1157.0 KiB
www.googletagmanager.com/gtag/js?id=G-BJM043QM72156.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J131.2 KiB
www.theringer.com/_next/static/media/af780a379cdeea63-s.p.woff2113.5 KiB
www.theringer.com/_next/static/media/77f9cf24d40ba9ac-s.p.woff2106.5 KiB
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js104.0 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 25 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
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.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8 div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8
div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8 div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8
div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8 div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8
article.ui-flex-col > a > div.ui-relative > button.ui-inline-flex article.ui-flex-col > a > div.ui-relative > button.ui-inline-flex
div.ui-flex > div.ui-relative > div.ui-absolute > button.ui-flex div.ui-flex > div.ui-relative > div.ui-absolute > button.ui-flex

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.ui-relative > div.ui-flex-col > div.ui-mb-4 > a.ui-inline-flex div.ui-relative > div.ui-flex-col > div.ui-mb-4 > a.ui-inline-flex
div#swiper-wrapper-776fb8a63d282e94 > div.swiper-slide > div.ui-bg-black > a.ui-absolute div#swiper-wrapper-776fb8a63d282e94 > div.swiper-slide > div.ui-bg-black > a.ui-absolute
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
main.main-grid > section.col-span-full > div.mb-4 > a.ui-inline-flex main.main-grid > section.col-span-full > div.mb-4 > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex

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
Who’s Going First? section.col-span-full > div.mb-4 > p.motion-safe:ui-transition-colors > span.motion-safe:ui-transition-colors
a True Crime Podcast div.w-full > div.flex > h2.text-heading-sm-medium > span.text-black/30

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NFL Draft article.ui-flex > div.ui-flex > div.ui-flex > a.ui-rounded-5xl

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
Discover div#__next > header#main-header > div.relative > button
○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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○`<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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Topics
micro.rubiconproject.com/prebid/dynamic/7470.js line 64, col 1164

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
/identity/?sv_domain=theringer.com&sv_pubid=7470&ssp_ids=...
Failed to load resource: the server responded with a status of 403 ()
/_next/data/c8a36f4e5aecd402ee36208bf365aa55021c19c7/todd...
Failed to load resource: the server responded with a status of 404 ()
api.rlcdn.com/api/identity/envelope?pid=13292
Failed to load resource: the server responded with a status of 451 ()
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J line 155, col 503
Uncaught [object Object]
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J line 155, col 503
Uncaught [object Object]

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.

URLMap URL
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.jscdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js.map
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

55
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.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
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.

799 ms

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

3.76 s

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

476 ms

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

0.023

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.

5.70 s

Detailed Report

Audit breakdown by category with detailed findings.

55

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

RequestCache TTLTransfer Size
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...3600.0 s888.5 KiB
www.theringer.com/_next/static/media/af780a379cdeea63-s.p.woff23600.0 s113.5 KiB
www.theringer.com/_next/static/media/77f9cf24d40ba9ac-s.p.woff23600.0 s106.5 KiB
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js3600.0 s104.0 KiB
www.theringer.com/_next/static/media/005497315cf9acf0-s.p.woff23600.0 s100.6 KiB
www.theringer.com/_next/static/media/35c02c0f3907609f-s.p.woff23600.0 s99.1 KiB
www.theringer.com/_next/static/media/175a77cc9db9a24c-s.p.woff23600.0 s96.7 KiB
www.theringer.com/_next/static/media/4e28d8537bc72037-s.p.woff23600.0 s91.8 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
www.theringer.com/_next/static/media/bda8101939848cfd-s.p.otf3600.0 s85.7 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js86400.0 s128.4 KiB
www.theringer.com/_next/static/media/3582f3c0309ef02d-s.p.woff23600.0 s56.2 KiB
www.theringer.com/_next/static/media/f1c33117647e1241-s.p.woff23600.0 s56.2 KiB
www.theringer.com/_next/static/media/d2f736b85ce1753d-s.p.woff23600.0 s54.4 KiB
www.theringer.com/_next/static/media/07ac3fb93eb1994c-s.p.woff23600.0 s48.4 KiB
www.theringer.com/_next/static/media/9c177ba8760f9e4d-s.p.woff23600.0 s45.4 KiB
/_next/static/chunks/framework-48bf801e6e8f0470.js?dpl=c8...3600.0 s42.7 KiB
/_next/static/css/2148c686b2e2b82e.css?dpl=c8a36f4e5aecd4...3600.0 s40.1 KiB
/_next/static/chunks/main-3f5a3e7ed442262d.js?dpl=c8a36f4...3600.0 s36.8 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
static.chartbeat.com/js/chartbeat.js7200.0 s15.9 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png86400.0 s19.2 KiB
static.chartbeat.com/js/chartbeat_mab.js7200.0 s10.1 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otTCF.js86400.0 s17.7 KiB
cdn.concert.io/lib/concert-concierge.2.10.1.min.js86400.0 s17.0 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
config.aps.amazon-adsystem.com/configs/31763600.0 s4.4 KiB
/_next/static/chunks/6323.6cfa8ea6e87ec2f4.js?dpl=c8a36f4...3600.0 s3.7 KiB
/_next/static/chunks/webpack-05a9c13c525df01f.js?dpl=c8a3...3600.0 s3.4 KiB
/_next/static/chunks/8366.d44cd9e274f096d6.js?dpl=c8a36f4...3600.0 s1.7 KiB
open.spotify.com/embed/iframe-api/v10.0 ms1.3 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.5 KiB
/_next/static/chunks/8889.c764b191e90cc939.js?dpl=c8a36f4...3600.0 s1.2 KiB
/_next/static/chunks/5112.29b6cc2c6bed70ac.js?dpl=c8a36f4...3600.0 s1.1 KiB
/_next/static/chunks/pages/index-9e0928ac59586ac9.js?dpl=...3600.0 s1.1 KiB
/_next/static/chunks/7736.19c9402df3e5b6d8.js?dpl=c8a36f4...3600.0 s1.1 KiB
/_next/static/chunks/8039.054821cf2c869355.js?dpl=c8a36f4...3600.0 s1.1 KiB
/_next/static/c8a36f4e5aecd402ee36208bf365aa55021c19c7/_b...3600.0 s966 B
/_next/static/chunks/9068.b620888aa4fb3df5.js?dpl=c8a36f4...3600.0 s823 B
/_next/static/chunks/3796.599ba5fb4f8f954f.js?dpl=c8a36f4...3600.0 s755 B
/_next/static/chunks/8157.bf32a5a163733b3a.js?dpl=c8a36f4...3600.0 s592 B
apps.voxmedia.com/ad-block-detect/test_ads_prebid_blocker.js0.0 ms378 B
/_next/static/c8a36f4e5aecd402ee36208bf365aa55021c19c7/_s...3600.0 s369 B
/_next/static/chunks/pages/search-140eedacdf5d6623.js?dpl...3600.0 s0 B
/_next/static/chunks/pages/[...wordpressNode]-8bd98f619fc...3600.0 s0 B

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.

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:112.702 source:map[column:138339 line:1 type:source-location url:https://www.theringer.com/_next/static/chunks/framework-48bf801e6e8f0470.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 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:40.497 source:map[type:text value:[unattributed]]] map[reflowTime:0.689 source:map[column:50619 line:28 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.283 source:map[column:49144 line:28 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:2.426 source:map[column:62205 line:464 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.255 source:map[column:216764 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:26.137 source:map[column:57614 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:4.002 source:map[column:36529 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:3.135 source:map[column:59846 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.092 source:map[column:65800 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:13.209 source:map[column:50732 line:28 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.194 source:map[column:80439 line:464 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.113 source:map[column:8921 line:464 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.595 source:map[column:206580 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:5.531 source:map[column:111523 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.233 source:map[column:54350 line:485 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:1.518 source:map[column:286403 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.979 source:map[column:273922 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:59.426 source:map[column:84572 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:12.381 source:map[column:84737 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:0.112 source:map[column:84685 line:265 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]] map[reflowTime:2.705 source:map[column:55025 line:456 type:source-location url:https://www.theringer.com/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c8a36f4e5aecd402ee36208bf365aa55021c19c7 urlProvider:network]]]

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
div.[@media(min-width:1920px)]:!ui-ml-0 > div.ui-relative > a.ui-absolute > img.ui-object-cover div.[@media(min-width:1920px)]:!ui-ml-0 > div.ui-relative > a.ui-absolute > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...736.5 KiB467.3 KiB
div.[@media(min-width:1920px)]:!ui-ml-0 > div.ui-relative > a.ui-absolute > img.ui-object-cover div.[@media(min-width:1920px)]:!ui-ml-0 > div.ui-relative > a.ui-absolute > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...633.9 KiB364.7 KiB
div.swiper-slide > div.ui-flex > a.ui-absolute > img.ui-object-cover div.swiper-slide > div.ui-flex > a.ui-absolute > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...487.0 KiB243.0 KiB
div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...74.6 KiB21.5 KiB
div.swiper-slide > div.ui-relative > a.ui-absolute > img.ui-object-cover div.swiper-slide > div.ui-relative > a.ui-absolute > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...36.4 KiB18.6 KiB
article.ui-flex-col > a > div.ui-relative > img.ui-object-cover article.ui-flex-col > a > div.ui-relative > img.ui-object-cover
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...42.4 KiB17.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-3-IMG
nodeLabel: div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover
path: 1,HTML,1,BODY,0,DIV,2,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,IMG
selector: div.swiper-slide > div.ui-bg-black > div.lg:ui-relative > img.ui-object-cover
snippet: <img alt="" data-sentry-element="Image" data-sentry-source-file="contained.tsx" loading="lazy" decoding="async" data-nimg="fill" class="ui-object-cover ui-select-none" sizes="(max-width: 1024px) 100vw, (max-width: 1920px) 50vw, 960px" srcset="/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-content%2Fuploads%2F2…" src="https://www.theringer.com/_next/image?url=https%3A%2F%2Fwp.theringer.com%2…" style="position: absolute; height: 100%; width: 100%; inset: 0px;" pinger-seen="true">

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

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: 356 ms
URLTime Spent
theringer.com/356 ms
www.theringer.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

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

Estimated savings: 400 ms 1.2 MiB
URLTransfer SizeEst Savings
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...885.5 KiB521.0 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB242.9 KiB
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...187.5 KiB104.7 KiB
micro.rubiconproject.com/prebid/dynamic/7470.js156.8 KiB90.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J130.9 KiB68.9 KiB
www.googletagmanager.com/gtag/js?id=G-BJM043QM72156.9 KiB65.5 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js128.2 KiB62.1 KiB
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js103.8 KiB53.0 KiB
c.amazon-adsystem.com/aax2/apstag.js90.5 KiB38.2 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.

URLTotal CPU TimeScript EvaluationScript Parse
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...1.8 s902 ms83 ms
/_next/static/chunks/framework-48bf801e6e8f0470.js?dpl=c8...899 ms737 ms7.5 ms
Unattributable407 ms104 ms0.0 ms
www.theringer.com/239 ms5.4 ms0.2 ms
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...142 ms116 ms10 ms
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J126 ms109 ms6.7 ms
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js98 ms86 ms7.9 ms
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js92 ms58 ms9.9 ms
micro.rubiconproject.com/prebid/dynamic/7470.js70 ms61 ms8.8 ms
www.googletagmanager.com/gtag/js?id=G-BJM043QM7255 ms46 ms8.8 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 Evaluation2.4 s
Other1.0 s
Style & Layout303 ms
Script Parsing & Compilation185 ms
Rendering158 ms
Garbage Collection98 ms
Parse HTML & CSS52 ms

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 52.4 KiB
URLTransfer SizeEst Savings
/_next/static/css/2148c686b2e2b82e.css?dpl=c8a36f4e5aecd4...39.9 KiB33.2 KiB
22.4 KiB19.2 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.

URLTransfer Size
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...888.5 KiB
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...736.6 KiB
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...634.0 KiB
/_next/image?url=https%3A%2F%2Fwp.theringer.com%2Fwp-cont...487.1 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js362.4 KiB
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...187.6 KiB
www.googletagmanager.com/gtag/js?id=G-BJM043QM72157.2 KiB
micro.rubiconproject.com/prebid/dynamic/7470.js157.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-5TPFJR6J131.0 KiB
cdn.cookielaw.org/scripttemplates/202601.2.0/otBannerSdk.js128.4 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 23 user timings
●Avoid long main-thread tasks 6 long tasks found
●Avoid non-composited animations 16 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 15 layout shifts found
○INP breakdown
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
article.ui-flex-col > a > div.ui-relative > button.ui-inline-flex article.ui-flex-col > a > div.ui-relative > button.ui-inline-flex

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#swiper-wrapper-fd558c107352d9831 > div.swiper-slide > div.ui-bg-black > a.ui-absolute div#swiper-wrapper-fd558c107352d9831 > div.swiper-slide > div.ui-bg-black > a.ui-absolute
div.ui-relative > div.ui-flex-col > div.ui-mb-4 > a.ui-inline-flex div.ui-relative > div.ui-flex-col > div.ui-mb-4 > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
main.main-grid > section.col-span-full > div.mb-4 > a.ui-inline-flex main.main-grid > section.col-span-full > div.mb-4 > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex

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
Discover div.relative > div.ui-pointer-events-none > div.ui-border > span.motion-safe:ui-transition-colors
Who’s Going First? section.col-span-full > div.mb-4 > p.motion-safe:ui-transition-colors > span.motion-safe:ui-transition-colors
a True Crime Podcast div.w-full > div.flex > h2.text-heading-sm-medium > span.text-black/30

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jump to slide 3 section.col-span-full > div.!-ui-ml-4 > div.ui-gap-1 > button.ui-rounded-full

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
NBA Panic Rankings and NFL Draft Guesses div.ui-relative > div.-ui-mx-6 > div.ui-px-4 > a.ui-block
The Latest Top-12 Intel vs. What We’d Do div.ui-relative > div.-ui-mx-6 > div.ui-px-4 > a.ui-block
○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
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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.
○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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Topics
micro.rubiconproject.com/prebid/dynamic/7470.js line 64, col 1164

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
/identity/?sv_domain=theringer.com&sv_pubid=7470&ssp_ids=...
Failed to load resource: the server responded with a status of 403 ()
/_next/data/c8a36f4e5aecd402ee36208bf365aa55021c19c7/todd...
Failed to load resource: the server responded with a status of 404 ()
/_next/data/c8a36f4e5aecd402ee36208bf365aa55021c19c7/nfl-...
Failed to load resource: the server responded with a status of 404 ()
api.rlcdn.com/api/identity/envelope?pid=13292
Failed to load resource: the server responded with a status of 451 ()

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.

URLMap URL
/_next/static/chunks/pages/_app-ee3d012350456bf5.js?dpl=c...
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.jscdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js.map
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback