Let’s review all the measurements we’ve done so far. In the graphs below, I have plotted against the different load time optimization steps that we have taken:
- Compressing images and using Google hosted JQuery
- Using of CloudFlare CDN
In the left chart the shows the first-run load-times from Amsterdam, in the right chart the second-run load-times.
A dramatic improvement of +- 10 sec to +- 2 sec! Again, keep in mind that this is based on single samples, and there may be considerable fluctuations between results. For the second time loading of the website differences are much less significant. This was expected, because there is also less to win. What stands out is the loading time of the header image when w3 total cache is used. Apparently there is an issue in the browser caching instructions and the image is loaded from the server.
From Montreal, we also see an improvement, but it is smaller. From +- 10 sec to +- sec 6. Here, the advantage of the CloudFlare CDN is minimal for some unknown reason. Also after loading a second time the difference between unoptimized and fully optimized is again quite small
To conclude, I would like to revisit the first chart we made, the loading time of the Web page. This is now looking a whole lot better:
All in all there, it is certainly possible to gain a lot if you decide to optimize your website. But before you start to all kinds of trendy optimization tricks, start at the same thing that already mattered 10 years ago, have a look at your images sizes 🙂
The last weeks, performance seems to have decreased again, especially when I use the WordPress back-end. This is all dynamically generated, and I use a lot of WordPress plugins. I believe the processing power of my Versio server is currently the biggest bottleneck. I’ll keep you posted if new developments arise.