cyon.ch speed test — 20 Oct 2026

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

https://cyon.ch/

20 October 2026 at 14:18 UTC · Free test · report pt_a2d6a00477a0
Grade
B
89/100
Performance91/100
Structure86/100

12 audit(s) passed, 4 need work

First byte (TTFB)528 msmeasured from this server
Fully loaded1.06 sfirst byte + slowest asset
Requests2document + assets
Page weight19.7 KBcompressed transfer
HTML document449 Bno compression
ProtocolHTTP/3server not sent

Where the first byte went

  • DNS lookup 206 ms 39%
  • TCP connect 93 ms 18%
  • Server wait 229 ms 43%

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 57% of 4,999 pages tested here528 ms against a median of 448 ms
Page weightlighter than 94% of 4,999 pages tested here19.7 KB against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.06 s against a median of 1.84 s
Requestssends fewer requests than 96% of 4,999 pages tested here2 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 528 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 19.7 KB over 2 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.
  • It runs over HTTP/3, 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.

Screenshot

What the page looks like

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

Desktop screenshot of cyon.ch
Desktop 1366 × 768 · 4.7 KB · page is 768 px tall
Mobile screenshot of cyon.ch
Mobile 390 × 844 · 2.7 KB · page is 2121 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 paintnot reportedgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paintnot reportedfirst content on screen
Browser page weight20.2 KB2 request(s), scripts included
Largest contentful paintnot reported
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
19.3 KB 98%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 528 ms. Of that, 229 ms was the server thinking and 299 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.

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

JAVASCRIPTcyon.ch/kramericaindustries.ac_v2.lib.js
532 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://cyon.ch/kramericaindustries.ac_v2.lib.jsjavascript200532 ms19.3 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.