railway.com speed test — 20 Oct 2026

The first byte arrived after 451 ms. Of that, 258 ms was the server thinking and 192 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.

0 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 0 B of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

1 image(s) over 200 KB and 0 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

5 render-blocking resource(s) in the document head (0 script(s), 5 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.

13 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.