isaidub.green speed test — 20 Oct 2026

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

https://isaidub.green/

20 October 2026 at 14:47 UTC · Free test · report pt_4c6d351944f2
Grade
B
88/100
Performance87/100
Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)674 msmeasured from this server
Fully loaded1.41 sfirst byte + slowest asset
Requests7document + assets
Page weight167.0 KBcompressed transfer
HTML document3.0 KBzstd
ProtocolHTTP/3cloudflare
Third-party155.3 KBother hosts

Where the first byte went

  • DNS lookup 85 ms 13%
  • TCP connect 27 ms 4%
  • Server wait 562 ms 83%

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 68% of 4,999 pages tested here674 ms against a median of 448 ms
Page weightlighter than 82% of 4,999 pages tested here167.0 KB against a median of 650.5 KB
Fully loadedfaster than 76% of 4,999 pages tested here1.41 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 674 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 167.0 KB over 7 request(s), which is lean. Javascript files are 93% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 93% 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 824 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 52 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.

Desktop screenshot of isaidub.green
Desktop 1366 × 768 · 92.1 KB · page is 3075 px tall
Mobile screenshot of isaidub.green
Mobile 390 × 844 · 68.6 KB · page is 3810 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 paint824 msgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time52 mslong tasks during load
First contentful paint824 msfirst content on screen
Browser page weight209.7 KB12 request(s), scripts included
Largest contentful paint824 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time52 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
155.3 KB 93%
Css 1 request
5.7 KB 3%
Images 3 requests
3.0 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 674 ms. Of that, 562 ms was the server thinking and 112 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.

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

IMAGESisaidub.green/favicon.ico
739 ms
IMAGESisaidub.green/favicon.png
690 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
343 ms
JAVASCRIPTyt.drainedrerolls.com/rxzPwQDJWJlMdr/Wgael
337 ms
CSSisaidub.green/style.min.css
304 ms
IMAGESisaidub.green/assets/images/folder.svg
231 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://isaidub.green/favicon.icoimages200739 ms1.4 KB
https://isaidub.green/favicon.pngimages200690 ms1.3 KB
https://www.googletagmanager.com/gtag/js?id=G-9M0PHTGQ8Y 3rd partyjavascript200343 ms155.3 KB
https://yt.drainedrerolls.com/rxzPwQDJWJlMdr/Wgael 3rd partyjavascript200337 ms25 B
https://isaidub.green/style.min.css?v=1.4css200304 ms5.7 KB
https://isaidub.green/assets/images/folder.svgimages200231 ms364 B
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.