ffmpeg.org speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 16:28 UTC. Grade C (77/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 59 ms 7%
- TCP connect 188 ms 22%
- Server wait 595 ms 71%
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 843 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 663.1 KB over 13 request(s), which is lean. Images files are 48% of it, so resize and recompress the largest images before anything else.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- The largest element painted at 2.15 s, inside the 2.5 s Google calls good.
- The main thread was blocked for 116 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. 13 request(s) in total, 663.1 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 843 ms. Of that, 595 ms was the server thinking and 247 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.
Compress text responses
high impact4 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 245.4 KB 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.
Render-blocking resources
high impact6 render-blocking resource(s) in the document head (2 script(s), 4 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.
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 impact12 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://ffmpeg.org/favicon.ico | images | 200 | 999 ms | 31.3 KB |
| https://ffmpeg.org/css/simple-sidebar.css | css | 200 | 970 ms | 1.6 KB |
| https://ffmpeg.org/css/style.min.css | css | 200 | 946 ms | 6.4 KB |
| https://ffmpeg.org/css/bootstrap.min.css | css | 200 | 918 ms | 106.9 KB |
| https://ffmpeg.org/css/font-awesome.min.css | css | 200 | 875 ms | 21.5 KB |
| https://ffmpeg.org/js/bootstrap.min.js | javascript | 200 | 867 ms | 34.8 KB |
| https://ffmpeg.org/img/dascha-ffmpeg-ampere.png | images | 200 | 843 ms | 128.4 KB |
| https://ffmpeg.org/js/jquery.min.js | javascript | 200 | 801 ms | 82.3 KB |
| https://ffmpeg.org/img/coverity-lifetime-2024-08.PNG | images | 200 | 799 ms | 61.6 KB |
| https://ffmpeg.org/img/AmpereServer1.avif | images | 200 | 799 ms | 48.4 KB |
| https://ffmpeg.org/img/AmpereServer2.avif | images | 200 | 797 ms | 48.2 KB |
| https://ffmpeg.org/img/ffmpeg3d_white_20.png | images | 200 | 779 ms | 633 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.