Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
/Arturus/kaggle-web-traffic/refs/heads/master/images/trai...	300.0 s	203.7 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/auto...	300.0 s	153.0 KiB
storage.googleapis.com/kaggle-media/blog/research-grant.png	3600.0 s	135.8 KiB
/kaggle-organizations/5164/thumbnail.png?t=2026-01-30-17-...	3600.0 s	92.4 KiB
/kaggle-datasets-images/5857/8713/df2a86f4b6ecfff7996be17...	3600.0 s	77.5 KiB
/kaggle-competitions/kaggle/134561/logos/thumb76_76.png?G...	3600.0 s	57.0 KiB
storage.googleapis.com/kaggle-organizations/855/thumbnail.png	3600.0 s	51.6 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/spli...	300.0 s	41.3 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/enco...	300.0 s	41.1 KiB
storage.googleapis.com/kaggle-media/Images/Header_560x280_04-2.png	3600.0 s	46.6 KiB
storage.googleapis.com/kaggle-organizations/3837/thumbnail-2.png	3600.0 s	33.6 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/from...	300.0 s	27.3 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/lagg...	300.0 s	26.0 KiB
storage.googleapis.com/kaggle-avatars/thumbnails/3399668-kg.jpg	3600.0 s	30.6 KiB
storage.googleapis.com/kaggle-organizations/4582/thumbnail.png	3600.0 s	28.3 KiB
/kaggle-datasets-images/4305/6656/174b3eae6099dbc6ef1149c...	3600.0 s	20.5 KiB
storage.googleapis.com/kaggle-avatars/thumbnails/26782-kg.png	3600.0 s	17.9 KiB
/kaggle-datasets-images/612177/5023398/ed4470482e04000d11...	3600.0 s	14.6 KiB
/kaggle-avatars/thumbnails/15559822-kg.png?t=2025-07-02-2...	3600.0 s	14.5 KiB
/kaggle-media/Images/Screenshot 2026-03-17 10.04.44 AM.png	3600.0 s	11.7 KiB
storage.googleapis.com/kaggle-organizations/1202/thumbnail.png%3Fr=601	3600.0 s	11.3 KiB
/kaggle-datasets-images/1346/2425/573bbb9b260839fc8208792...	3600.0 s	9.0 KiB
/kaggle-avatars/thumbnails/13838978-kg.jpg?t=2024-10-04-0...	3600.0 s	6.6 KiB
storage.googleapis.com/kaggle-avatars/thumbnails/1034065-gr.jpg	3600.0 s	5.0 KiB
storage.googleapis.com/kaggle-organizations/4/thumbnail.png	3600.0 s	4.1 KiB
storage.googleapis.com/kaggle-avatars/thumbnails/1455-fb.jpg	3600.0 s	4.0 KiB
storage.googleapis.com/kaggle-avatars/thumbnails/59561-kg.jpg	3600.0 s	3.7 KiB
storage.googleapis.com/kaggle-avatars/thumbnails/263524-kg.jpg	3600.0 s	3.6 KiB
/kaggle-avatars/thumbnails/29956017-kg.png?t=2025-11-04-1...	3600.0 s	2.3 KiB
/kaggle-competitions/kaggle/133468/logos/thumb76_76.png?G...	3600.0 s	1.8 KiB
/kaggle-competitions/kaggle/133724/logos/thumb76_76.png?G...	3600.0 s	1.8 KiB
/p.css?s=1&k=tql2nih&ht=tk&f=40891.40892.40899.40904&a=20...	604800.0 s	172 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.146045] map[node:map[boundingRect:map[bottom:1887 height:952 left:16 right:388 top:935 width:372] lhId:page-24-DIV nodeLabel:Who's on Kaggle? AI Builders Test your AI skills against the world's best. Com… path:1,HTML,1,BODY,0,DIV,2,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,2,DIV selector:div.sc-fJxzGP > div.sc-cSiyUa > section.sc-cEpjUL > div.sc-cEzlxh snippet:<div class="sc-cEzlxh bqXCIk"> type:node] score:0.146045 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/googlesymbols/v419/HhyqU5Ak9u-oMExPeInvcuEmPosC9zS3FYkFU68cPrjdKM1XMoDZlWmzc3IiWvF1SbxVhQidBnv_C-yl9mm4Tw.woff2]]] type:subitems]]]

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.

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
/s/googlesymbols/v419/HhyqU5Ak9u-oMExPeInvcuEmPosC9zS3FYk...	200 ms
/af/37ff2c/00000000000000003b9b2a25/27/l?primer=7cdcb44be...	35 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:53.335 source:map[column:247682 line:1 type:source-location url:https://www.kaggle.com/static/assets/app.js?v=b2dca7301fc0aab7 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:53.335 source:map[column:966032 line:0 type:source-location url:https://www.kaggle.com/static/assets/app.js?v=b2dca7301fc0aab7 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.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	storage.googleapis.com/kaggle-media/blog/research-grant.png	135.4 KiB	134.3 KiB
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/benchmarks-landing@1.png	149.2 KiB	94.0 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-organizations/5164/thumbnail.png?t=2026-01-30-17-...	92.1 KiB	91.0 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-datasets-images/5857/8713/df2a86f4b6ecfff7996be17...	77.5 KiB	76.3 KiB
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/competitions-detail@1.png	90.6 KiB	57.1 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-competitions/kaggle/134561/logos/thumb76_76.png?G...	56.9 KiB	55.8 KiB
a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy `a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy`	storage.googleapis.com/kaggle-organizations/855/thumbnail.png	51.3 KiB	50.1 KiB
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/datasets-landing@1.png	73.4 KiB	46.2 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	storage.googleapis.com/kaggle-media/Images/Header_560x280_04-2.png	46.4 KiB	45.2 KiB
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/discussions-landing@1.png	62.5 KiB	39.3 KiB
a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy `a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy`	storage.googleapis.com/kaggle-organizations/3837/thumbnail-2.png	33.6 KiB	32.5 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > a.sc-gstvan > div.sc-amjVG `div.sc-ekA-dNx > div.sc-jTdpvq > a.sc-gstvan > div.sc-amjVG`	storage.googleapis.com/kaggle-avatars/thumbnails/3399668-kg.jpg	30.3 KiB	28.7 KiB
a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy `a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy`	storage.googleapis.com/kaggle-organizations/4582/thumbnail.png	28.2 KiB	27.1 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-datasets-images/4305/6656/174b3eae6099dbc6ef1149c...	20.5 KiB	19.4 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/external/rpWnThEeFpgquiBqnkuDsO-h5inX2a0FnYabeXwZZUU/htt...	18.4 KiB	18.2 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > a.sc-gstvan > div.sc-amjVG `div.sc-ekA-dNx > div.sc-jTdpvq > a.sc-gstvan > div.sc-amjVG`	storage.googleapis.com/kaggle-avatars/thumbnails/26782-kg.png	17.6 KiB	16.0 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-datasets-images/612177/5023398/ed4470482e04000d11...	14.6 KiB	13.5 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > a.sc-gstvan > div.sc-amjVG `div.sc-ekA-dNx > div.sc-jTdpvq > a.sc-gstvan > div.sc-amjVG`	/kaggle-avatars/thumbnails/15559822-kg.png?t=2025-07-02-2...	14.3 KiB	12.7 KiB
a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy `a.sc-jHCVDH > div.sc-ekA-dNx > div.sc-jTdpvq > img.sc-lTCXy`	storage.googleapis.com/kaggle-organizations/1202/thumbnail.png%3Fr=601	11.2 KiB	10.7 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-media/Images/Screenshot 2026-03-17 10.04.44 AM.png	11.4 KiB	10.3 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-datasets-images/1346/2425/573bbb9b260839fc8208792...	9.0 KiB	7.9 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-avatars/thumbnails/13838978-kg.jpg?t=2024-10-04-0...	6.3 KiB	5.2 KiB
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-competitions/kaggle/133469/logos/thumb76_76.png?G...	4.8 KiB	4.2 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:341.506 label:Time to first byte subpart:timeToFirstByte] map[duration:1342.46 label:Resource load delay subpart:resourceLoadDelay] map[duration:266.665 label:Resource load duration subpart:resourceLoadDuration] map[duration:583.693 label:Element render delay subpart:elementRenderDelay]]

lhId: page-23-IMG

nodeLabel: div.sc-cSiyUa > section.sc-cEpjUL > div.sc-jxfsUQ > img

path: 1,HTML,1,BODY,0,DIV,2,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,1,DIV,0,IMG

selector: div.sc-cSiyUa > section.sc-cEpjUL > div.sc-jxfsUQ > img

snippet: <img src="/static/images/home/logged-out/hero-illo.svg" alt="" style="width: 100%;">

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-23-IMG

nodeLabel: div.sc-cSiyUa > section.sc-cEpjUL > div.sc-jxfsUQ > img

path: 1,HTML,1,BODY,0,DIV,2,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,1,DIV,0,IMG

selector: div.sc-cSiyUa > section.sc-cEpjUL > div.sc-jxfsUQ > img

snippet: <img src="/static/images/home/logged-out/hero-illo.svg" alt="" style="width: 100%;">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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
www.kaggle.com/static/assets/app.js?v=b2dca7301fc0aab7	1.0 MiB	7.7 s
fonts.googleapis.com/css2?family=Google+Symbols:wght,FILL@400..700,0..1	508 B
www.kaggle.com/static/assets/vendor.js?v=f36df333f5148fa7	967.1 KiB	12.2 s
fonts.googleapis.com/css2?family=Roboto+Mono:ital,wght@0,100..700;1,100..700	753 B
/p.css?s=1&k=tql2nih&ht=tk&f=40891.40892.40899.40904&a=20...	172 B	759 ms
use.typekit.net/tql2nih.css	982 B	754 ms
www.kaggle.com/static/assets/runtime.js?v=16c84880ce9121ae	6.7 KiB
www.kaggle.com/static/assets/app.css?v=a53f951c511cf82e	770 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.

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

URL	Time Spent
kaggle.com/	881 ms
www.kaggle.com/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Who's on Kaggle? AI Builders Test your AI skills against the world's best. Com… `div.sc-fJxzGP > div.sc-cSiyUa > section.sc-cEpjUL > div.sc-cEzlxh`	0.146

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 8.4 s 1.4 MiB

URL	Transfer Size	Est Savings
www.kaggle.com/static/assets/app.js?v=b2dca7301fc0aab7	1.0 MiB	732.5 KiB
www.kaggle.com/static/assets/vendor.js?v=f36df333f5148fa7	942.9 KiB	477.1 KiB
/_/scs/abc-static/_/js/k=gapi.lb.en.HLcjcliCxoY.O/m=auth2...	107.9 KiB	80.4 KiB
accounts.google.com/gsi/client	95.4 KiB	79.6 KiB
www.googletagmanager.com/gtag/js?id=G-T7QHS60L4Q	157.5 KiB	63.0 KiB
www.kaggle.com/static/assets/9469.dabe1046ea806696.js	42.7 KiB	30.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.kaggle.com/static/assets/app.js?v=b2dca7301fc0aab7	3.1 s	2.3 s	494 ms
Unattributable	1.3 s	102 ms	0.0 ms
www.kaggle.com/static/assets/vendor.js?v=f36df333f5148fa7	476 ms	46 ms	373 ms
www.kaggle.com/	429 ms	45 ms	9.1 ms
www.googletagmanager.com/gtag/js?id=G-T7QHS60L4Q	331 ms	270 ms	57 ms
/_/scs/abc-static/_/js/k=gapi.lb.en.HLcjcliCxoY.O/m=auth2...	116 ms	76 ms	39 ms
www.kaggle.com/static/assets/9469.dabe1046ea806696.js	102 ms	81 ms	21 ms
accounts.google.com/gsi/client	58 ms	24 ms	32 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.0 s
Other	1.1 s
Script Parsing & Compilation	1.1 s
Style & Layout	506 ms
Garbage Collection	154 ms
Rendering	88 ms
Parse HTML & CSS	38 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
/s/googlesymbols/v419/HhyqU5Ak9u-oMExPeInvcuEmPosC9zS3FYk...	1.3 MiB
www.kaggle.com/static/assets/app.js?v=b2dca7301fc0aab7	1.0 MiB
www.kaggle.com/static/assets/vendor.js?v=f36df333f5148fa7	967.1 KiB
i.imgur.com/z62wCWj.png	212.9 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/trai...	203.7 KiB
www.kaggle.com/static/images/home/logged-out/hero-illo.svg	187.8 KiB
www.googletagmanager.com/gtag/js?id=G-T7QHS60L4Q	157.9 KiB
/Arturus/kaggle-web-traffic/refs/heads/master/images/auto...	153.0 KiB
www.kaggle.com/static/images/home/logged-out/benchmarks-landing@1.png	149.2 KiB
www.kaggle.com/static/images/home/logged-out/benchmarks-community@1.png	140.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/benchmarks-landing@1.png
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/datasets-landing@1.png
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/competitions-detail@1.png
div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh `div > div.sc-gHlpEC > a.sc-bIXARr > img.sc-hotPxh`	www.kaggle.com/static/images/home/logged-out/discussions-landing@1.png
div.sc-cSiyUa > section.sc-cEpjUL > div.sc-jxfsUQ > img `div.sc-cSiyUa > section.sc-cEpjUL > div.sc-jxfsUQ > img`	www.kaggle.com/static/images/home/logged-out/hero-illo.svg
Kaggle `div.sc-cGKHkA > div.sc-gGGBMi > a > img.sc-dSnXRV`	www.kaggle.com/static/images/site-logo.svg
Kaggle `div.sc-cGKHkA > div.sc-gGGBMi > a > img.sc-dSnXRV`	www.kaggle.com/static/images/site-logo.svg
div.sc-cSiyUa > div.sc-dQEXcY > div.sc-inuzel > img `div.sc-cSiyUa > div.sc-dQEXcY > div.sc-inuzel > img`	www.kaggle.com/static/images/site-logo.svg

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

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 16 long tasks found

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 130 ms

○INP breakdown

○Avoid non-composited animations

100

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/external/rpWnThEeFpgquiBqnkuDsO-h5inX2a0FnYabeXwZZUU/htt...	48 x 48 (1.00)	880 x 766 (1.15)
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	storage.googleapis.com/kaggle-media/blog/research-grant.png	48 x 48 (1.00)	1080 x 608 (1.78)
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	storage.googleapis.com/kaggle-media/Images/Header_560x280_04-2.png	48 x 48 (1.00)	560 x 280 (2.00)
div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img `div.sc-ekA-dNx > div.sc-jTdpvq > div.sc-hNqkyh > img`	/kaggle-media/Images/Screenshot 2026-03-17 10.04.44 AM.png	48 x 48 (1.00)	211 x 185 (1.14)

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.kaggle.com/cookies	Learn more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`