Webdevelopment

12 min read

Why is my website slow?

Your website loads slowly? Causes, a speed test for mobile and desktop, and what actually helps, without the technical chaos.

Why is my website slow?

Short answer: A website is usually slow because the images are too large, too many scripts and trackers load, the hosting is weak, or the site has been bloated over the years with plugins and building blocks. Measure first with the Website Speed Test on OpenGraph Check, which shows mobile and desktop at a glance. Then fix the three biggest bottlenecks and decide whether optimizing is enough or a relaunch is cheaper.

Your website feels sluggish. On a phone it takes forever for text and images to show up. That's not a minor issue. Slow sites lose visitors, inquiries and Google rankings.

"Why is my website slow?" is something I hear regularly in first calls. Often a caching plugin has already been installed or images have been "compressed". The site still feels janky. Usually it's not one single setting, but several bottlenecks at the same time.

Why load time matters for your business

Google uses Core Web Vitals and Page Experience as ranking signals. If you're slow on mobile, you'll have a harder time. And for most company websites, mobile is the main channel.

In practice, that means:

  • Bounce rate: From around three seconds of load time, drop-offs increase noticeably.
  • Inquiries and sales: Every extra second costs conversions.
  • Trust: A stuttering site looks unprofessional, no matter how good your offer is.

Speed isn't an extra for tech nerds. It's part of how you present yourself. If you're already thinking about a new or redesigned site, it's worth looking at how much a website costs and how performance should be planned in from the start.

The most common causes

Images that are too large

The classic: a 3 or 4 MB hero image, uploaded straight from the camera. 4000 pixels wide, saved as a JPEG. The browser has to download and render that. On LTE or weak Wi-Fi, that takes a while.

I see this a lot with relaunches: beautiful photos, but nobody prepared them for the web. A header image should rarely be more than 150 to 200 KB. Formats like WebP or AVIF save even more space. If your files are bigger than that, you can shrink them for free in the browser, for example with toolit Image Compress. No account needed, and nothing is uploaded to someone else's server.

Don't forget the OG image for social shares either. Many sites load small images on the page but set a 2 MB PNG as the og:image in their meta tags. That doesn't necessarily slow down your homepage, but it shows that images aren't being managed properly. You can check whether title, description and OG image are right with a scan on OpenGraph Check.

Too many scripts and trackers

Cookie banner, Google Analytics, Meta Pixel, Hotjar, chat widget, A/B testing tools, embedded social feeds. Every tool loads its own JavaScript files. Some block rendering until they're done.

Ask yourself for every script: do I really need this data? If yes, load it deferred or only after a user interaction. Cutting back here is often a bigger lever than any speed plugin.

Heavy WordPress setup

WordPress can be fast. In practice it often isn't: 25 plugins, a page builder, no caching, a theme from 2019, hosting for a few euros a month.

A plugin audit helps: temporarily deactivate everything that isn't strictly necessary. Every plugin has to justify its existence. As requirements grow, a modern stack is sometimes worth more than more patchwork. I'll come back to that below.

No caching and no CDN

Without caching, the server rebuilds everything on every request. Without a CDN, images always come from the same location, even if your visitor is on the other side of the country.

Browser caching, server caching and a CDN for static files are standard in professional setups. With web development in Next.js, a lot of this is built in, because pages and assets are delivered in a targeted way.

Fonts and CSS block the first render

Four or five font weights from Google Fonts or Adobe, all loaded right away. The page stays white until everything has arrived.

Fewer weights, font-display: swap, self-hosted fonts. Critical CSS first, the rest loaded later. Sounds technical, but it often gives you a visible jump in load time.

Too many effects and pages that are too big

Parallax, scroll animations on every block, a full HD video background, hundreds of DOM elements. Looks great on the designer's MacBook. Not on an older Android phone.

Use animations only where they actually help users. CSS instead of heavy JavaScript. Fewer elements per page.

Weak hosting

Shared hosting with hundreds of other sites on one server, a slow database, no HTTP/2, no edge network. No plugin fixes that for good.

If the server response time (TTFB) is regularly above 600 ms, that's often where the problem is. In that case, no image optimizer in the world helps as much as better hosting.

How to find out where it's stuck

Before you blindly install plugins: measure. Don't guess.

Website speed test: mobile and desktop at a glance

My first step in audits: enter the URL, look at the result. With the Website Speed Test on OpenGraph Check you immediately see how fast your site loads on a phone and on a desktop. Both are shown side by side, so you don't have to test twice and compare numbers.

Many sites score worse on mobile in particular. What feels snappy on a laptop can be janky on a phone. That's exactly why it's worth looking at both numbers.

Among other things, you'll see:

  • a speed score for mobile and desktop (0 to 100)
  • how long it takes until the main content is visible
  • whether the page jumps or stutters while loading
  • hints on what to improve next

As a rule of thumb: above 90 is good. Below 50, you should act. In between, targeted optimization pays off. Often images, fewer scripts and better caching are enough.

ToolWhat it shows
OpenGraph Check Speed TestHow fast your site loads on mobile and desktop
OpenGraph Check ScanOG preview, meta tags, OG image, domain rating, sitemap, canonical
PageSpeed InsightsSpeed and optimization tips from Google
WebPageTestWaterfall, load times worldwide
GTmetrixOverview with history

Test the site the way visitors see it: with the cookie banner, tracking and all plugins. An empty staging environment fakes good numbers.

Performance is only half the story. After the speed test, it's worth checking the technical basics with the OpenGraph Scan: Are title and description for social media missing? Is the preview image too large? Are the most important meta tags right? Together, the two give you a clear picture in a few minutes.

In the speed test, pay particular attention to:

  • Mobile score: Often the more important number, because most visitors come from a phone.
  • Desktop score: Shows whether the site feels noticeably faster on a laptop.
  • Concrete hints: What the tool suggests as the next improvement.

Step by step: what you can do now

This is the order I usually recommend in audits. Not everything at once. Measure first, then tackle the biggest bottlenecks, then measure again.

Step 1: Record your baseline

Check your homepage and one important subpage in the Website Speed Test. Write down the mobile and desktop scores and save screenshots. That way you'll see later whether a change actually helped.

If mobile scores much worse than desktop, the problem is almost always images, JavaScript or a heavy mobile layout. A laptop test alone won't show you that.

Step 2: Fix your images

Check every image over 200 KB. Export to WebP or AVIF and match the resolution to the display size. For a quick first pass, toolit Image Compress works well: compress JPG, PNG and WebP right in the browser. Also check the OG image in your meta tags, because that's often still an uncompressed original. OpenGraph Check shows you the preview and missing tags in one go. Turn on lazy loading for everything below the fold. This is often the fastest win.

Step 3: Clean out scripts and plugins

List everything that's loaded from external sources. Cookie tools, analytics, chat, maps, embeds. What can go, or load later? On WordPress: go through it plugin by plugin. Many sites carry 10 to 15 plugins nobody needs anymore.

Step 4: Check caching and CDN

Is browser caching active? Is there a server cache? Are images and CSS served via a CDN? If not, that's the next sensible step after the images.

Step 5: Check hosting and TTFB

How fast does the server respond before any content arrives? Consistently high TTFB points to hosting or server configuration, not to a missing WordPress plugin.

Step 6: Prioritize instead of doing everything at once

Take the three biggest opportunities from the report. Implement them. Measure again. Many projects improve significantly without a relaunch.

Quick wins vs. bigger rebuilds

Not every measure takes the same effort.

Often done in a few hours:

  • Compress images and switch formats
  • Deactivate unnecessary plugins
  • Enable browser caching
  • Lazy loading for images and iframes
  • Reduce the number of fonts

Several days:

  • Set up a CDN properly
  • Reorganize third-party scripts
  • Tune the database and server for WordPress
  • Optimize critical CSS and load order

Weeks, but a big lever:

  • Relaunch on a modern stack
  • Less client-side rendering, more static or edge delivery
  • A new design with a fixed performance budget from day one

The question isn't "optimize or rebuild?" but: what will cost you less over the next two years?

Typical optimization mistakes

Only chasing the speed score. Green on the homepage doesn't help much if checkout, blog or forms are still slow. Test all important pages.

Installing a caching plugin and calling it done. Caching hides symptoms. If every image weighs 4 MB, you're just serving large files from the cache faster.

Ignoring mobile. Google primarily indexes the mobile version. Desktop numbers alone aren't enough.

Stacking too many speed plugins. Every "booster" plugin can create new conflicts. Better to fix three causes deliberately than to install ten tools.

No measurement before and after. Without a baseline, you don't know whether something was worth it.

When a relaunch makes more sense than patching

Sometimes the foundation has simply hit its limits:

  • A page builder plus 30 or 40 plugins on an old theme
  • Every page loads 2 MB of JavaScript for a classic company website
  • Mobile stays red even though it has already been "optimized"
  • New features like multiple languages or a customer portal would make it even heavier

Then starting fresh is often cheaper than endless retrofitting. Not because a relaunch is better per se. But because the architecture can't grow with you anymore.

In a relaunch, plan performance from day one: image sizes, fonts, script budget, Core Web Vitals as an acceptance criterion. If you set up web development properly, you save yourself expensive firefighting later.

For projects with a clearly defined scope, targeted performance audits are often in the low four figures. A relaunch with a performance focus depends on the scope, similar to a new business website.

FAQ

How fast should a website load?

As a rule of thumb, under three seconds until the page is usable on mobile. Under two is better. Core Web Vitals in the green are the concrete goal.

What is a good performance score?

Above 90 is considered good. Below 50, you should take action. In between, targeted optimization pays off. More important than a perfect number: look at mobile and desktop separately and tackle the biggest weaknesses first.

Why do mobile and desktop scores differ?

On mobile, a slower network and weaker hardware are simulated. That's why the mobile score is often lower, and for most websites it's the more relevant one.

Can I fix this myself?

Small things, yes: shrink images, cut down on plugins, enable caching. Deeper problems like render-blocking JavaScript, poor architecture or the server setup usually need someone with web performance experience.

Does a CDN always help?

A CDN speeds up the delivery of static files worldwide. It doesn't replace bad hosting, 5 MB images or bloated JavaScript. Useful, but not a miracle cure.

Why is my WordPress site suddenly slow?

Common triggers: a new plugin, a plugin update, large images in the blog, more traffic on weak hosting, an outdated PHP version. Start with a plugin audit and a hosting check.

Does slowness really affect SEO?

Yes. Core Web Vitals are a ranking factor. Indirectly, the bounce rate counts too, when users leave right away.

How much does performance optimization cost?

An audit with quick wins is often in the low four figures. A relaunch with a performance focus depends on the scope. In a first call, we can figure out whether optimization is enough or a fresh start makes more sense.

Do I have to rebuild everything at once?

No. Often images, fewer scripts and better caching are enough for a noticeable jump. Measure first, then tackle the three biggest bottlenecks.

Conclusion

Slow websites rarely have a single cause. Usually it's images, trackers, weak hosting and a structure that has grown over the years.

Measure first. Prioritize the three biggest levers. Then decide whether fine-tuning is enough or the foundation needs rethinking.

If you're not sure where your site is losing time, a quick check is often enough before you invest in plugins or an expensive relaunch.

Tom Schindler

Software Engineer

Cookies

Cookies on this website

I use essential cookies for language, basic functionality, and privacy-friendly usage analytics. More in the Privacy Policy.