kinescopecdn.net speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:04 UTC. Grade B (81/100), with the screenshots, the timings and the fixes that matter.

https://kinescopecdn.net/

20 October 2026 at 15:04 UTC · Free test · report pt_121bcc5cfdb6
Grade
B
81/100
Performance77/100
Structure88/100

14 audit(s) passed, 2 need work

First byte (TTFB)1.07 smeasured from this server
Fully loaded1.07 sfirst byte + slowest asset
Requests1document + assets
Page weight392 Bcompressed transfer
HTML document392 Bno compression
ProtocolHTTP/2kinescope-engine

Where the first byte went

  • DNS lookup 254 ms 24%
  • TCP connect 194 ms 18%
  • Server wait 623 ms 58%

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 88% of 4,999 pages tested here1.07 s against a median of 448 ms
Page weightlighter than 99% of 4,999 pages tested here392 B against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.07 s against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 took 1.07 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 392 B over 1 request(s), which is lean.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.

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.

No screenshot for this report.

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1071 ms. Of that, 623 ms was the server thinking and 448 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.

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.

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.