0xrpc.github.io speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:24 UTC. Grade A (98/100), with the screenshots, the timings and the fixes that matter.

https://0xrpc.github.io/

20 October 2026 at 12:24 UTC · Free test · report pt_fd1c22604714
Grade
A
98/100
Performance98/100
Structure98/100

15 audit(s) passed, 1 need work

First byte (TTFB)273 msmeasured from this server
Fully loaded539 msfirst byte + slowest asset
Requests2document + assets
Page weight5.0 KBcompressed transfer
HTML document2.8 KBgzip
ProtocolHTTP/3GitHub.com

Where the first byte went

  • DNS lookup 73 ms 27%
  • TCP connect 22 ms 8%
  • Server wait 177 ms 65%

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 bytefaster than 80% of 4,999 pages tested here273 ms against a median of 449 ms
Page weightlighter than 96% of 4,999 pages tested here5.0 KB against a median of 650.5 KB
Fully loadedfaster than 98% of 4,999 pages tested here539 ms 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 arrived in 273 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 5.0 KB over 2 request(s), which is lean. Css files are 44% of it, so split the stylesheet so the first screen does not download the whole site.
  • 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 556 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 67 ms in total, which is not enough to feel.

Fix first: Avoid extra redirects - Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

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.

Mobile screenshot of 0xrpc.github.io
Mobile 390 × 844 · 50.9 KB · page is 3717 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 paint556 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time67 mslong tasks during load
First contentful paint556 msfirst content on screen
Browser page weight5.6 KB2 request(s), scripts included
Largest contentful paint556 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time67 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 1 request
2.2 KB 44%

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

Top issues

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

CSS0xrpc.github.io/style.css
266 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://0xrpc.github.io/style.csscss200266 ms2.2 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.