i993.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:06 UTC. Grade A (95/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 89 ms 28%
- TCP connect 60 ms 19%
- Server wait 165 ms 53%
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
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 314 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 10.0 KB over 8 request(s), which is lean. Images files are 53% 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 624 ms, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.006), so nothing jumps under the reader's cursor.
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.
Screenshot
What the page looks like
Loaded in headless Chromium on this server. Click an image to open it full size.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 8 request(s) in total, 10.0 KB across all of them.
Top issues
Render-blocking resources
high impact3 render-blocking resource(s) in the document head (0 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.
Cache static assets
medium impact2 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.
Waterfall
Slowest requests
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://mc.yandex.ru/watch/101930307 3rd party | other | 302 | 1.07 s | 0 B |
| https://my.rtmark.net/img.gif?f=sync&lr=1&partner=a86cac3c7b90fe9e4a995ae094e38cb961f30649a9539312ee91a6c1ceaf4c58 3rd party | images | 200 | 607 ms | 43 B |
| https://my.rtmark.net/p.js?f=sync&lr=1&partner=a86cac3c7b90fe9e4a995ae094e38cb961f30649a9539312ee91a6c1ceaf4c58 3rd party | javascript | 200 | 512 ms | 424 B |
| https://i993.com/assets/logo.svg | images | 200 | 415 ms | 5.2 KB |
| https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:ital,wght@0,200..800;1,200..800&display=swap 3rd party | css | 200 | 403 ms | 367 B |
| https://i993.com/assets/index.css | css | 200 | 377 ms | 670 B |
| https://i993.com/assets/normalize.css | css | 200 | 376 ms | 1.5 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.