# Why Your Website Is Slow (and How to Fix It): Core Web Vitals in Plain English
You know the feeling. You tap a link on your phone, somewhere between the BTS and the office, and nothing happens. A white screen appears. A spinning circle turns. Half a picture loads. By the time the page finally appears, you have already lost interest.
Your customers experience the same thing when they visit a slow website.
For businesses in Thailand, where customers often browse on mobile devices while travelling or switching between apps, website performance deserves more attention than it usually gets. A slow website can frustrate visitors, make products and services harder to explore, and interrupt the journey from discovering your business to contacting you.
Speed also matters for search visibility. Google uses page experience signals, including Core Web Vitals, as part of its ranking systems. But a fast website will not automatically outrank a competitor with more relevant content or a stronger reputation.
The practical goal is simple: make your website load quickly, respond reliably, and remain easy to use.
In this guide, we explain what makes websites slow, how to test your own website, what Core Web Vitals actually measure, and which fixes are worth tackling first.
How much does website speed really matter?
Website speed affects more than the time it takes for a page to appear.
When visitors have to wait, they may leave before reading your content, viewing your products, or submitting an enquiry. Slow interactions can also make a website feel broken, even when the underlying server is working.
For an ecommerce store, that could mean customers abandoning a product page before reaching checkout. For a service business, it could mean a potential client giving up before the contact form loads.
Performance also affects how people perceive your business. A website that responds smoothly feels more reliable than one where images jump around, buttons lag, and content appears unpredictably.
That does not mean every millisecond translates directly into a particular amount of revenue. The commercial impact depends on your audience, website, offer, and the source of your traffic.
The sensible approach is to measure performance, identify the biggest problems, and prioritise improvements that make the website easier to use.
What are Core Web Vitals?
Core Web Vitals are Google's measurements of three important aspects of the user experience: loading performance, responsiveness, and visual stability.
The three metrics are:
- Largest Contentful Paint (LCP): How quickly the main content becomes visible.
- Interaction to Next Paint (INP): How quickly the page responds visually after a user interaction.
- Cumulative Layout Shift (CLS): How much the page layout unexpectedly moves while loading.
These metrics measure different problems. A page can display its main content quickly but still feel slow when someone taps a menu. Another page may respond immediately but move around as images and advertisements load.
Google's recommended thresholds for a good experience, measured at the 75th percentile of real visits, are:
Metric Good result What it tells you
--- --- ---
LCP 2.5 seconds or less How quickly the main content loads
INP 200 milliseconds or less How responsive the page feels
CLS 0.1 or less How visually stable the layout is
The 75th percentile means that the thresholds should be met for at least 75% of visits, assessed separately for mobile and desktop where sufficient data is available.
These are useful targets, not a guarantee of rankings or conversions. They help you identify whether visitors are experiencing performance problems.
1. Largest Contentful Paint: why the main content takes too long to appear
Imagine opening a business website and seeing an empty space for several seconds before the main heading or hero image finally appears.
That is the kind of experience LCP helps assess.
The LCP element is typically the largest visible image, text block, or other content element within the initial viewport. On a marketing website, it might be the main hero image or a large heading.
What causes a poor LCP score?
Common causes include:
- A slow server or delayed initial HTML response.
- Large hero images that take too long to download.
- Images that are discovered late by the browser.
- Render-blocking CSS or JavaScript.
- Excessive third-party scripts.
- Unnecessary redirects before the page begins loading.
How to improve LCP
Start by identifying the actual LCP element. PageSpeed Insights can help show what is loading slowly and which resources are involved.
If the main element is a large image, check its file size, dimensions, and format. Use an appropriately sized WebP or AVIF image where suitable, rather than serving an unnecessarily large original.
If the server takes too long to respond, investigate hosting performance, caching, database queries, and the page's backend workload.
For WordPress websites, a well-configured page cache can help reduce repeated processing for pages that do not need to be generated from scratch on every visit.
The important point is to fix the resource that is actually delaying the page. Compressing an unrelated footer image will not solve a slow hero image.
2. Interaction to Next Paint: why buttons and menus feel unresponsive
A website can appear fully loaded and still feel slow.
You tap the menu button, but nothing happens immediately. You click a filter, and the product list freezes. You press a button, and the page takes too long to react.
Interaction to Next Paint, or INP, measures the responsiveness of a page across user interactions during a visit. It looks at how long it takes for the browser to present the next visual update after an interaction.
What causes poor INP?
One frequent cause is excessive JavaScript work on the main browser thread.
When the browser is busy processing a large task, it may not respond promptly to the next click or tap. Heavy scripts, complex animations, oversized page builders, and third-party integrations can all contribute, depending on how they are implemented.
How to improve INP
Review the scripts and interactive features that run on your pages.
Remove unnecessary functionality, reduce expensive JavaScript tasks, and investigate scripts that block the browser from responding. Where appropriate, break long tasks into smaller pieces or defer work that does not need to happen immediately.
If you use Elementor or another visual page builder, do not assume that the builder itself is the entire problem. The number and behaviour of widgets, animations, add-ons, and third-party scripts all matter.
Test the interactions that customers actually use, such as navigation, product filters, accordions, booking forms, and checkout buttons.
A useful performance improvement should make those actions feel faster, not merely improve a score in a testing tool.
3. Cumulative Layout Shift: why your website jumps around
Have you ever tried to tap a button, only for an image to load above it and push the button somewhere else?
That is a layout shift.
Cumulative Layout Shift, or CLS, measures unexpected movement of visible page elements during a visit. A high score can make a website frustrating to use, particularly on mobile devices.
What causes layout shifts?
Common causes include:
- Images without reserved dimensions.
- Advertisements or embedded content that appears after the page loads.
- Web fonts that change the layout when they load.
- Banners inserted above existing content.
- Elements that expand unexpectedly after loading.
How to improve CLS
Give images and videos appropriate width and height attributes or reserve space for them through CSS. This allows the browser to allocate space before the media finishes loading.
Reserve space for advertisements, embeds, and other elements that may appear later. Avoid inserting new content above something the visitor is already reading unless it is a response to their action.
If text shifts when a web font loads, review font loading and fallback font metrics.
For WordPress and Elementor websites, inspect hero sections, image widgets, pop-ups, sticky headers, and dynamically inserted elements. Small layout changes can become noticeable when several occur together.
The goal is not to eliminate all animation. It is to prevent unexpected movement that interferes with reading or clicking.
How to test your website speed in two minutes
You do not need expensive software to begin investigating a slow website.
Start with Google's PageSpeed Insights:
https://pagespeed.web.dev/
Follow these steps:
- Open PageSpeed Insights.
- Enter the URL of a page you want to test.
- Run the analysis.
- Review the mobile results first if most of your customers visit on phones.
- Check the Core Web Vitals assessment and the individual LCP, INP, and CLS measurements where available.
- Scroll down to the diagnostics and opportunities to see which resources or tasks are causing problems.
Test more than the homepage. Your service pages, product pages, blog articles, and checkout can behave very differently.
For example, the homepage might load quickly because it is cached, while a product category page struggles because it loads many images and filters.
Understand lab data versus real-user data
PageSpeed Insights can provide two different kinds of information.
Lab data comes from a controlled test environment. It is useful for diagnosing issues and comparing changes under similar conditions.
Field data reflects real visits collected through the Chrome User Experience Report when sufficient data is available. It helps show how actual users experience the page.
A page may have a good lab score but weaker real-world results because visitors use different devices, networks, and browsers.
The reverse can also happen.
If field data is unavailable for a page, that does not automatically mean the page is slow or that something is broken. There may simply not be enough eligible data for a report.
The five most common reasons websites are slow
Once you have tested your website, look for these common causes.
1. Images are too large
Large images are one of the easiest problems to overlook.
A website may display an image at 600 pixels wide while downloading a file several thousand pixels wide. On mobile devices, this can waste bandwidth and delay the page.
Resize images to dimensions appropriate for their display area, compress them, and use modern formats where appropriate.
Responsive images can also help the browser select a suitable file for the screen size.
Do not lazy-load the main hero image if it is the LCP element. Lazy loading is generally more useful for images further down the page that are not immediately visible.
2. Too many plugins or scripts
WordPress plugins can add useful functionality, but each one should have a clear purpose.
Some plugins add scripts or styles across the whole website even when their features are used on only a few pages. Others introduce database queries, remote requests, or background processing.
Review the plugins you actually use. Remove redundant ones, replace unnecessarily heavy solutions when there is a suitable alternative, and test performance after each meaningful change.
Simply counting plugins is not a reliable way to judge performance. One poorly implemented plugin can cause more problems than several lightweight ones.
3. Poor caching configuration
Caching can reduce repeated work and help pages load faster.
Depending on the website, useful measures may include page caching, browser caching, and object caching. A content delivery network may also help serve assets closer to visitors.
The right configuration depends on the hosting environment, platform, and type of content.
Be careful with caching on ecommerce sites and websites with personalised content. Cart pages, account pages, and other dynamic content may require special handling to avoid showing the wrong information to a user.
If you use a WordPress caching plugin, test the actual site after making changes. Aggressive CSS or JavaScript optimisation can sometimes break menus, layouts, forms, or other functionality.
4. Slow hosting or server response
If the server takes a long time to deliver the initial response, front-end optimisation alone may not solve the problem.
Possible causes include limited server resources, inefficient database queries, expensive dynamic processing, or a poorly configured hosting environment.
Check the initial server response and compare performance across several pages. If the delay persists after basic optimisation, ask your hosting provider or developer to investigate the server-side workload.
Upgrading hosting can help in some situations, but it should follow diagnosis rather than be the first thing you purchase.
5. Too much content and too many effects above the fold
Large sliders, video backgrounds, multiple animation libraries, pop-ups, and several third-party widgets can make the initial page more complicated than it needs to be.
A visually impressive website does not need every element to animate or load immediately.
Keep the first screen focused on the main message and the most important action. Load non-essential elements later when appropriate, and remove visual effects that do not improve the customer experience.
Good design and good performance can coexist. The key is deciding which elements deserve the resources they consume.
A practical website speed checklist
Use this checklist when reviewing a slow WordPress or business website.
- [ ] Test the homepage and several important internal pages.
- [ ] Check mobile and desktop results separately.
- [ ] Identify the actual LCP element.
- [ ] Resize and compress oversized images.
- [ ] Avoid lazy-loading the main above-the-fold image.
- [ ] Review unnecessary plugins, scripts, and third-party integrations.
- [ ] Check caching and server response times.
- [ ] Reserve space for images, videos, banners, and embeds.
- [ ] Test menus, forms, filters, and other interactive features.
- [ ] Confirm that optimisation changes have not broken the website.
- [ ] Retest after making changes and compare the results.
Do not attempt every optimisation at once. Make a change, verify that the site still works, and measure the outcome.
Does website speed affect Google rankings?
Website performance is one part of Google's broader page experience considerations. Core Web Vitals are used in Google's ranking systems, but good scores alone do not guarantee high rankings.
Google still needs to determine whether a page is relevant and useful for the search query. Content quality, search intent, competition, and other signals remain important.
That is why performance work should happen alongside good SEO practices, including useful content, clear site structure, crawlable links, and accurate page metadata.
A fast website with poor content may still struggle to rank. A useful website with severe performance problems may also deliver a poor experience.
The objective is to remove avoidable friction while making the site genuinely useful to visitors.
Frequently asked questions
What is a good website loading speed?
For Core Web Vitals, Google recommends an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS of 0.1 or less, measured at the 75th percentile of visits. These metrics cover different aspects of the experience, so there is no single number that describes every part of website performance.
Why is my WordPress website slow?
Common causes include oversized images, poorly configured caching, heavy scripts, inefficient plugins, slow server responses, and excessive third-party integrations. Test the affected pages first so you can identify the actual bottleneck.
Will a caching plugin make my website faster?
It can, particularly when repeated server-side page generation is contributing to slow responses. However, caching cannot fix every problem, and incorrect settings can break dynamic features. Test the site after making changes.
Does Elementor slow down a website?
Elementor can add page structure, styles, and scripts, but performance depends on how the website is built, which widgets and add-ons are used, and how the site is hosted and optimised. A carefully built Elementor site can perform well, while an overloaded site built with any platform can be slow.
Should I aim for a 100 PageSpeed score?
Not at the expense of functionality or useful design. A high lab score is helpful, but real-user experience and Core Web Vitals matter too. Prioritise meaningful improvements rather than removing necessary features just to reach a perfect score.
How often should I test my website speed?
Test after significant design, plugin, theme, hosting, or integration changes. Periodic checks are also useful for important pages because new content, scripts, and features can introduce performance problems over time.
Final thoughts
A slow website is rarely fixed by one magic plugin or a single setting. The most effective improvements come from identifying the actual bottleneck and addressing it in the right order.
Start with PageSpeed Insights, check your Core Web Vitals, and prioritise the biggest issues affecting your visitors. Optimise images, review unnecessary scripts, improve caching where appropriate, and investigate server delays when the evidence points to the backend.
If your website is slow despite basic optimisation, a technical review can help identify problems that are difficult to spot from a score alone.
Klickode builds and maintains business websites with attention to performance, usability, and long-term maintainability.
Need help improving your website? Contact Klickode to discuss a website performance review or development project.