People who search "why is my website slow" are usually hoping for one big fix. There normally isn't one, but there are a handful of ordinary causes, and most of them take an afternoon to sort out.
What slow looks like from the customer's side
Picture someone who finds you on Google Maps while sitting in a car park in Al Quoz. One bar of 4G and maybe six seconds of patience.
They tap your website link. The screen stays white while a 5 MB banner image downloads, then a cookie bar and a chat bubble load on top of it. They go back and tap the next result.
You never hear about it. That's what makes a slow site expensive: it doesn't send complaints, it quietly loses enquiries.
And it's rarely one thing. On the slow small-business sites we're asked to look at, the cause is usually a mix of four or five ordinary problems, each adding a second or two. The biggest ones tend to be the easiest to fix, which is good news if you're paying for the work.
Images straight off a phone or a camera
This is the most common cause by a distance. A photo from a modern phone is often 3 to 6 MB. Upload ten of them to a gallery page, add a homepage slider with five more, and the page can weigh 50 MB before a visitor has read a word.
Nobody needs that. A full-width banner looks sharp at around 1,600 to 2,000 pixels wide, and once it's compressed and saved as WebP it usually comes in under 300 KB. Product thumbnails and team photos can be far smaller.
Two checks are worth doing. First, look at the file size of the biggest images on your homepage (on a laptop, open one in a new tab and save it to see the size). Second, check whether images further down the page only load as the visitor scrolls. That's called lazy loading, and it should be switched on for everything except the top image.
Sliders deserve a mention of their own. Five rotating banners mean five large images loaded for a visitor who sees one.
Hosting that costs less than a coffee a month
Cheap shared hosting can put hundreds of sites on one server. When a neighbour gets busy, your site slows down, and you've no way of seeing it happen.
The sign is a long wait before anything appears at all. If the page sits blank for two or three seconds and then everything arrives quickly, the server is the likely problem rather than the page. PageSpeed Insights flags this as a slow server response.
Location plays a part too. A site for customers in Dubai hosted on a budget server on another continent adds a delay to every request. A content delivery network (CDN) helps by serving files from somewhere closer to the visitor.
Here's the caveat a hosting company won't give you. Paying for better hosting won't rescue a homepage made of 15 MB of images and 40 scripts. Fix the page weight first, then judge the hosting.
Plugins, trackers and the chat bubble nobody opens
Every plugin and tracking code adds files the phone has to download and run. Individually they're small. Together they add up fast.
It's common to find a slow WordPress site running 30 or more plugins, several doing the same job. Then there's the leftover stuff from campaigns that ended long ago: an old Facebook pixel, two analytics tags, a heatmap tool someone tried for a week, a review widget nobody updates.
Chat widgets are a particular drag. Many load a large script on every page, even for visitors who'll never open them. If your customers message you on WhatsApp anyway, a plain WhatsApp button does the same job for almost no weight. Our guide to adding WhatsApp to your website covers the setup.
So go through the list with whoever manages the site. For each script, ask who uses the data and when they last looked at it. If nobody can answer, it goes.
Caching and fonts, the quieter problems
Without caching, the server builds each page from scratch for every visitor. With it, a ready-made copy is sent instead, which is much quicker. Most hosting supports caching, but it's often switched off, or set up badly by two plugins fighting each other.
Browser caching is the other half. It tells a returning visitor's phone to keep your logo and stylesheet instead of downloading them again.
Fonts are easy to overlook. A site loading three font families in six weights each asks the phone for 18 files before the text looks right, and on a slow connection the words can stay invisible until those files arrive. One or two families, with only the weights you use, is plenty.
What to fix first
Most "speed up my website" requests we get come down to the same order of work:
- Resize and compress the largest images, starting with the homepage banner
- Remove old tracking codes and plugins nobody can explain
- Swap a heavy chat widget for a plain WhatsApp button
- Switch on page caching and browser caching, using one tool, not several
- Cut fonts down to one or two families
- Only then look at better hosting
Test it the way your customers see it
Measure before you change anything, then again after each fix, so you know what made the difference. Start with Google's PageSpeed Insights, or run our free website checker, which uses Google's PageSpeed data and explains the results in plain English. Look at the mobile score. Desktop scores flatter almost every site.
If your site gets enough visitors, PageSpeed also shows real-user data collected from Chrome over the past 28 days. That counts for more than the lab score, because it reflects real phones on real networks. Google treats the main content appearing within about 2.5 seconds as good.
Then do the test that matters most. Take your own phone, switch off Wi-Fi and open the site on mobile data in a private tab, so nothing is cached. Count the seconds until you could read the first heading and tap a button. Try it somewhere other than the office.
Don't chase a perfect 100. A mobile score in the 70s or 80s on a page that feels quick in your hand is fine for most small businesses. Some things that cost points, like an embedded map or an analytics tag you actually use, are worth keeping.
Sometimes the site is built on a heavy theme and page builder, and patching it costs more than starting again. If that's where you are, our website redesign service rebuilds it mobile-first with the speed basics done from day one.
Send your web address on WhatsApp to +971 52 292 3875 and we'll tell you what's slowing it down.
Questions people ask
How fast should my website load on a phone?
Aim for the main content to appear in under about 2.5 seconds on mobile data. If you can read the headline and tap a button within three seconds on your own phone, you're in decent shape.
Will a faster website rank higher on Google?
Speed is one of many signals Google uses, so it can help, but it won't lift a site on its own. The clearer gain is that fewer visitors give up before the page loads.
Is my hosting the reason the site is slow?
Sometimes. If the page stays blank for a few seconds before anything appears, suspect the server. If it starts quickly but drags on, look at images and scripts first.
Why does my PageSpeed score change every time I test?
The lab test simulates a phone and a network, and small differences in server response shift the result. Run it a few times and go by the typical score, not the highest.
Can you speed up a site you didn't build?
Usually, depending on how it was built and whether we can get access. For some heavy older sites a rebuild works out cheaper than repairs, and we'll say so if that's the case.