Quick answer
Most slow websites are caused by large images, too many plugins or third-party scripts, heavy themes, and slow or overloaded hosting. Test your pages with Google PageSpeed Insights, look at the Core Web Vitals (LCP, INP and CLS), then fix the biggest problems first, usually images, scripts and hosting.
Key takeaways
- Test with PageSpeed Insights before changing anything.
- Core Web Vitals are LCP (loading), INP (responsiveness) and CLS (visual stability).
- Oversized images and extra scripts are the usual culprits.
- Fix the biggest issue first, then test again.
Why does website speed matter?
A slow site frustrates visitors. People on phones, often on mobile data, are the least patient of all. If your page takes too long to show anything useful, many will tap back and choose the next business in the results.
Speed also matters to Google. Page experience, which includes Core Web Vitals, is one of the signals Google uses. It will not rescue a weak page, but a fast, stable page is better for both people and search.
If you run ads, speed matters even more. You pay for every click. A slow landing page means you pay for visitors who leave before they ever see your offer.
How to test your website speed with PageSpeed Insights
PageSpeed Insights is a free tool from Google. It is the best place to start because it shows both real-world data and a lab test.
- Open PageSpeed Insights and paste in the full address of a page. Start with your home page, then test your most important service or product page.
- Check the Mobile tab first. Most local searches happen on phones, and mobile results are usually the weaker ones.
- Look at the top section. If it shows real-user data, labeled as what your real users are experiencing, that is field data from Chrome users. It reflects actual visits over recent weeks.
- Scroll to the diagnostics. The Opportunities and Diagnostics lists show what is slowing the page down, such as large images or render-blocking scripts.
- Write down your results. Note LCP, INP, CLS and the performance score for each page, with the date.
- Test again after each fix so you know what actually made a difference.
Lab scores can vary from one test to the next. Run the test two or three times and look at the general picture rather than a single number.
What are Core Web Vitals?
Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors. Google publishes a "good" threshold for each one.
| Metric | What it measures | Google's "good" threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How long the main content, often a big image or heading, takes to appear | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps around while loading | 0.1 or less |
Google assesses these at the 75th percentile of real visits, so most of your visitors should get a good experience, not just the ones on fast connections. Your Search Console account also has a Core Web Vitals report that groups your pages by status.
Are images slowing down your website?
Images are the most common cause of a slow LCP. A photo straight from a phone or camera can be many times larger than it needs to be on a web page.
- Resize images to the largest size they are actually shown on screen.
- Compress them and use modern formats such as WebP or AVIF where your platform supports them.
- Lazy-load images below the fold, so they only load when someone scrolls toward them.
- Do not lazy-load the main hero image. It should load right away, because it is often the LCP element.
- Set width and height on images so the browser reserves space and the layout does not jump. This helps CLS.
Background videos and large sliders deserve a hard look too. They often add a lot of weight for little benefit.
Is your hosting the problem?
If even a simple page is slow to start loading, the problem may be your server. PageSpeed Insights flags this as a slow server response time, sometimes shown as Time to First Byte.
Cheap shared hosting puts many websites on one server. When neighbors get busy, your site slows down. Hosting far from your customers can also add delay.
Caching matters a lot for platforms like WordPress. Without it, the server builds each page from scratch for every visitor. With page caching, it can send a ready-made copy instead, which is much less work.
Things that usually help are page caching, a content delivery network (CDN) that serves files from locations closer to your visitors, an up-to-date version of PHP if you use WordPress, and a hosting plan that matches your traffic. Before switching hosts, test at a few different times of day to see whether the slowness is constant or comes and goes.
Do plugins, themes and scripts make a website slow?
Often, yes. Every plugin, tracking tag, chat widget, pop-up tool and embedded map can add code that the browser must download and run. Each one may seem small. Together, they add up, and heavy JavaScript is a common cause of poor INP.
Go through your list of plugins and third-party scripts and ask of each one: are we still using this, and is it worth what it costs in speed? Remove anything you do not need. Replace heavy page builders or multipurpose themes with lighter options where you can.
For scripts you do need, ask your developer whether they can load later. Many chat widgets, review badges and social feeds do not need to load before the main content. Delaying them lets the important part of the page appear first. Ask the same question about anything that loads from another company's servers, since you do not control how fast those servers respond.
Also check fonts. Loading many font families and weights adds requests. Two families with only the weights you use is usually enough.
Checklist: how to speed up a slow website
- Baseline test recorded in PageSpeed Insights for key pages
- Images resized, compressed and in modern formats
- Hero image loads right away; other images lazy-load
- Width and height set on images and embeds
- Unused plugins and scripts removed
- Third-party tags reviewed and trimmed
- Page caching turned on
- CDN in place if your audience is spread out
- Fonts limited to what you use
- Core Web Vitals report in Search Console checked monthly
When should you rebuild instead of fixing?
Sometimes a site is slow because of how it was built. If it sits on an old theme stacked with page-builder layers and dozens of plugins, every fix becomes a fight. You may improve the score a little, only to see it slide again after the next update.
A rebuild makes sense when fixes keep failing, when the site is hard to edit, or when you are planning a redesign anyway. A clean build with light code, optimized images and only the features you need is usually easier to keep fast. Our website plans are one-time fixed prices, and our ready-made websites are another quick option if you want a fresh start.
Want this done for you?
Website plans from $500. Fixed prices, no contracts, and you own every account.



