Skip to content
TECH Consult

Slow Website? The Usual Causes and How to Find Them One by One

Why a website loads slowly: oversized images, too many plugins, an overloaded server, old PHP. How to measure page speed and what to fix first.

Published 9 min read

A website that loads slowly loses visitors before they get to see what you sell. The trouble is that “it’s slow” can have many causes, and each one has a different fix. Moving to new hosting won’t help if the culprit is a huge photo on the home page, and optimising images won’t help if the server is overloaded. Below you’ll find how to measure properly, how to tell the causes apart and what to fix in which order.

Measure before you change anything

The feeling that a site is slow depends on the phone, the network and the time of day you opened it. To know whether a change helped, you need a measured starting point.

Free tools that give you numbers:

  • PageSpeed Insights (pagespeed.web.dev). Enter the address and you get a report for mobile and desktop, with a concrete list of problems.
  • Your browser’s developer tools. In Chrome or Edge, press F12, go to the Network tab and reload the page. You’ll see every file, how big it is and how long it took.
  • The Core Web Vitals report in the search engines’ webmaster tools, if the site has enough traffic. It shows the experience of real visitors, not a lab test.

Three metrics are worth tracking. According to the web.dev guide, a page counts as good when the largest visible element appears within 2.5 seconds (LCP), the page responds to a tap or click within 200 milliseconds (INP) and the content doesn’t jump around while loading (a CLS of 0.1 or less). The thresholds apply to 75% of real visits.

Test several times, at different times of day, and write the results down. Test an inner page too, not just the home page.

The server’s first response: slow or fast?

In the Network tab, the first row is the page itself. Hover over its timing bar and you’ll see “Waiting for server response” (TTFB, time to first byte). That’s how long the server thinks before sending the first byte.

This one number splits problems into two families:

  • The response is slow (over a second, for example). The problem is on the server: the application does too much work on every visit, the database is slow or the server is busy.
  • The response is fast, but the page loads slowly. The problem is in the page: big images, lots of scripts, external fonts, elements loaded from other sites.

For most small websites, the second family is to blame. Start there, because you can fix it without touching the server.

Images: the number one cause on small sites

Photos from a phone are usually several megabytes each. Uploaded straight to the site at full resolution, they turn a simple company page into a download of tens of megabytes.

What to do:

  1. Resize before uploading. An image shown across the full width of the screen needs no more than about 2000 pixels wide. One inside an article column needs far less.
  2. Use modern formats. WebP and AVIF usually take up much less space than JPEG at the same visible quality. WordPress accepts WebP uploads.
  3. Lazy loading. Images further down the page load only when the visitor scrolls to them. WordPress does this automatically for images in your content.
  4. Watch out for the home page slider. Five large rotating images means five images downloaded before the visitor sees anything.

In the Network tab, sort by the Size column. If the top files in the list are images over 500 KB, you’ve found your first problem.

Too many plugins and third-party scripts

Every WordPress plugin can add its own CSS and JavaScript files to every page, even pages where it isn’t used. A contact form plugin that loads its scripts on pages with no form is a typical example.

Elements loaded from other sites add time too: chat widgets, social media widgets, maps, embedded videos, several analytics codes added by different people over the years.

How to tidy up:

  • List your active plugins and ask of each one: do we still use it? Delete the ones you don’t. There’s a security bonus as well, explained in our article on WordPress security.
  • Replace an embedded map with a static image that links to the map.
  • For videos, use a preview image that loads the player only when clicked.
  • Keep a single analytics code.

Visual page builders add a lot of code. They aren’t necessarily something to avoid, but a site built with one starts slower than one with a simple theme.

Why the website is slower on mobile

Mobile results are almost always worse than desktop ones. Phones have weaker processors, and mobile networks add more delay to every request. A site that downloads 60 small files feels that more than one with 15 larger files.

What to check specifically for mobile:

  • Fonts. Every font family, in every weight (regular, bold, italic), is a separate file. Three families with four weights each means twelve downloads. Keep one or two families and only the weights you use.
  • Render-blocking scripts. Some scripts have to be downloaded and run before the browser can draw the page. PageSpeed Insights lists them under “Eliminate render-blocking resources”. Many can be loaded later with defer.
  • Pop-ups covering the content. The cookie banner, the newsletter sign-up box and a chat window that opens by itself take over a small screen and add scripts. One is acceptable; three at once make the site hard to use.
  • Images served at desktop size. The theme should send phones a smaller version of each image. WordPress automatically generates several sizes on upload, but some themes and page builders ignore them.

Test on a real phone, not just the simulator in the browser. A mid-range phone a few years old shows best what your customers experience.

Caching: build the page once, serve it many times

A WordPress site builds each page on every visit: it reads the database, runs the theme and plugins, then sends the result. A cache saves the finished page and serves it straight to the next visitor.

The kinds of cache that matter:

  • Page cache. Saves the final HTML. For brochure sites, where content changes rarely, it has the biggest effect on response time.
  • Browser cache. Tells the browser to keep images, styles and scripts for a few days, so the second page a visitor opens loads much faster.
  • OPcache for PHP. Keeps already-compiled PHP code in memory. It’s switched on at server level, usually by the hosting provider.
  • Object cache (Redis, Memcached). Helps sites with lots of database queries, such as online shops. A brochure site rarely needs it.

Be careful with online shops and pages with customer accounts. The basket and account pages must not go into the page cache. Reputable caching plugins know this, but check after enabling one that a customer can’t see someone else’s basket.

The server and your hosting

If the server’s first response stays slow after you’ve added page caching, the problem is probably the hosting or the application. Check:

  • The PHP version. Newer versions run the same code faster. WordPress recommends PHP 8.3 or newer. You change it from the hosting control panel, after a backup and a test.
  • Your plan’s resources. On shared hosting, each site has limits on processor, memory and simultaneous processes. A busy shop can hit those limits, and the site slows down exactly when it has the most customers. The control panel usually shows whether you’ve hit the limits.
  • Storage. Servers with SSDs answer database reads much faster than ones with traditional hard drives.
  • Server location. For visitors in Romania, a server in Romania or nearby means a shorter trip for every request.
  • A bloated database. Unlimited post revisions, spam comments kept around, data left behind by uninstalled plugins. A clean-up, after a backup, shortens queries.

The right shared hosting is enough for most business websites. If you’ve optimised the page and still hit the limits, the next step is a bigger plan or a server dedicated to the site. The differences between the options are explained in our answer on the three types of web hosting.

When the site slows down suddenly

If the site was fine and became slow overnight, look for what changed:

  1. A recent update to a plugin or theme. Disable it on a test copy and compare.
  2. A wave of automated traffic. Bots trying passwords on the login page, or downloading the whole site, can load the server. The access logs in the hosting panel show which addresses make the most requests.
  3. Foreign code. A hacked site can run scripts that send spam or mine cryptocurrency. Check recently modified files.
  4. A full disk. A hosting account with no free space can behave strangely: the cache can’t be written and sessions aren’t saved.
  5. A problem at the provider. Ask directly whether there’s a known issue on the server.

Frequently asked questions

How fast should a website load?

As a benchmark, the largest visible element on the page should appear within 2.5 seconds on a phone for most visitors. A well-built brochure site can come in well under that. Measure on mobile, because that’s usually where results are weakest.

Does website speed affect search rankings?

It does, as part of page experience, but relevant content still matters more. The most visible effect of a slow site is on visitors directly: they leave before the page loads, or give up on a form that responds slowly.

Will an optimisation plugin fix everything?

No. A caching and optimisation plugin helps a lot on the page side, but it won’t shrink an image uploaded the wrong way and can’t make up for an overloaded server. Install one, not several that do the same thing, because they can conflict with each other.

Why is the site fast for me and slow for customers?

Your browser already has the images and scripts stored from earlier visits. New visitors download all of them. Test in a private window or with PageSpeed Insights to see what a new visitor sees.

Will changing hosts make my website faster?

Only if the server was the problem. If the server’s response time is good and the page is heavy, the site will be just as slow on any hosting. Do the measurements above first. If you do decide to switch, our guide to moving a website to a new host shows the steps without downtime.

When to call a technician

You can sort out images and extra plugins yourself. Get help when the server responds slowly even with caching on, when the site slowed down suddenly with no obvious cause, or when the PHP version needs changing on an older site, where one incompatible plugin can take everything down.

TECH Consult web hosting runs on Dell servers with SSD storage in the INES data centre in Bucharest, with Plesk and WordPress Toolkit. If you’re not sure which plan suits your site, read our guide to choosing business web hosting.

Tell us what is not working

Describe the problem in a few lines. We reply with what we think needs doing and what it would cost.

Request a quote