widgetable.net speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:21 UTC. Grade A (94/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 90 ms 31%
- TCP connect 56 ms 20%
- Server wait 141 ms 49%
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 287 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 433.6 KB over 5 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.
- The largest element painted at 536 ms, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.028), so nothing jumps under the reader's cursor.
- The main thread was blocked for 3 ms in total, which is not enough to feel.
Fix first: Cache static assets - Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.
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. 5 request(s) in total, 433.6 KB across all of them.
Top issues
Cache static assets
medium impact4 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.
JavaScript weight
medium impact1 JavaScript file(s) over 200 KB: main.3e89bcfb.js (423.1 KB)
Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.
Strict-Transport-Security
low impactHSTS 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
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://widgetable.net/static/css/main.e6c13ad2.css | css | 200 | 315 ms | 337 B |
| https://widgetable.net/logo.icon.png | images | 200 | 277 ms | 9.3 KB |
| https://widgetable.net/static/js/main.3e89bcfb.js | javascript | 200 | 242 ms | 423.1 KB |
| https://widgetable.net/manifest.json | other | 200 | 204 ms | 290 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.