Web Development
Why is my website slow? Core Web Vitals in plain English, and 8 fixes
A slow site loses visitors before they read a word. How to measure your speed, what LCP, INP and CLS actually mean, and the fixes that make the biggest difference on most small business sites.
By NeuHaze Team4 min read
Short answer: most slow websites are slowed down by the same few things: images that are far too large, too many plugins and third-party scripts, cheap or distant hosting, and no caching. Test your site in Google's free PageSpeed Insights, look at the three Core Web Vitals, and fix the biggest problem first. Compressing images alone often makes the largest difference.
How to measure your website's speed
- Open PageSpeed Insights (pagespeed.web.dev) and test your home page and your most important page, such as a product or service page.
- Look at the mobile result first. Most visitors are on phones, and phones are slower.
- The top section shows real-user data from Chrome when your site has enough visitors. The lab score below it is a simulation, useful for finding causes.
- Check Search Console → Core Web Vitals to see which groups of pages need work.
Core Web Vitals in plain English
Google measures three things about how a page feels to real visitors. A page passes when at least 75% of visits meet each target:
- LCP (Largest Contentful Paint): how fast the main content appears. Target: 2.5 seconds or less. Usually slowed by a huge hero image or slow server.
- INP (Interaction to Next Paint): how fast the page responds when you tap or click. Target: 200 milliseconds or less. Usually slowed by heavy JavaScript.
- CLS (Cumulative Layout Shift): how much the page jumps around while loading. Target: 0.1 or less. Usually caused by images, ads or banners without a reserved space.
8 fixes that help most sites
1. Resize and compress images
A photo straight from a phone can be 5 MB; on a web page it rarely needs more than 200 KB. Resize images to the size they're shown at and save them as WebP or AVIF. On neuhaze.com, the five photos behind our home page header are under 60 KB each.
2. Load images only when needed
Images further down the page should load as the visitor scrolls (lazy loading). The main image at the top should load first, not last.
3. Remove plugins and scripts you don't use
Every chat widget, tracking pixel, slider and plugin adds code that the visitor's phone has to download and run. Review them once a year and remove what nobody checks.
4. Use fewer, lighter fonts
Two font families with a few weights is plenty. Host them with the site where possible, so the browser doesn't wait on another server.
5. Turn on caching and a CDN
Caching saves ready-made copies of your pages, so the server doesn't rebuild them for every visitor. A CDN (content delivery network) serves those copies from a location close to each visitor. Many hosts and Cloudflare offer this for free.
6. Choose better hosting
Cheap shared hosting can take a second or more just to start sending a page. If your server response time is slow in PageSpeed Insights, no amount of image work will fully fix it.
7. Reserve space for images and embeds
Give every image, video and ad a set width and height, so text doesn't jump when they load. Cookie banners should overlay the page rather than push it down.
8. Keep heavy work off the first load
Load extras like chat, maps and video players after the page is usable, or only when someone clicks them. Your visitor sees content first and the extras a moment later.
Does website speed affect SEO?
Yes, but it isn't everything. Core Web Vitals are part of how Google judges page experience, and a fast page won't beat a much more useful one. The bigger cost of a slow site is usually people leaving before it loads. Speed is also on our day-one SEO checklist.
Frequently asked questions
What's a good PageSpeed Insights score?
90 or more is good, and 50–89 needs work. Passing the three Core Web Vitals with real visitors matters more than the lab score, which changes a little on every test.
Why is my site fast on my computer but slow for customers?
Your browser has cached the site and you're likely on a fast connection near your server. Customers on phones, slower networks or in other countries see the real load time. Test on mobile in PageSpeed Insights.
Do I need to rebuild my website to make it fast?
Usually not. Images, plugins, caching and hosting fix most sites. A rebuild makes sense when the theme or platform itself is the bottleneck, which is when a custom website or a lighter e-commerce setup pays off.
- Website speed
- Core Web Vitals
- PageSpeed Insights
- SEO
- Performance


