registry.in speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:32 UTC. Grade D (66/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 77 ms 9%
- TCP connect 31 ms 4%
- Server wait 753 ms 88%
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 took 860 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 39.70 MB over 8 request(s), which is lean. Media files are 99% of it, so let video load on demand instead of on first paint.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- The largest element painted at 1.52 s, inside the 2.5 s Google calls good.
- The main thread was blocked for 74 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.
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, 39.70 MB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 860 ms. Of that, 753 ms was the server thinking and 108 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.
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.
Total page weight
high impactThe page transfers 39.70 MB across 8 request(s), with the document itself at 1.2 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Cache static assets
medium impact1 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://registry.in/assets/front/assets/css/animate1.css | css | 200 | 991 ms | 4.8 KB |
| https://registry.in/assets/front/assets/css/stylesheet1.css | css | 200 | 984 ms | 20.0 KB |
| https://registry.in/assets/front/assets/landing/registry.in.mov | media | 200 | 909 ms | 39.48 MB |
| https://registry.in/assets/front/assets/landing/favicon.png | images | 200 | 874 ms | 3.8 KB |
| https://registry.in/assets/admin/website_logo/1641193390_logo.png | images | 200 | 856 ms | 13.5 KB |
| https://www.googletagmanager.com/gtag/js?id=G-410FW91SMF 3rd party | javascript | 200 | 556 ms | 185.0 KB |
| https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap 3rd party | css | 200 | 526 ms | 238 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.