Zinn® CacheWordPress speed test: the same page with Zinn® Cache off and on
The same WordPress pages measured with the page cache off and on: mobile Lighthouse, median of 5 runs, dated. Then time both yourself from your own browser.
Time it yourself, from where you are
Press the button and your browser asks for the same page five times without the cache and five times with it, and shows how long each took to start arriving. Your result depends on your connection and where you are, which is the point: it is your own measurement.
Page: https://tranzly.io/
| Cache off | Cache on | |
|---|---|---|
| Median of 5 requests from your browser |
Measured with Lighthouse, mobile
Each page below was measured five times with the cache off and five times with it on, on a simulated mid-range phone on a slow 4G connection, the two taking turns. The figures are the median run.
https://tranzly.io/
| Cache off | Cache on | |
|---|---|---|
| Lighthouse performance score | 93 | 99 |
| Server response (time to first byte) | 1,464 ms | 19 ms |
| First Contentful Paint | 2,557 ms | 1,720 ms |
| Largest Contentful Paint | 2,610 ms | 1,807 ms |
| Speed Index | 2,595 ms | 1,777 ms |
| Total Blocking Time | 0 ms | 0 ms |
Measured on · Tool: Lighthouse 13.4.1 · 5 × 2
How the cache was turned off and on
Both columns are the same page. With the cache off, the address carries a test word the cache does not know, so the page is built by WordPress on every visit, as on a site without a page cache. With it on, the address carries a marketing tag that Zinn® Cache ignores, so it serves the saved copy. Every run checked the cache's own response header before it counted.
The tag also keeps the CDN in front of the site out of the measurement, so the difference you see is the page cache alone.
Each run used a fresh browser, the two sides took turns, and the slowdown for the phone and the connection was applied to the real page load.
What this does not tell you
These are fast, well-built pages. On a heavier site, a slow theme or a busy shop, WordPress takes longer to build each page and the cache saves more.
A cache makes the server answer sooner. Images, fonts and scripts still have to download, so the gain in the score is smaller than the gain in server time.
WordPress cache benchmark: a cached page against an uncached one
Included free with Zinn Digital® hosting
Get Zinn® Cache free on Zinn Digital® hosting
Every WordPress site on our own servers comes with Zinn® Cache installed and connected: the page cache is on, the Redis object cache is managed for you, and plugin updates arrive on their own. Zinn® Cache Pro is not included; add it to any site when you want it.