Core Web Vitals are three measurements Google uses to judge how a web page feels to real visitors: how fast the main content appears, how quickly the page responds when someone taps, and whether things jump around while it loads. They are part of how Google ranks pages, and more importantly, they describe the experience your customers have on their phones. This guide explains Core Web Vitals in plain words, shows how to measure them for free, and lists the fixes that work best for websites in Bangladesh.
The three Core Web Vitals in plain words
| Name | What it measures | Good result |
|---|---|---|
| LCP – Largest Contentful Paint | How long until the biggest thing on the screen (usually the main image or heading) is visible. | 2.5 seconds or less |
| INP – Interaction to Next Paint | How quickly the page reacts when a visitor taps a button, opens a menu or types. | 200 milliseconds or less |
| CLS – Cumulative Layout Shift | How much the layout moves unexpectedly while loading. | 0.1 or less |
These thresholds are Google's published targets. A page "passes" when most real visits meet all three.
LCP: "When can I see the page?"
Imagine opening a shop's website on mobile data. The menu appears, but the big banner photo and headline take a long time. Until they show up, the visitor is staring at an empty space. That waiting time is LCP. Slow servers, huge images and render-blocking fonts or scripts are the usual causes.
INP: "Does it react when I tap?"
You tap "Order now" and nothing happens for a moment, so you tap again. That delay is what INP measures. It is usually caused by heavy JavaScript — sliders, chat widgets, tracking codes, page builders — keeping the phone's processor busy. On mid-range Android phones, which many visitors use, this delay is much worse than on a developer's laptop.
CLS: "Why did the button move?"
You are about to tap a link and an advert or image suddenly loads above it, pushing everything down, so you tap the wrong thing. That is layout shift. Images without fixed sizes, ads, cookie banners and late-loading fonts cause it.
How to measure Core Web Vitals
PageSpeed Insights
Go to pagespeed.web.dev, enter a page address and run the test. You will see two sections:
- "Discover what your real users are experiencing" — field data from real Chrome users over the last 28 days. This is what Google uses. Small sites may not have enough visitors for this section to appear.
- "Diagnose performance issues" — a lab test run once by Google's server. Useful for finding causes, but the score changes from run to run.
Always check the Mobile tab first. Test your home page, your most important service page and one blog post.
Google Search Console
In Search Console, the Core Web Vitals report groups your pages into Good, Needs improvement and Poor, for mobile and desktop separately. It is the best way to see problems across the whole site rather than one page at a time.
How to fix LCP (slow main content)
- Start with fast hosting. If PageSpeed reports a slow server response time, no plugin will fix it fully. Hosting with NVMe SSD storage, LiteSpeed and a current PHP version makes the first byte arrive sooner. Our hosting plans are set up this way.
- Resize the hero image. A banner photo straight from a camera or phone can be several megabytes. Resize it to the size it is shown at, compress it and use WebP format.
- Do not lazy-load the first image. Lazy loading is great for images further down, but the main banner should load immediately.
- Remove the slider. Home-page sliders with five big images are a common LCP problem — and most visitors never see slide two. One strong image and headline usually work better.
- Use caching. Page caching serves ready-made pages instead of building them on every visit. On WordPress, LiteSpeed Cache does this on LiteSpeed servers.
How to fix INP (slow response to taps)
- Audit third-party scripts. Facebook Pixel, Google Analytics, Tag Manager, chat widgets, heatmaps and ad codes all add JavaScript. Keep the ones you actually use and remove the rest.
- Reduce plugins and page-builder add-ons. Each one may load its own scripts on every page.
- Delay non-essential scripts. Chat and tracking scripts can load after the page becomes usable.
- Test on a real phone. Use an ordinary Android phone, not only a fast laptop, to feel what your visitors feel.
How to fix CLS (jumping layout)
- Give images a width and height so the browser reserves space before they load.
- Reserve space for ads and embeds such as YouTube videos and Facebook posts.
- Load fonts carefully. Use few font files and the
font-display: swapsetting, and preload the main font if possible. Bangla fonts can be large, so include only the weights you use. - Do not insert banners at the top after loading. Notices and cookie bars should overlay the page or have space reserved.
Common problems on Bangladeshi websites
- News portals with many ads: ad slots without reserved space cause heavy CLS, and ad scripts hurt INP. Fixed-size ad containers help a lot.
- Shops with uncompressed product photos: product images uploaded straight from phones slow LCP on category pages.
- Several tracking codes added over the years: old pixels and tags that nobody uses any more still load on every page.
- Cheap overloaded hosting: pages wait a long time before the server responds, especially in the evening.
Do Core Web Vitals really affect rankings?
Yes, but content still matters most. Google uses page experience signals, including Core Web Vitals, alongside relevance and quality. A fast page with weak content will not beat a strong, helpful page. But when two pages are similarly useful, the faster, more stable one has an edge — and it also converts more visitors into customers, which is the real goal.
A quick Core Web Vitals checklist
- Test your home page and top service page on PageSpeed Insights (Mobile tab).
- Open the Core Web Vitals report in Google Search Console to see site-wide problems.
- Fix slow server response first — upgrade hosting if needed. WordPress sites benefit from hosting tuned for WordPress with LiteSpeed caching.
- Resize, compress and convert large images to WebP; never lazy-load the main banner.
- Remove unused plugins, tracking codes and widgets.
- Add width and height to images and reserve space for ads and embeds.
- Limit font files, especially large Bangla fonts.
- Re-test after each change, and again every month.
Work through the list in this order. Hosting and images usually bring the biggest improvement for the least effort, while script clean-up takes a little more care but fixes the slow taps visitors notice most.
Frequently asked questions
Why is my PageSpeed score different every time I test?
The lab test runs once on Google's servers and is affected by network conditions. Look at the trend and the real-user data rather than a single score.
My site has no field data. What does that mean?
Your site does not yet have enough Chrome visitors for Google to report real-user data. Use the lab results and Search Console as a guide until traffic grows.
Is a score of 100 necessary?
No. Aim to pass all three Core Web Vitals on mobile. Chasing a perfect score often brings little extra benefit.
Can my existing website be fixed, or does it need rebuilding?
Many sites improve a lot with better hosting, smaller images and fewer scripts. If the theme or page builder itself is the problem, a redesign may be the better long-term fix.
For WordPress-specific steps, read our guide to speeding up a WordPress website. Want us to check your Core Web Vitals? Contact us for a free review.