filezilla-project.org speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:07 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 43 ms 8%
- TCP connect 158 ms 29%
- Server wait 349 ms 63%
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 550 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 16.9 KB over 8 request(s), which is lean. Images files are 40% 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 1.32 s, inside the 2.5 s Google calls good.
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.
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. 8 request(s) in total, 16.9 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 550 ms. Of that, 349 ms was the server thinking and 201 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.
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://filezilla-project.org/style.css?v=13 | css | 200 | 697 ms | 2.4 KB |
| https://filezilla-project.org/images/sponsors/route4me.png | images | 200 | 682 ms | 2.2 KB |
| https://filezilla-project.org/images/sponsors/bairesdev.png | images | 200 | 666 ms | 1.2 KB |
| https://filezilla-project.org/images/sponsors/buy-fans.png | images | 200 | 604 ms | 1.8 KB |
| https://filezilla-project.org/images/sponsors/ndchost.png | images | 200 | 575 ms | 680 B |
| https://filezilla-project.org/images/sponsors/automatio.png | images | 200 | 521 ms | 1.0 KB |
| https://filezilla-project.org/new Blob([xhr.response] | other | 0 | 0 ms | 0 B |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.