www.king.com speed test — 20 Oct 2026

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

https://www.king.com/

20 October 2026 at 14:23 UTC · Free test · report pt_c7dd1e3135f2
Grade
A
92/100
Performance93/100
Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)470 msmeasured from this server
Fully loaded1.22 sfirst byte + slowest asset
Requests19document + assets
Page weight528.9 KBcompressed transfer
HTML document5.5 KBbr
ProtocolHTTP/3cloudflare
Third-party92 Bother hosts

Where the first byte went

  • DNS lookup 76 ms 16%
  • TCP connect 52 ms 11%
  • Server wait 343 ms 73%

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 byteslower than 52% of 4,999 pages tested here470 ms against a median of 448 ms
Page weightlighter than 56% of 4,999 pages tested here528.9 KB against a median of 650.5 KB
Fully loadedfaster than 87% of 4,999 pages tested here1.22 s against a median of 1.84 s
Requestssends fewer requests than 80% of 4,999 pages tested here19 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 470 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 528.9 KB over 19 request(s). Images files are 87% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 376 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.032), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 34 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.king.com
Mobile 390 × 844 · 271.7 KB · page is 3080 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint376 msgood is under 2.5 s
Cumulative layout shift0.032under 0.1 is stable
Total blocking time34 mslong tasks during load
First contentful paint344 msfirst content on screen
Browser page weight1,023.6 KB36 request(s), scripts included
Largest contentful paint376 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.032
Goodgood under 0.1, poor over 0.25
Total blocking time34 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 15 requests
459.8 KB 87%
Css 1 request
44.7 KB 8%
Javascript 1 request
18.8 KB 4%
Html 1 request
92 B 0%

Transfer size, compressed as sent. 19 request(s) in total, 528.9 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 470 ms. Of that, 343 ms was the server thinking and 128 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Waterfall

Slowest requests

HTMLwww.googletagmanager.com/ns.html
746 ms
IMAGESwww.king.com/media/yxfbnuyx/candy-crush.jpg
690 ms
IMAGESwww.king.com/media/4uplnlku/bg_jobs.webp
666 ms
JAVASCRIPTwww.king.com/js/global.min.js
648 ms
IMAGESwww.king.com/media/ccddscdy/king_yeti_tiffi__mrtoff…
645 ms
IMAGESwww.king.com/favicon/favicon.ico
643 ms
IMAGESwww.king.com/media/azme5gjf/farm-heroes.jpg
636 ms
CSSwww.king.com/css/style.min.css
634 ms
IMAGESwww.king.com/media/zkyjxa2s/bird-svg.webp
634 ms
IMAGESwww.king.com/assets/images/bubble-mint.webp
634 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.googletagmanager.com/ns.html?id=GTM-P6KML8MS 3rd partyhtml200746 ms92 B
https://www.king.com/media/yxfbnuyx/candy-crush.jpg?width=350&height=350&v=133770055909630000&format=webp&quality=60images200690 ms13.4 KB
https://www.king.com/media/4uplnlku/bg_jobs.webp?width=750&height=645&v=133809814207200000&format=webp&quality=60images200666 ms38.5 KB
https://www.king.com/js/global.min.js?v=QqfQEfNzGzv8fTsz4i-Mk9Mmw34sjt3En14ddFEPlU4javascript200648 ms18.8 KB
https://www.king.com/media/ccddscdy/king_yeti_tiffi__mrtoffee_party_desktop.webp?width=950&height=647&v=133809814197370000&format=webp&quality=60images200645 ms105.8 KB
https://www.king.com/favicon/favicon.icoimages200643 ms3.5 KB
https://www.king.com/media/azme5gjf/farm-heroes.jpg?width=350&height=350&v=133770056038330000&format=webp&quality=60images200636 ms16.8 KB
https://www.king.com/css/style.min.css?v=EzP_1Qz8BU9_Rv_FcOckGAZ1e1MXcyMD-ZKIvXGOs7scss200634 ms44.7 KB
https://www.king.com/media/zkyjxa2s/bird-svg.webp?width=340&height=425&v=133770056730330000&format=webp&quality=60images200634 ms13.5 KB
https://www.king.com/assets/images/bubble-mint.webpimages200634 ms6.4 KB
https://www.king.com/media/aplg20fk/logo.svg?width=110&height=74&v=133770142968670000images200634 ms3.1 KB
https://www.king.com/media/y0sdyzq4/hero-image.webp?width=1920&height=1080&v=133809811771700000&format=webp&quality=60images200601 ms85.8 KB
https://www.king.com/favicon/apple-touch-icon.pngimages200596 ms12.6 KB
https://www.king.com/media/fmmhfmbh/king_characters_playful_small.webp?width=600&height=288&v=133809814188200000&format=webp&quality=60images200589 ms43.3 KB
https://www.king.com/media/1h0p3eiy/49dc984afae67b4b5a71cc8c6f2f6953.jpg?width=350&height=350&v=133836615943770000&format=webp&quality=60images200588 ms12.6 KB
https://www.king.com/media/gycllehu/featured-graphic.webp?width=567&height=790&v=133809814226500000&format=webp&quality=60images200586 ms43.7 KB
https://www.king.com/media/w4yg44hu/candy-crush-saga.webp?width=260&height=190&v=133770850056330000&format=webp&quality=60images200585 ms10.2 KB
https://www.king.com/media/rjip4sei/hero-mobile-image.webp?width=768&height=1300&v=133809811788570000&format=webp&quality=60images200584 ms50.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.