There is a very specific moment in the life of every local media outlet: the news goes viral, the whole town (and the neighbouring town) visits the website at once, and the server decides it has had enough. It crashes, slows down, or simply returns a 500 error right when you have the most readers. It’s the paradox of digital success: the better you do, the closer you are to technical collapse.
When traffic spikes and the server gives up
Local media thrive on spikes. An accident on the national road, a town hall announcing construction work, an event that is discussed in the corner bar even before it is published. This type of content generates waves of visits concentrated in a few hours, and that’s where many shared hostings show their seams.
The problem is usually not the content or the design of the website, but the infrastructure behind it. A hosting service designed for stable traffic, with resources shared among dozens of websites, is simply not built to absorb ten thousand visits in an hour when it normally receives five hundred a day. It’s like trying to fit the whole neighbourhood in the elevator: technically, someone can fit, but not everyone at once.
Why WordPress struggles so much with massive visits
WordPress is fantastic for publishing quickly, but it generates each page dynamically by querying the database every time someone enters. If there’s no caching involved, each visit means extra work for the server. Multiply that by thousands of simultaneous users, and you’ll understand why the website collapses just when it needs to stay up the most.
Here, it’s not enough to just "install a caching plugin and cross your fingers." It helps to cushion the blow, but it doesn’t provide a shield. When the spike is real, you need something more robust working in front of the server.
The first line of defence: a well-configured CDN
A CDN (Content Delivery Network) acts as a buffer between your readers and your origin server. Instead of each visit hitting your hosting directly, the CDN serves cached versions of your pages from geographically distributed servers, much closer to the end user.
The practical result: your server breathes, pages load faster, and you also gain points in Core Web Vitals, which Google scrutinises when ranking. It’s one of those improvements that benefits the reader, the server, and SEO at the same time, something that doesn’t always align so well.
What your CDN needs to withstand the downpour
Not all CDNs are created equal. For a local media outlet with unpredictable spikes, it’s important to look for three things: dynamic caching capability (not just images and CSS, but also HTML), basic protection against attacks or malicious bots that take advantage of the chaos of a viral spike, and quick cache purging when you update a hot news item, because nothing is worse than serving an outdated version just when you’re correcting an important fact.
Even with all this set up well, there comes a point where the CDN alone is no longer enough. If the origin behind it remains weak, any request that isn’t cached will still bring down the server.
The leap to VPS: when shared hosting becomes too small
This is where many local media outlets take the step they have been postponing for months. Migrating from shared hosting to a scalable VPS for local media means no longer sharing resources with unknown websites and having a portion of the server dedicated exclusively to you, with the ability to expand CPU and RAM just when traffic demands it.
The great advantage of a well-configured VPS is that it allows you to anticipate. If you know that a local event with special coverage is coming up (municipal elections, local festivals, a high-profile trial), you can temporarily scale resources instead of praying that the shared hosting can withstand the strain.
For media with a more established newsroom, or that already manage several domains or subdomains with considerable traffic volumes, the next logical step is dedicated servers from GreenGeeks, where you don’t even share the physical machine with anyone else. It’s the difference between renting a room and owning the entire building.
Signs that you need to scale now
There are quite clear indicators that it’s time to move. If your website takes more than three seconds to load during peak hours, if you receive constant notices of "resource limit exceeded" from your hosting, or if every important news item comes with the ritual of refreshing the page in fear, you’re probably already late.
It’s also worth looking at reader behaviour. A user arriving from social media or from a breaking news notification has zero patience. If the website doesn’t load in a couple of seconds, they will go to another media outlet, and that lost reader won’t return just because the news was good.
How to combine CDN and VPS without dying in the attempt (technically)
The most sensible strategy is not to choose between CDN or VPS, but to use them together. The CDN absorbs the bulk of repeated and static traffic, while the VPS efficiently manages everything that needs to be processed in real-time: comments, contact forms, internal searches, or personalised content.
This combination drastically reduces the load on the origin server and provides breathing room even on the busiest days of the local news calendar. And the best part is that, once correctly configured, it stops being a recurring headache and becomes infrastructure that simply works in the background, which is exactly what any newsroom needs to get off their mind to focus on what matters: telling the story of what’s happening in their city well.
You may also like
