A slow website is rarely caused by one mysterious technical problem. It is almost always a combination of issues stacking on top of each other: oversized images, weak hosting, too many plugins, heavy page builders, third party scripts and no real mobile first thinking. The good news is that most of these problems are diagnosable with free tools and fixable without rebuilding the entire site.
This guide walks through the most common speed killers in order of impact, the free tools you can use to find them, which fixes are quick wins and when a deeper rebuild makes more sense than patching. If you want the full picture of how speed fits into what your website needs to do, our web design pillar guide covers everything. This article focuses on diagnosis and triage.
The Straight Answer: Your Website Is Probably Slow Because of a Few Common Bottlenecks
Most slow websites are not slow because of some buried technical fault. They are slowed down by a combination of these:
Oversized images (the most common offender)
Cheap or overloaded hosting
Too many plugins or apps
Heavy page builders and bloated themes
Third party scripts (tracking, chat, widgets, social embeds)
Poor caching setup
Video, sliders and animation bloat
Poor mobile layout served to phone users
Too many font files or font weights
Redirect chains, broken resources and old website baggage
The goal is not to guess what is wrong. The goal is to test the page, find the bottleneck and fix the issues that will make the biggest difference first.
Why Website Speed Matters
Speed is not a vanity metric. It directly affects whether people stay, trust and act.
Slow sites create friction
A slow website can reduce enquiries, hurt sales, lower booking completions, waste paid ad spend, erode trust, weaken SEO performance and make the mobile experience frustrating. If the page feels sluggish, visitors may leave before they see the offer, the proof or the call to action. If you are running Google Ads and sending traffic to slow pages, you are paying for clicks that never convert. Our guide on why your Google Ads are not converting covers how landing page speed directly affects ad performance and cost per lead.
Google measures page experience
Google describes Core Web Vitals as metrics for real world user experience across loading performance, interactivity and visual stability. Speed is not the only ranking factor, but poor page experience can hold back pages that otherwise deserve to rank. For a plain English breakdown, see our guide to what Core Web Vitals actually mean. And if speed is affecting your organic visibility, our SEO guide for Melbourne businesses explains how page experience fits into the bigger ranking picture.
But speed is not just about pleasing Google
A faster website gives people a smoother path to understand, trust and enquire. That matters whether traffic comes from Google, ads, social or a referral. The commercial benefit is not a better test score. It is more people completing the action the page was built for.
Before You Fix Anything, Test the Website Properly
Do not start randomly changing things. Test first, diagnose, then fix in order of impact.
Test more than just the homepage
Check the homepage, one key service page, the contact page, one landing page if you run ads, one article page if content matters and one product page if ecommerce. Speed problems are often page specific.
Test mobile first
Small business owners usually review their website on a desktop monitor. But most of their customers are searching on a phone. If you only test desktop, you will miss the problems that matter most.
Use more than one tool
No single tool tells the full story. Use a combination:
PageSpeed Insights for mobile and desktop scores, Core Web Vitals and improvement suggestions
Google Search Console for the Core Web Vitals report based on real user data
GTmetrix for waterfall charts, large files and image/script issues
WebPageTest for deeper waterfall analysis and filmstrip loading views
Chrome DevTools Lighthouse for local testing and technical detail
A manual mobile test on your actual phone for real usability
What the Speed Metrics Actually Mean
You do not need to memorise these. But knowing what each one measures helps you understand what your test results are actually telling you.
LCP (Largest Contentful Paint): How quickly the main content loads. A good LCP is within 2.5 seconds.
INP (Interaction to Next Paint): How quickly the page responds when someone taps or clicks. A good INP is 200 milliseconds or less.
CLS (Cumulative Layout Shift): Whether the page jumps around while loading. A good CLS score is 0.1 or less.
TTFB (Time to First Byte): How quickly the server starts responding. This is where hosting and backend issues show up.
TIP: Do not obsess over a single score. A green number does not mean the site converts well and a yellow number does not always mean the site is broken. Focus on what is causing the delay, not just what the number says. |
Common Website Speed Killers Ranked by Impact
Issue | Impact | Difficulty | Common Signs | First Fix |
|---|---|---|---|---|
Oversized images | High | Low Med | PageSpeed flags image sizing/format. Slow LCP. | Compress and resize before uploading |
Weak hosting | High | Medium | High TTFB. Slow even on simple pages. Inconsistent speed. | Check server response. Consider upgrading. |
Too many plugins/apps | High | Medium | Got slower over time. Unused JS/CSS flagged. | Remove unused plugins. Replace heavy ones. |
Heavy page builder/theme | High | Med High | Simple pages still test badly. Excessive DOM size. | Simplify sections. Consider lighter framework. |
Third party scripts | Med High | Medium | Third party code flagged. Buttons feel delayed. | Audit GTM. Remove unused tags and pixels. |
Poor caching | High | Medium | Repeat visits still slow. High server response time. | Enable page and browser caching. |
Video/slider bloat | Med High | Low Med | Hero takes too long. LCP tied to media. | Replace video with static image. Remove sliders. |
Poor mobile layout | High | Medium | Desktop OK, mobile poor. Mobile users bouncing. | Simplify mobile hero. Compress mobile images. |
Font loading | Medium | Medium | Text appears late or shifts. CLS issues. | Reduce font weights. Preload key fonts. |
Redirects/broken resources | Medium | Medium | Redirect chains in crawl. Console errors. | Update internal links. Fix missing files. |
1. Oversized images
This is the single most common speed problem on small business websites. Uploading a 5MB photo straight from a camera as a hero image can add seconds to load time, especially on mobile. Common culprits include full resolution photos, no WebP or modern formats, no lazy loading and image dimensions far larger than the display size.
Quick wins: Compress images before uploading. Resize to the dimensions actually needed. Use WebP where possible. Lazy load images below the fold. Avoid image sliders with multiple large slides.
Bigger fixes: Image CDN, responsive image setup at template level or redesigning image heavy sections. For a full walkthrough, see our guide on how to speed up your website.
2. Cheap or overloaded hosting
If the server is slow to respond, everything else starts late. Common signs include high TTFB, a slow admin dashboard and speed that gets worse during busy periods. Cheap shared hosting with overloaded servers, old PHP versions or no Australian server option for Australian users can drag down an otherwise well built site.
Quick wins: Enable server side caching. Check your PHP version. Ask your host about resource limits.
Bigger fixes: Move to better hosting, managed WordPress, VPS or managed cloud. For a comparison of what is available, see our Australian web hosting comparison.
3. Too many plugins or apps
Each plugin can add scripts, styles, database queries or external requests. Multiple plugins doing the same job, old or poorly coded plugins, unused plugins still active and heavy form, slider or popup add ons all stack up. If the site has gotten slower over time and plugin updates keep breaking things, this is likely a factor.
Quick wins: Remove unused plugins. Replace heavy plugins with lighter alternatives. Disable plugin assets on pages where they are not needed.
Bigger fixes: Developer plugin audit, rebuilding heavy features natively or replacing the bloated theme and plugin stack entirely.
4. Heavy page builders and bloated themes
Some websites are built with too many nested sections, animation libraries, style layers and builder specific scripts loading on every page. Simple looking pages can still test badly because the underlying code is heavy. PageSpeed will often flag excessive DOM size or unused CSS and JavaScript.
Quick wins: Remove unnecessary sections. Simplify animations. Clean up unused templates. Disable unused builder features where possible.
Bigger fixes: Rebuild key templates with a lighter framework, move to cleaner components or custom development for high value pages. Our comparison of Elementor vs Divi vs Bricks vs Gutenberg covers how these builders compare on performance and flexibility.
5. Too many third party scripts
Tracking pixels, chat widgets, heatmaps, social embeds, booking widgets, review widgets and maps all add load. If PageSpeed flags third party code, buttons feel delayed on mobile or performance is weak despite a clean design, third party scripts are likely the issue.
Quick wins: Remove unused tracking tags. Audit Google Tag Manager. Load scripts only on pages where they are needed. Replace heavy embeds with click to load versions.
Bigger fixes: Consent aware tag strategy, server side tagging or rebuilding integrations with lighter alternatives.
6. Poor caching setup
Caching helps the website avoid rebuilding the same page from scratch every time someone visits. If there is no page caching, the cache plugin is misconfigured or caching has been disabled because of plugin conflicts, every visitor triggers a full page rebuild on the server.
Quick wins: Enable page caching and browser caching. Use host level caching if available. Clear and retest after updates.
Bigger fixes: Object caching, CDN setup, developer managed caching rules or WooCommerce specific caching strategies.
7. Video, sliders and animation bloat
Hero videos, autoplay backgrounds, image sliders and animation libraries can make a page feel impressive but load slowly. If the hero section takes too long to appear and LCP is tied to hero media, this is likely the issue.
Quick wins: Replace hero video with a static image. Remove sliders. Compress media. Disable background video on mobile.
Bigger fixes: Redesign the hero and above the fold layout. Create a mobile specific media strategy.
8. Poor mobile layout
A desktop first design can create heavy, awkward mobile pages. Desktop images served to mobile, stacked sections that are too long, hidden desktop elements that still load, popups blocking the page and tiny buttons all contribute. If the desktop score is okay but the mobile score is poor, this is the area to investigate.
Quick wins: Simplify the mobile hero. Remove mobile popups. Use shorter sections. Compress mobile images. Make buttons easier to tap.
Bigger fixes: Mobile first redesign, template rebuild, responsive image setup or form redesign.
9. Poor font loading
Too many font families, too many font weights, external font requests and no font display strategy can delay text rendering or cause layout shifts. If text appears late or flashes, this is likely a factor.
Quick wins: Reduce font weights. Use system fonts where appropriate. Host fonts locally. Preload key fonts.
10. Redirects, broken resources and old website baggage
Redirect chains, old HTTP to HTTPS issues, broken CSS or JavaScript files, missing images and leftover staging assets all add unnecessary delays.
Quick wins: Update internal links to final URLs. Remove broken resources. Fix missing files. Clean old tracking tags.
Bigger fixes: Full crawl and redirect audit. Migration cleanup. Rebuild templates with clean asset paths.
Quick Wins vs Bigger Website Speed Fixes
Fix | Type | Difficulty | Who Can Do It | Notes |
|---|---|---|---|---|
Compress images | Quick win | Low | Business owner | Biggest bang for least effort on most sites |
Remove unused plugins | Quick win | Low | Business owner | Deactivate and delete, not just deactivate |
Enable caching | Quick win | Low Med | Owner or developer | Check host level caching first |
Audit scripts and tags | Quick win | Medium | Owner or developer | Remove old pixels and unused GTM tags |
Move hosting | Bigger fix | Medium | Developer | Test on new host before switching DNS |
Rebuild templates | Bigger fix | Med High | Developer | Focus on high traffic pages first |
Optimise JS/CSS delivery | Bigger fix | High | Developer | Defer, combine, remove unused code |
Mobile first redesign | Bigger fix | High | Agency/developer | Needed when mobile layout is structurally poor |
How to decide where to start
Start with the issue that is highest impact, visible on your most important pages, affecting mobile users, affecting enquiries or sales and easiest to fix without breaking the site. If you are not sure which page matters most, run our DIY website audit checklist to score your key pages and identify where to focus.
Free Tools to Find What Is Slowing Your Website Down
Tool | Best For | What to Look At | Limitation |
|---|---|---|---|
PageSpeed Insights | Mobile/desktop scores, Core Web Vitals, suggestions | LCP, INP, CLS, TTFB, field data vs lab data | Lab data may differ from real user experience |
Search Console CWV | Real user data, page groups, mobile vs desktop | URL groups by status. Failing vs passing metrics. | Needs enough traffic for field data to appear |
GTmetrix | Waterfall charts, large files, image/script issues | Largest files, slowest requests, total page weight | Free version limited to one test location |
WebPageTest | Deeper waterfall analysis, repeat views, filmstrip | First view vs repeat view. Filmstrip timeline. | More technical. Can be overwhelming for beginners. |
Chrome Lighthouse | Local testing, technical hints, developer detail | Performance, accessibility, SEO, best practices | Lab only. No real user data. |
Manual phone test | Real usability, tap to call, form, first impression | How the page actually feels on your phone | Subjective. No metrics. But catches real UX issues. |
Slow Website Diagnosis: What the Symptoms Usually Mean
If you have run your tests and are not sure what the results mean, this table maps common symptoms to likely causes.
Symptom | Likely Cause | What to Check First |
|---|---|---|
Mobile score much worse than desktop | Heavy mobile layout, large images, scripts | Mobile PageSpeed + manual phone test |
Main content appears late | LCP issue: hero image, slow server response | PageSpeed LCP element identifier |
Site responds slowly to taps | JavaScript bloat, third party scripts, heavy builder | INP diagnostics, JS coverage audit |
Page jumps around while loading | Missing image dimensions, fonts, banners, embeds | CLS diagnostics in PageSpeed |
Site is slow before anything appears | Hosting, caching, TTFB | Server response time in PageSpeed/GTmetrix |
Homepage OK but service pages slow | Template or content specific bloat | Test multiple page types separately |
Admin dashboard is slow too | Hosting, database or plugin issue | Backend plugin audit, host resource check |
Speed changes wildly between tests | Hosting or caching instability | Repeat tests at different times + host review |
What Not to Do When Your Website Is Slow
Do not install five speed plugins at once. They can conflict with each other and make diagnosis harder, not easier.
Do not chase a perfect score blindly. A perfect PageSpeed score is not the goal. A fast, usable, conversion ready website is.
Do not blame hosting before testing. Hosting may be the issue, but prove it with TTFB data first.
Do not compress images and ignore everything else. Images are common, but they are not the only factor.
Do not run tests only on desktop. Mobile is where the real problem usually appears for small business websites.
Do not remove tracking blindly. Some scripts matter for measuring conversions. Audit before deleting. If you are spending on Google Ads, the cost of running those campaigns is wasted if you remove the conversion tracking that proves they work.
When a Slow Website Needs a Rebuild, Not Another Plugin
Signs patching may not be enough
Old bloated theme that cannot be easily cleaned up
Too many page builder dependencies baked into every page
Slow on every page, not just one or two
Poor mobile structure that cannot be fixed with CSS tweaks
Repeated plugin conflicts that break functionality after every update
Outdated CMS version or unsupported PHP version
Speed fixes keep breaking the design
Performance problems return after every round of patching
Signs patching is enough
Images are the main issue (easy to fix without a rebuild)
Hosting is the main bottleneck (upgrade the host, not the site)
One or two heavy scripts are the problem (remove or replace them)
A few specific templates are heavy (rebuild just those templates)
Caching is missing or misconfigured (enable and test)
A rebuild is not always necessary. But if the foundation is bloated, every speed fix becomes a workaround. Factor the ongoing cost of patching into your
decision. Our guide to ongoing website upkeep covers what maintenance actually costs after launch.
What We Recommend at Elev8d
Most slow websites do not have one villain. It is usually a heavy theme, plus large images, plus cheap hosting, plus too many plugins, plus tracking scripts, plus no real mobile first thinking. They stack.
The smartest approach is to diagnose before fixing, improve the highest impact pages first and avoid turning the site into a pile of speed plugins and temporary patches. If the site's foundation is solid but a few things are dragging it down, targeted fixes work well. If the foundation itself is the problem, a clean rebuild of the key pages is usually more cost effective than years of patching.
And remember: speed should support conversion, not replace it. A fast site with vague copy and no proof will still underperform. If your site is fast but not generating enquiries, the problem may be deeper. Our guide on why your website gets traffic but no enquiries covers the conversion side.
FAQs
Why is my website so slow?
Most likely a combination of oversized images, weak hosting, too many plugins, heavy page builder code and third party scripts. Test with PageSpeed Insights to identify which issues are affecting your specific pages.
What is the most common cause of a slow website?
Oversized images are the single most common cause. They are also the easiest to fix. After that, hosting quality, plugin bloat and heavy themes are the next most frequent culprits.
How do I test why my website is slow?
Start with PageSpeed Insights on mobile. Test the homepage and one key service page. Look at LCP, TTFB and the improvement suggestions. Then check Google Search Console for the Core Web Vitals report. Use GTmetrix for waterfall analysis if you need more detail.
Can cheap hosting make my website slow?
Yes. If the server response time (TTFB) is slow, everything else starts late. Cheap shared hosting with overloaded servers, no Australian server option or old PHP versions can all contribute.
Do plugins slow down WordPress websites?
They can. Each plugin can add scripts, styles and database queries. Multiple plugins doing the same job, poorly coded plugins and unused plugins that are still active all stack up over time.
Why is my website slow on mobile but fine on desktop?
Usually because the mobile version is loading the same heavy images, scripts and layout as the desktop version. A desktop first design often creates mobile pages that are heavier than they need to be.
What is a good PageSpeed score?
Above 90 is strong. Above 70 is decent. Below 50 on mobile needs attention. But the score is a guide, not a verdict. Focus on the specific issues flagged, not just the number at the top.
Should I use a speed optimisation plugin?
One well configured caching and optimisation plugin can help. Five speed plugins installed at once will usually make things worse. Pick one, configure it properly and test.
When should I rebuild a slow website instead of fixing it?
When the theme is fundamentally bloated, every page is slow, plugin conflicts are constant, mobile structure is poor and every speed fix breaks the design or reverts after the next update. If patching keeps costing time and money without lasting results, a clean rebuild of the key pages is usually the smarter investment.
Next Steps: Pick Your Path
Found the bottleneck? Start with the highest impact fix from the ranked list above. Images and caching are usually the quickest wins.
Not sure what is causing it? Run PageSpeed Insights on mobile for your homepage and top service page. The suggestions will point you in the right direction.
Need a deeper review? Talk to Elev8d about identifying the real speed bottleneck before you waste time patching the wrong problem. We can help you figure out whether the fix is quick, structural or a rebuild conversation.
Speed is fine but enquiries are low? The problem may not be speed. Our full web design guide for Melbourne businesses covers everything from page structure and copy to trust signals and conversion paths.
Planning a redesign? Our business website design in Melbourne is built on speed, clarity and conversion from day one. No bloat. No guesswork.
Sources and Further Reading
Google PageSpeed Insights - Mobile and desktop performance testing with Core Web Vitals
web.dev Core Web Vitals - Google's documentation on LCP, INP and CLS metrics
Google Search Console - Real user Core Web Vitals report and indexing data
GTmetrix - Waterfall analysis and page weight diagnostics
Australian Cyber Security Centre - Security basics including software updates and access controls
Australian Government Digital Service Standard - Guidance on building performant, user centred digital services
General information only. Rules vary by situation, particularly around advertising claims, privacy, reviews and consumer law. If you are unsure about compliance, get professional advice.
