B — https://kotaku.com | BeaverCheck Audit

Site Health

Score: 80 / 100

Based on 8 categories, 0 sections

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

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.

Mostly compliant — a few items need attention.

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 · 712 peers

You 80

Avg 74

+6 above average

0 50 100

Better than 91% of WordPress sites See full WordPress benchmark →

Font Awesome · 515 peers

You 80

Avg 73

+7 above average

0 50 100

Better than 95% of Font Awesome sites See full Font Awesome benchmark →

Top Priorities (5)

Page weighs 13.7 MB (6.1 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

13 image-only link(s) without alt text

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

Accessibility › Link & Button Quality

5 link(s) with no accessible text

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

Accessibility › Link & Button Quality

102 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

74 third-party resources (94% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fkotaku.com)](https://beavercheck.com/results/8a369ee0-48d7-4a13-9fcc-7c5ec2d97560)

HTML

<a href="https://beavercheck.com/results/8a369ee0-48d7-4a13-9fcc-7c5ec2d97560"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkotaku.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fkotaku.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 21.4s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your conversion rate.

Your LCP is 21.4s — fixing the 3 performance criticals could bring it under Google's 2.5s 'Good' threshold.

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 4 warning

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

Speed (2)

Page takes 21.4s to load

+12% bounce

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

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

Page feels frozen for 1.4s

+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)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

6 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

6 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

$900 investment → $1.53/month returns + USD 157,500 risk avoided

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

Investment

$900

9h · 5 findings

Monthly returns

$1.53 /mo

~$18 / year

Bandwidth savings $1.53

Regulatory risk avoided

USD 157,500

if kept compliant

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

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

$900

9.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,127 / month at risk

~$157,518 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
3 advertising/retargeting trackers detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+2 more

Bandwidth Waste

$1.53 /mo

19110.8 MB/mo × 0.080 USD/GB

Optimize transfer: save ~1.9 MB per page load
Saves $1.53/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.

10.93 s

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

21.38 s

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

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

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

21.42 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

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.

Request	Cache TTL	Transfer Size
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	3600.0 s	326.8 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=6017	1800.0 s	58.3 KiB
cdn.confiant-integrations.net/33CYnLkVKFSMCUwC1MMcR-L4HeU/video/config.js	1100.0 s	53.0 KiB
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	15.4 KiB
scripts.opti-digital.com/modules/?site=kotaku_com	7200.0 s	9.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.sirdata.eu/youtube-iframe.js	360.0 s	3.7 KiB
cache.consentframework.com/js/pa/41707/c/KGWlR/stub	3600.0 s	2.5 KiB
kotaku.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	2871.0 s	1.1 KiB
scripts.opti-digital.com/assets/712/logo.svg	691200.0 s	750 B
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	0 B
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	0 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/webfonts/fa-brands-400.woff2	75 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/webfonts/fa-solid-900.woff2	65 ms

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:91.054 source:map[type:text value:[unattributed]]] map[reflowTime:0.823 source:map[column:203896 line:2 type:source-location url:https://scripts.opti-digital.com/lib/?site=kotaku_com&lib=launcher&v=5.3.5 urlProvider:network]] map[reflowTime:0.671 source:map[column:142678 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.renderer.js urlProvider:network]] map[reflowTime:0.137 source:map[column:141036 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.renderer.js urlProvider:network]] map[reflowTime:13.668 source:map[column:90935 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:1.33 source:map[column:152770 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:0.669 source:map[column:118143 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:0.118 source:map[column:115111 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:0.595 source:map[column:27962 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.renderer.js urlProvider:network]] map[reflowTime:1.842 source:map[column:197320 line:0 type:source-location url:https://cds.connatix.com/p/320810193/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=995c4c7d-194f-4077-b0a0-7ad466eb737c urlProvider:network]] map[reflowTime:1.065 source:map[column:505329 line:0 type:source-location url:https://cds.connatix.com/p/320810193/connatix.player.js?cid=872d12ce-453b-4870-845f-955919887e1b&pid=995c4c7d-194f-4077-b0a0-7ad466eb737c urlProvider:network]] map[reflowTime:1.491 source:map[column:341954 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.ads.js urlProvider:network]] map[reflowTime:1.455 source:map[column:84838 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.renderer.js urlProvider:network]] map[reflowTime:2.482 source:map[column:126569 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.renderer.js urlProvider:network]] map[reflowTime:0.487 source:map[column:91428 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:0.644 source:map[column:47563 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:0.604 source:map[column:46787 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js urlProvider:network]] map[reflowTime:0.437 source:map[column:47184 line:0 type:source-location url:https://cds.connatix.com/p/320810193/player.lit.ui.js 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.

	URL	Resource Size	Est Savings
div.grid > a.block > figure.bg-black > img.w-full `div.grid > a.block > figure.bg-black > img.w-full`	kotaku.com/app/uploads/2026/04/IMG_3119-672x378.jpg	33.4 KiB	22.7 KiB
Magic Cards 1080 `div.grid > a.flex > figure.flex-none > img.w-full`	kotaku.com/app/uploads/2026/04/magic-cards-1080-336x189.jpg	21.9 KiB	20.1 KiB
div.grid > a.flex > figure.flex-none > img.w-full `div.grid > a.flex > figure.flex-none > img.w-full`	kotaku.com/app/uploads/2026/04/vcrawlers-336x189.jpg	13.9 KiB	8.1 KiB
A still from Guy Montgomery's Guy Mont-Spelling Bee showing Guy Montgomery smil… `div.grid > a.flex > figure.flex-none > img.w-full`	kotaku.com/app/uploads/2026/04/guy-montgomery-336x189.jpg	13.8 KiB	7.9 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
cache.consentframework.com/js/pa/41707/c/KGWlR/stub	2.5 KiB	915 ms
cdn.sirdata.eu/youtube-iframe.js	3.7 KiB	827 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css	10.9 KiB	1.2 s
kotaku.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	31.1 KiB	1.2 s
kotaku.com/app/themes/kotaku/public/app.5ff212.css	24.1 KiB	1.2 s
kotaku.com/wp/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.4 KiB	150 ms
kotaku.com/app/plugins/simple-tags/assets/frontend/js/frontend.js?ver=3.26.0	649 B
kotaku.com/app/plugins/simple-tags/assets/frontend/css/frontend.css?ver=3.26.0	861 B	150 ms
kotaku.com/app/plugins/keleops-toc/assets/css/screen.min.css?ver=2.0.23	1.3 KiB
kotaku.com/app/plugins/keleops-shopbot/css/all.min.css?ver=1.6.36	8.4 KiB
kotaku.com/app/plugins/pdfjs-viewer-shortcode/blocks/dist/style.css?ver=2.2.1	725 B

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: 140 ms 4.3 KiB

URL	Transfer Size	Est Savings
scripts.opti-digital.com/modules/?site=kotaku_com	8.6 KiB	4.3 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: 170 ms 31.5 KiB

URL	Transfer Size	Est Savings
kotaku.com/app/themes/kotaku/public/app.5ff212.css	23.7 KiB	21.4 KiB
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css	10.2 KiB	10.1 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: 4.0 s 749.0 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	142.6 KiB
imasdk.googleapis.com/js/sdkloader/ima3.js	145.7 KiB	79.6 KiB
scripts.opti-digital.com/lib/?site=kotaku_com&lib=launcher&v=5.3.5	98.9 KiB	74.0 KiB
cdn.confiant-integrations.net/video/202603241056/wrap.js	125.1 KiB	69.6 KiB
cds.connatix.com/p/320810193/player.ads.js	94.8 KiB	65.7 KiB
www.googletagmanager.com/gtag/js?id=G-XPGQQYNNL7&cx=c&gtm=4e64h1h1	157.0 KiB	65.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-W5PBFP3X	120.0 KiB	59.5 KiB
/p/320810193/connatix.player.js?cid=872d12ce-453b-4870-84...	138.5 KiB	48.2 KiB
cds.connatix.com/p/320810193/player.hls.js	74.9 KiB	39.4 KiB
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	304.3 KiB	32.5 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=6017	58.0 KiB	27.9 KiB
cds.connatix.com/p/320810193/player.renderer.js	44.1 KiB	23.1 KiB
kotaku.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	30.8 KiB	21.6 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	780 ms	89 ms	0.0 ms
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	662 ms	478 ms	100 ms
/p/320810193/connatix.player.js?cid=872d12ce-453b-4870-84...	629 ms	474 ms	43 ms
kotaku.com/	536 ms	38 ms	13 ms
cds.connatix.com/p/320810193/player.lit.ui.js	519 ms	394 ms	13 ms
cdn.confiant-integrations.net/video/202603241056/wrap.js	467 ms	432 ms	26 ms
imasdk.googleapis.com/js/sdkloader/ima3.js	428 ms	302 ms	40 ms
cds.connatix.com/p/320810193/player.user.manager.service.js	423 ms	376 ms	5.8 ms
cds.connatix.com/p/320810193/player.hls.js	285 ms	180 ms	20 ms
www.googletagmanager.com/gtag/js?id=G-XPGQQYNNL7&cx=c&gtm=4e64h1h1	256 ms	208 ms	39 ms
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	201 ms	186 ms	11 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	152 ms	105 ms	37 ms
cache.consentframework.com/js/pa/41707/c/KGWlR/stub	135 ms	121 ms	0.9 ms
scripts.opti-digital.com/lib/?site=kotaku_com&lib=launcher&v=5.3.5	127 ms	81 ms	1.2 ms
www.googletagmanager.com/gtm.js?id=GTM-W5PBFP3X	119 ms	91 ms	27 ms
cds.connatix.com/p/plugins/connatix.omsdk.service-web-1.4.13-compressed.js	79 ms	74 ms	4.0 ms
kotaku.com/app/themes/kotaku/public/vendor/app.9e12ed.js	76 ms	45 ms	1.8 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	75 ms	66 ms	7.8 ms
cds.connatix.com/p/320810193/player.renderer.js	67 ms	31 ms	13 ms
cds.connatix.com/p/320810193/player.ads.js	59 ms	25 ms	27 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	4.0 s
Other	961 ms
Style & Layout	636 ms
Script Parsing & Compilation	489 ms
Parse HTML & CSS	136 ms
Garbage Collection	136 ms
Rendering	30 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/cd4bb9bf-d232-43a7-bf12-67bdcd92b0a0/mmid-396dbbd9-4915-...	2.9 MiB
/cd4bb9bf-d232-43a7-bf12-67bdcd92b0a0/mmid-396dbbd9-4915-...	571.3 KiB
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	326.8 KiB
imasdk.googleapis.com/js/core/bridge3.758.1_en.html?gdpr=1	270.9 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB
www.googletagmanager.com/gtag/js?id=G-XPGQQYNNL7&cx=c&gtm=4e64h1h1	157.0 KiB
imasdk.googleapis.com/js/sdkloader/ima3.js	146.1 KiB
/p/320810193/connatix.player.js?cid=872d12ce-453b-4870-84...	139.1 KiB
cdn.confiant-integrations.net/video/202603241056/wrap.js	125.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W5PBFP3X	120.3 KiB

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

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

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 260 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 250 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
10:18 AM `div.relative > a.flex > div.flex-none > span.py-3`
9:38 AM `div.relative > a.flex > div.flex-none > span.py-3`
8:58 AM `div.relative > a.flex > div.flex-none > span.py-3`
8:18 AM `div.relative > a.flex > div.flex-none > span.py-3`
7:38 AM `div.relative > a.flex > div.flex-none > span.py-3`
6:58 AM `div.relative > a.flex > div.flex-none > span.py-3`
Apr 20 `div.relative > a.flex > div.flex-none > span.py-3`
Apr 20 `div.relative > a.flex > div.flex-none > span.py-3`
Apr 20 `div.relative > a.flex > div.flex-none > span.py-3`
Do not accept `div > div.sd-cmp-ke5c5 > button.sd-cmp-7Ga7b > span.sd-cmp-j-Z5-`
Kotaku `div.sd-cmp-gpI1s > div.sd-cmp-tZcty > div.sd-cmp-kT8Te > span`

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
ul.col-span-2 > li.py-8 > div.flex > a.flex-none `ul.col-span-2 > li.py-8 > div.flex > a.flex-none`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

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

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[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"]`

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
/pagead/managed/js/gpt/m202604160201/pubads_impl.js line 18, col 611901	`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

●Use a strong HSTS policy

●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

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●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

Performance

Accessibility

Best Practices

SEO

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.

898 ms

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

1.11 s

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

76 ms

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

0.004

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

2.26 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.03 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 ▾

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.

Request	Cache TTL	Transfer Size
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	3600.0 s	325.0 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	91.0 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=6017	1800.0 s	58.3 KiB
cdn.confiant-integrations.net/33CYnLkVKFSMCUwC1MMcR-L4HeU/video/config.js	1100.0 s	53.0 KiB
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	15.4 KiB
scripts.opti-digital.com/modules/?site=kotaku_com	7200.0 s	9.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.sirdata.eu/youtube-iframe.js	360.0 s	3.7 KiB
cache.consentframework.com/js/pa/41707/c/KGWlR/stub	3600.0 s	2.5 KiB
config.aps.amazon-adsystem.com/configs/ec4e8edf-c46b-44a1-bcab-17b3a4420b9a	3600.0 s	1.3 KiB
kotaku.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	2825.0 s	1.0 KiB
scripts.opti-digital.com/assets/712/logo.svg	691200.0 s	750 B
/hadron.js?url=https%3A%2F%2Fkotaku.com%2F&ref=&_it=amazo...	432000.0 s	186 B
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	0 B
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	0 B
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	3600.0 s	0 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/webfonts/fa-solid-900.woff2	75 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/webfonts/fa-brands-400.woff2	45 ms

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.801 source:map[column:5458 line:3378 type:source-location url:https://scripts.opti-digital.com/modules/?site=kotaku_com urlProvider:network]] map[reflowTime:42.393 source:map[type:text value:[unattributed]]]]

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.

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
kotaku.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	31.4 KiB	364 ms
cdn.sirdata.eu/youtube-iframe.js	3.7 KiB	277 ms
kotaku.com/app/themes/kotaku/public/app.5ff212.css	24.3 KiB	364 ms
cache.consentframework.com/js/pa/41707/c/KGWlR/stub	2.5 KiB	280 ms
kotaku.com/wp/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.5 KiB	189 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css	10.9 KiB	325 ms
kotaku.com/app/plugins/keleops-shopbot/css/all.min.css?ver=1.6.36	8.7 KiB	248 ms
kotaku.com/app/plugins/keleops-toc/assets/css/screen.min.css?ver=2.0.23	1.6 KiB	189 ms
kotaku.com/app/plugins/simple-tags/assets/frontend/js/frontend.js?ver=3.26.0	895 B	189 ms
kotaku.com/app/plugins/simple-tags/assets/frontend/css/frontend.css?ver=3.26.0	1.1 KiB	189 ms
kotaku.com/app/plugins/pdfjs-viewer-shortcode/blocks/dist/style.css?ver=2.2.1	926 B	73 ms

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

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: 30 ms 30.6 KiB

URL	Transfer Size	Est Savings
kotaku.com/app/themes/kotaku/public/app.5ff212.css	23.7 KiB	20.5 KiB
cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css	10.2 KiB	10.1 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/p/320936758/connatix.player.js?cid=872d12ce-453b-4870-84...	2.0 s	1.8 s	11 ms
Unattributable	402 ms	52 ms	0.0 ms
cdn.confiant-integrations.net/video/202603241056/wrap.js	280 ms	207 ms	6.7 ms
imasdk.googleapis.com/js/sdkloader/ima3.js	187 ms	174 ms	7.9 ms
kotaku.com/	187 ms	16 ms	3.3 ms
cds.connatix.com/p/320936758/player.lit.ui.js	154 ms	124 ms	2.7 ms
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	144 ms	103 ms	24 ms
cache.consentframework.com/js/pa/41707/c/KGWlR/stub	129 ms	109 ms	0.3 ms
cds.connatix.com/p/320936758/player.hls.js	127 ms	96 ms	4.7 ms
pagead2.googlesyndication.com/omsdk/releases/live/omweb-v1.js	57 ms	53 ms	2.9 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	53 ms	41 ms	11 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.1 s
Other	642 ms
Style & Layout	170 ms
Script Parsing & Compilation	145 ms
Garbage Collection	71 ms
Parse HTML & CSS	47 ms
Rendering	22 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size	Est Savings
scripts.opti-digital.com/modules/?site=kotaku_com	8.6 KiB	4.3 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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 893.4 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB	141.2 KiB
cds.connatix.com/p/plugins/prebid10.22-2.js	163.5 KiB	115.7 KiB
scripts.opti-digital.com/lib/?site=kotaku_com&lib=launcher&v=5.3.5	98.9 KiB	78.6 KiB
imasdk.googleapis.com/js/sdkloader/ima3.js	145.7 KiB	77.9 KiB
cdn.confiant-integrations.net/video/202603241056/wrap.js	125.1 KiB	69.6 KiB
www.googletagmanager.com/gtag/js?id=G-XPGQQYNNL7&cx=c&gtm=4e64k0h2	156.8 KiB	65.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-W5PBFP3X	119.8 KiB	59.7 KiB
cds.connatix.com/p/320936758/player.ads.js	95.2 KiB	57.4 KiB
/p/320936758/connatix.player.js?cid=872d12ce-453b-4870-84...	138.6 KiB	44.5 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.5 KiB	40.5 KiB
cds.connatix.com/p/320936758/player.hls.js	74.8 KiB	39.4 KiB
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	302.6 KiB	32.3 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=6017	58.0 KiB	26.6 KiB
cds.connatix.com/p/320936758/player.renderer.js	44.1 KiB	22.9 KiB
kotaku.com/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	30.8 KiB	21.7 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/cd4bb9bf-d232-43a7-bf12-67bdcd92b0a0/mmid-396dbbd9-4915-...	2.9 MiB
/cd4bb9bf-d232-43a7-bf12-67bdcd92b0a0/mmid-396dbbd9-4915-...	571.2 KiB
cache.consentframework.com/js/pa/41707/c/KGWlR/cmp	325.0 KiB
imasdk.googleapis.com/js/core/bridge3.758.1_en.html?gdpr=1	270.9 KiB
kotaku.com/app/uploads/2026/04/switch-2-games-1600x952.jpg	248.8 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB
kotaku.com/app/uploads/2026/04/ww22-1600x900.jpg	181.9 KiB
cds.connatix.com/p/plugins/prebid10.22-2.js	164.0 KiB
www.googletagmanager.com/gtag/js?id=G-XPGQQYNNL7&cx=c&gtm=4e64k0h2	156.9 KiB
imasdk.googleapis.com/js/sdkloader/ima3.js	146.1 KiB

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Improve image delivery

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 11 user timings

●Avoid long main-thread tasks 4 long tasks found

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

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 120 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 250 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

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
10:18 AM `div.relative > a.flex > div.flex-none > span.py-3`
9:38 AM `div.relative > a.flex > div.flex-none > span.py-3`
8:58 AM `div.relative > a.flex > div.flex-none > span.py-3`
8:18 AM `div.relative > a.flex > div.flex-none > span.py-3`
7:38 AM `div.relative > a.flex > div.flex-none > span.py-3`
6:58 AM `div.relative > a.flex > div.flex-none > span.py-3`
Apr 20 `div.relative > a.flex > div.flex-none > span.py-3`
Apr 20 `div.relative > a.flex > div.flex-none > span.py-3`
Apr 20 `div.relative > a.flex > div.flex-none > span.py-3`
Do not accept `div > div.sd-cmp-ke5c5 > button.sd-cmp-7Ga7b > span.sd-cmp-j-Z5-`
Kotaku `div.sd-cmp-gpI1s > div.sd-cmp-tZcty > div.sd-cmp-kT8Te > span`

These are opportunities to improve the legibility of your content.

Names and labels

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.col-span-2 > li.py-8 > div.flex > a.flex-none `ul.col-span-2 > li.py-8 > div.flex > a.flex-none`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

●Links are distinguishable without relying on color.

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

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[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"]`

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31... line 18, col 610999	`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

●Use a strong HSTS policy

●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

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

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

Results for https://kotaku.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Content (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts