www.kaggle.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:02 UTC. Grade A (91/100), with the screenshots, the timings and the fixes that matter.

https://www.kaggle.com/

20 October 2026 at 14:02 UTC · Free test · report pt_d43a85b4629a
Grade
A
91/100
Performance95/100
Structure85/100

11 audit(s) passed, 5 need work

First byte (TTFB)279 msmeasured from this server
Fully loaded1.03 sfirst byte + slowest asset
Requests13document + assets
Page weight1.17 MBcompressed transfer
HTML document2.3 KBbr
ProtocolHTTP/3server not sent
Third-party183.8 KBother hosts

Where the first byte went

  • DNS lookup 80 ms 29%
  • TCP connect 33 ms 12%
  • Server wait 166 ms 59%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 79% of 4,999 pages tested here279 ms against a median of 449 ms
Page weightheavier than 67% of 4,999 pages tested here1.17 MB against a median of 650.3 KB
Fully loadedfaster than 92% of 4,999 pages tested here1.03 s against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte arrived in 279 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 1.17 MB over 13 request(s), which is lean. Javascript files are 98% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Javascript 4 requests
1.15 MB 98%
Images 1 request
15.0 KB 1%
Css 2 requests
780 B 0%
Html 5 requests
536 B 0%

Transfer size, compressed as sent. 13 request(s) in total, 1.17 MB across all of them.

Top issues

Render-blocking resources

high impact

6 render-blocking resource(s) in the document head (3 script(s), 3 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

medium impact

The page transfers 1.17 MB across 13 request(s), with the document itself at 2.3 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: vendor.js (999.4 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Third-party weight

low impact

5 third-party host(s) serve 183.8 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Waterfall

Slowest requests

HTMLwww.kaggle.com/static/json/manifest.json
754 ms
HTMLwww.kaggle.com/static/assets/app.js
751 ms
HTMLwww.kaggle.com/static/assets/app.css
750 ms
HTMLwww.kaggle.com/static/assets/runtime.js
743 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
665 ms
JAVASCRIPTwww.google.com/recaptcha/enterprise.js
652 ms
HTMLaccounts.google.com/gsi/client
646 ms
CSSfonts.googleapis.com/css
624 ms
CSSfonts.googleapis.com/css2
614 ms
IMAGESwww.kaggle.com/static/images/favicon-new.ico
607 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.kaggle.com/static/json/manifest.jsonhtml404754 ms134 B
https://www.kaggle.com/static/assets/app.js?v=5078cf89a5430e8fhtml404751 ms134 B
https://www.kaggle.com/static/assets/app.css?v=81622af21c90f30chtml404750 ms134 B
https://www.kaggle.com/static/assets/runtime.js?v=ed5f69452a042795html404743 ms134 B
https://www.googletagmanager.com/gtag/js?id=G-T7QHS60L4Q 3rd partyjavascript200665 ms176.7 KB
https://www.google.com/recaptcha/enterprise.js?render=6LcVUOAUAAAAAP8nMSGuW46uJC5Zf6-PCYKN5xxv 3rd partyjavascript200652 ms679 B
https://accounts.google.com/gsi/client 3rd partyhtml403646 ms0 B
https://fonts.googleapis.com/css?family=Inter:400,400i,500,500i,600,600i,700,700i&display=swap 3rd partycss200624 ms324 B
https://fonts.googleapis.com/css2?family=Google+Symbols:FILL,[email protected],200..700&display=block 3rd partycss200614 ms456 B
https://www.kaggle.com/static/images/favicon-new.icoimages200607 ms15.0 KB
https://www.kaggle.com/static/assets/vendor.js?v=f3e86a541bb15dbbjavascript200601 ms999.4 KB
https://apis.google.com/js/api.js 3rd partyjavascript200568 ms5.7 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.