poki.com speed test — 20 Oct 2026

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

https://poki.com/

20 October 2026 at 12:32 UTC · Free test · report pt_f06fa0ccefd1

Re-test this page Test your own site

Grade

95/100

Performance100/100

Structure88/100

14 audit(s) passed, 2 need work

First byte (TTFB)192 msmeasured from this server

Fully loaded1.24 sfirst byte + slowest asset

Requests26document + assets

Page weight306.0 KBcompressed transfer

HTML document56.3 KBbr

ProtocolHTTP/3cloudflare

Third-party249.7 KBother hosts

Where the first byte went

DNS lookup 55 ms 29%
TCP connect 1 ms 1%
Server wait 136 ms 71%

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 94% of 4,999 pages tested here192 ms against a median of 449 ms

Page weightlighter than 71% of 4,999 pages tested here306.0 KB against a median of 650.5 KB

Fully loadedfaster than 86% of 4,999 pages tested here1.24 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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 server answered in 192 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 306.0 KB over 26 request(s). Images files are 82% 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.
82% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.00 s, inside the 2.5 s Google calls good.
The main thread was blocked for 72 ms in total, which is not enough to feel.

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.

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 paint1.00 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time72 mslong tasks during load

First contentful paint852 msfirst content on screen

Browser page weight1.38 MB308 request(s), scripts included

Failed requests4blocked or unreachable

Largest contentful paint1.00 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time72 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

249.7 KB 82%

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

Top issues

Render-blocking resources

high impact

12 render-blocking resource(s) in the document head (0 script(s), 12 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.

Third-party weight

medium impact

2 third-party host(s) serve 249.7 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.