Alrighty, let’s dive into this retro test from 2018, where I spent way too much time chasing that elusive perfect page speed score. It’s been a while since I revisited this topic, but I think it’s worth sharing my experiences, the ups and downs, and what I learned along the way.
So, here’s the deal: I was working on optimizing a couple of websites, and my goal was simple—get an A or at least a B score on GTMetrix. I also ran tests on Pingdom Tools, but honestly, GTMetrix was my go-to for reliable results.
One of the projects I worked on was maskice.hr, an e-commerce web shop. Despite throwing everything at it—near-perfect image compression, the Swift Performance caching plugin, Cloudflare as a CDN, and even Amazon SES + G Suite for email—it still hovered around a B grade on GTMetrix, with load times ranging from 4.8 to 8 seconds.
The problem? Web shops are complex beasts. They’re loaded with analytics scripts, live chat systems, and other external resources that you can’t just defer or cache. For example, Google Analytics and Facebook scripts were essential for customer experience and ad targeting, but they added to the load time.
Back then (in 2018), there’s this blog site. Running on shared hosting from Studio4Web (affiliated with them, check more here for my affiliate link), it loads in about 2 seconds on GTMetrix. Why? Because it’s a simple one-pager with minimal content, optimized using WPMU Dev’s Hummingbird Caching plugin and Optimus (now known as: Smush Pro) for image compression. Sometimes, less is more. As of 2022 and onwards, it’s been moved to a VPS with more optimizations and switched to other plugin solutions. If you’re curious about the specifics of that transition, you can check out the blog update from that time.
Here’s what I learned during this optimization journey. First, using a CDN like Cloudflare, or KeyCDN is a game-changer. It helps distribute content globally, reducing latency and improving load times.
Second, investing in a good server is non-negotiable. A well-configured VPS, like DigitalOcean with cPanel, can work wonders. Shared hosting has its limits, and if you’re serious about speed, you need a server that can handle the load. As of 2024, if you don’t want to deal with shared hosting, you’re on your own—there are plenty of options out there, from VPS to cloud hosting, depending on your needs and budget.
Third, image optimization is crucial. Compressing images and converting them to formats like WEBP can significantly reduce their size without sacrificing quality. This alone can shave seconds off your load time.
Fourth, leveraging caching plugins is a must. Whether you go for premium options like WP Rocket and Swift Performance or free ones like WP Super Cache and Autoptimize, caching can make a huge difference.
Fifth, minifying and compressing CSS and JavaScript files is essential. Smaller files mean faster rendering, and every millisecond counts when you’re chasing that perfect score.
Sixth, limiting external scripts is another key strategy. Hosting scripts locally whenever possible and deferring their parsing can reduce reliance on third-party resources, which often slow things down.
Finally, regular testing is a must. Tools like GTMetrix, Pingdom, and Google PageSpeed Insights are your best friends. They provide valuable insights and help you stay on top of performance issues.
Fast forward a bit, and I realized something important: Time to First Byte (TTFB) is the new king. By early 2018, Google started prioritizing TTFB and First Contentful Paint (FCP). A slow TTFB meant a slower FCP, and that’s bad news, especially for mobile users.
From my tests, I saw that a TTFB of less than 300ms was ideal, resulting in an FCP median of around 1.1 seconds. Achieving this required a well-optimized server, often a VPS, capable of quickly loading scripts and delivering content.
Server optimization is non-negotiable. A fast, well-configured server is the backbone of good performance. Without it, no amount of caching or image compression will save you.
Balancing functionality and speed is another challenge. External scripts like analytics and live chat are important, but they can slow you down. Finding the right balance is key.
Regular testing is a must. Tools like GTMetrix and PageSpeed Insights are invaluable, but you need to test regularly to stay on top of things. Performance optimization isn’t a one-time task—it’s an ongoing process.
Adapting to algorithm changes is also crucial. Google’s algorithms are always evolving, and what worked yesterday might not work tomorrow. Staying informed and adjusting your strategies accordingly is the only way to stay ahead.
Looking back, chasing that perfect page speed score was a mix of frustration and satisfaction. It taught me that optimization is a continuous process, not a one-time fix. Whether you’re running a complex e-commerce site or a simple blog, the principles remain the same: optimize your server, compress your assets, and minimize reliance on external resources.
And hey, if you’re still struggling with page speed, don’t sweat it. Even with all the tools and techniques out there, perfection is hard to achieve. But with persistence and a bit of experimentation, you can get pretty close.
So, here’s to faster websites, happier users, and fewer sleepless nights spent staring at GTMetrix reports.
Notice: This post was originally written in 2018 and has been updated and combined with its follow-up for clarity and flow. The text was proofread and edited with the assistance of AI tools (DeepSeek V3 and OpenAI ChatGPT 4.o) to ensure readability and consistency. Cover image was generated using Twitter/X Grok AI