
10 hosting mistakes that slow down your website
When a website feels slow, people usually blame the design or the images. Often the real problem sits underneath, in how the website is hosted. These are the ten hosting mistakes we find most often when we audit a slow business website, and what to do about each.
Why hosting matters for speed
Every time someone opens a page, their browser asks your server for it. The server has to receive the request, run your website's code, read from the database, build the page and send it back, along with images, styles and scripts. If any step is slow, the visitor waits.
Speed matters for two reasons. Visitors leave pages that take too long to appear, especially on mobile. And Google measures real-world loading experience through Core Web Vitals and uses it as one of many ranking signals. A slow server makes both worse before your design even gets a chance.
1. Choosing the cheapest shared plan for a business site
On a budget shared plan, your website shares processor and memory with hundreds of others. When a neighbour gets busy, you slow down. Many plans also cap the number of processes your site can run at once, so a few visitors at the same time can queue up.
Fix: if the website brings you enquiries, bookings or sales, move to hosting with reserved resources, such as a well-configured virtual or dedicated server. See our comparison of shared, VPS and managed hosting.
2. No page caching
Without caching, a WordPress site rebuilds every page from scratch for every visitor: PHP runs, the database is queried, the theme is assembled. With caching, the finished page is stored and served instantly to the next visitor.
Fix: enable server-level page caching where possible, or a reputable caching plugin such as WP Rocket. Our guide to the best WordPress speed plugins compares the options. Make sure logged-in users, carts and checkouts are excluded, so shops still work correctly.
3. An outdated PHP or Node.js version
Newer versions of PHP are not just more secure; they are also generally faster at running the same code. Sites left on an old version for years miss out on that improvement, and stop receiving security fixes. Read why in our article on outdated PHP.
Fix: test your website on a current, supported version on a staging copy, fix any plugin or theme conflicts, then switch the live site.
4. Servers far from your visitors
Data travels fast, but distance still adds delay to every request. A Cyprus business with most customers in Europe gains little from a server on another continent.
Fix: host close to your main audience. For Cyprus and wider European audiences, servers in the EU are a sensible choice, and they also simplify GDPR questions about where personal data is stored.
5. No content delivery network for static files
Images, fonts, stylesheets and scripts make up most of a page's weight. A content delivery network (CDN) keeps copies of these files in locations around the world and serves them from the nearest one.
Fix: put a CDN in front of your website if you have visitors in several countries, or heavy media. Configure it carefully so that dynamic pages and forms keep working.
6. Slow or overloaded database
WordPress and WooCommerce lean heavily on the database. Over time, tables fill with old revisions, expired temporary data, spam comments and logs from plugins. Some plugins also run inefficient queries on every page.
Fix: clean up revisions and expired data regularly, add object caching such as Redis on busier sites, and identify the plugins behind slow queries. A server with enough memory for the database matters too.
7. HTTP/2, compression and modern protocols switched off
Modern web servers can send many files over one connection at once and compress text files before sending them. Some older or poorly configured servers still do neither.
Fix: make sure your server supports HTTP/2 or HTTP/3, compresses text with gzip or Brotli, and sends sensible cache headers so browsers do not download the same files on every visit.
8. Running the website and heavy jobs on the same small server
Backups, image optimisation, email sending, imports from suppliers and scheduled reports all take server power. When they run in the middle of the working day on a small server, visitors feel it.
Fix: schedule heavy tasks for quiet hours, move email sending to a proper email service, and make sure backups run efficiently and are stored offsite rather than filling the same disk.
9. No monitoring, so problems go unnoticed
A site can get slower gradually, or slow down only at certain times. Without monitoring, you only find out when a customer complains, if they bother.
Fix: monitor uptime and response time around the clock, with alerts to someone who can act. Check real-user data in Google Search Console's Core Web Vitals report every month.
10. Blaming the hosting for problems in the website itself
Hosting is not always the culprit. Huge uncompressed images, a heavy page builder, ten tracking scripts and an autoplay video will be slow anywhere. Upgrading the server helps less than people hope if the page itself is bloated.
Fix: test a page in PageSpeed Insights. If the server response time is slow, look at hosting. If the page weight and script count are high, look at the website. Usually both need some attention.
How to tell where the slowness comes from
| Symptom | Likely cause |
|---|---|
| Every page is slow, even simple ones | Server, caching or PHP version |
| Slow at busy times, fine at night | Shared resources or too little memory |
| Admin area slow, front end fine | Database or heavy plugins |
| Page appears late, then jumps around | Large images, fonts or scripts on the page |
| Fast in Cyprus, slow abroad | Server location, no CDN |
| Checkout or search slow, rest fine | Database queries or uncached dynamic pages |
A quick action plan
- Run your home page and a key service or product page through PageSpeed Insights on mobile.
- Check your PHP version and whether page caching is active.
- Ask your host where the server is, what resources you actually have, and whether HTTP/2 and compression are on.
- Remove plugins and scripts you do not use.
- Set up uptime and speed monitoring.
How we can help
Our managed hosting is configured for speed from the start: dedicated servers in Germany, server-level caching, current PHP and Node.js versions, HTTP/2, compression and around-the-clock monitoring. We move your site across for you and check it is faster after the move. To keep it that way, our website management plans handle updates, clean-up and performance checks every month.