getcomposer.org speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:27 UTC. Grade A (96/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 56 ms 19%
- TCP connect 63 ms 22%
- Server wait 173 ms 59%
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 292 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 230.8 KB over 5 request(s), which is lean. Images files are 49% of it, so resize and recompress the largest images before anything else.
- 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 804 ms, inside the 2.5 s Google calls good.
- Layout shift is 0.128 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
Fix first: Image delivery and format - 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.
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, 230.8 KB across all of them.
Top issues
Image delivery and format
medium impact0 image(s) over 200 KB and 1 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.
Cache static assets
medium impact2 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://getcomposer.org/build/app.js?v=3 | javascript | 200 | 397 ms | 105.8 KB |
| https://getcomposer.org/img/private-packagist-logo-horizontal-2025.svg | images | 200 | 373 ms | 5.5 KB |
| https://getcomposer.org/img/logo-composer-transparent3.png | images | 200 | 305 ms | 107.1 KB |
| https://getcomposer.org/build/app.css?v=3 | css | 200 | 301 ms | 11.0 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.