Core Web Vitals Improvement: The 80/20 List
Core Web Vitals improvement rarely requires a full rebuild. Most sites fail on three or four specific technical debts, an oversized hero image, a blocking third-party script, layout shift from unset image dimensions, that account for nearly all of the gap between a failing score and a passing one. Fix those first; the rest is optional polish.
Core Web Vitals Improvement: The 80/20 List
Core Web Vitals improvement rarely requires a full rebuild. Most sites fail on three or four specific technical debts, an oversized hero image, a blocking third-party script, layout shift from unset image dimensions, that account for nearly all of the gap between a failing score and a passing one. Fix those first; the rest is optional polish.
What Core Web Vitals actually measure now
Google evaluates three metrics, each scored at the 75th percentile of real visitor sessions, not a single lab test. Google's own web.dev documentation defines the three: Largest Contentful Paint (LCP) measures how quickly the largest visible element loads, Interaction to Next Paint (INP) measures how quickly the page responds after a real user interaction, and Cumulative Layout Shift (CLS) measures how much visible content jumps around while the page is loading.
| Metric | What it measures | Good threshold (75th percentile) |
|---|---|---|
| LCP | How fast the largest visible element (usually a hero image or headline) finishes rendering | 2.5 seconds or less |
| INP | How fast the page responds after a click, tap, or keypress, measured across the full session | 200 milliseconds or less |
| CLS | How much visible content shifts position after it has already rendered | 0.1 or less |
A page needs all three in the "good" band at the 75th percentile to earn Google's overall "good" Core Web Vitals assessment. Missing on just one, usually INP or CLS, is enough to fail the whole page even if the other two are excellent.
cms vs static site covers a related upstream decision: some CMS platforms carry enough default JavaScript and plugin weight that Core Web Vitals improvement work has to start with the platform itself, not just the page.
Why the fix is worth the engineering time
The business case for core web vitals improvement is more concrete than most SEO advice. A 2026 statistics roundup of Core Web Vitals and site speed cites a joint Deloitte and Google study finding that a 0.1-second improvement in load time increased retail conversion rates by 8.4 percent, and documents two real case studies: Vodafone saw an 8 percent increase in sales after improving LCP by 31 percent, and Rakuten 24's A/B test of a faster LCP produced a 53.37 percent increase in revenue per visitor and a 33.13 percent increase in conversion rate.
The gap between sites that pass and sites that don't is also wider than most teams assume. A 2026 Core Web Vitals statistics report puts January 2026 CrUX data at 68.3 percent of origins passing LCP, 87.1 percent passing INP, and 80.9 percent passing CLS, meaning roughly one in three sites is still failing the metric that correlates most directly with the conversion numbers above.
website conversion rate optimization covers the wider set of conversion levers beyond page speed, for teams whose Core Web Vitals scores are already solid and need the next lever to pull.
The CUBEevo 80/20 List
After auditing Core Web Vitals reports for Malaysian client sites across e-commerce, SaaS, and content publishing, the same five fixes account for most of the gap between a failing score and a passing one, regardless of industry. That's the short answer to how to improve Core Web Vitals without turning it into a six-month project: fix the handful of things that move the score the most, first. This is the CUBEevo 80/20 List: the handful of fixes worth doing before anything else on a typical Core Web Vitals checklist.
| Fix | What it actually targets | Why it's high-leverage |
|---|---|---|
| Compress and preload the LCP element | The single image or text block Google measures for LCP, usually a hero image or headline | Often the single biggest score movement on the whole page, and rarely requires a redesign |
| Defer or remove blocking third-party scripts | Chat widgets, personalization tools, and ad tags that execute before the user can interact | The most common cause of poor INP, since these scripts run on the main thread whether or not the user asked for them yet |
| Reserve space for images, embeds, and ads | Any element that loads after the surrounding layout has already rendered | Usually fixes the majority of a page's CLS score with a single CSS attribute, no JavaScript required |
| Break long JavaScript tasks into smaller chunks | Any script that blocks the main thread for more than 50 milliseconds at a time | Directly improves INP, since the browser can't respond to a click while a long task is running |
| Move static assets to a CDN with edge caching | Images, fonts, and scripts served from a single origin server | Improves LCP for visitors physically far from the origin server, which matters more in a regional market like Malaysia than global benchmarks usually account for |
Most sites that fail Core Web Vitals fail on the first two rows of this table specifically: an unoptimized hero image and at least one blocking third-party script. Fixing those two alone is usually enough to move a page from "poor" to "needs improvement," with the remaining fixes closing the rest of the gap.
Where the largest contentful paint fix actually lives
A largest contentful paint fix almost never means "make everything on the page smaller." It means finding the one specific element Google is measuring, usually visible in Chrome DevTools' Performance panel or the PageSpeed Insights report, and fixing that element specifically. A common pattern: the LCP element is a hero image served at full camera resolution, with no modern format (WebP or AVIF), no explicit width and height, and no preload hint, so the browser doesn't even start fetching it until it has parsed most of the page's CSS first.
Interaction to next paint optimization works differently, because INP isn't measured once, it's measured across every interaction in a real session and reported at the 75th percentile. A page can have a fast INP on the first click and a slow one on the fifth, if a background script kicks off partway through the session. The fix is almost always the same regardless of which specific interaction is slow: identify the long JavaScript tasks blocking the main thread and either defer them, split them into smaller chunks the browser can interrupt, or remove them if they're not earning their weight.
ux design principles covers a closely related discipline: a layout that's visually stable by design, with space reserved for every dynamic element before it loads, avoids most CLS problems before a Core Web Vitals audit ever needs to catch them.
What a Malaysian electronics retailer learned about the 80/20 list
A Kuala Lumpur based electronics and appliance e-commerce retailer came to CUBEevo with a Search Console Core Web Vitals report showing 82 percent of mobile product page URLs rated "Poor." Product pages averaged an LCP of 5.8 seconds, driven by full-resolution product photography with no compression or preload, and an INP averaging 340 milliseconds, caused by a live chat widget and a personalization script that both loaded synchronously on every page regardless of whether the visitor ever used either one. Mobile cart abandonment on product pages sat at roughly 71 percent, and organic sessions to product pages had stayed flat for two quarters despite page-one rankings for several commercial keywords.
CUBEevo ran the 80/20 List against the product page template. The hero product images were converted to WebP, resized to actual display dimensions, and given an explicit preload hint. The live chat and personalization scripts were moved to load only after the user's first interaction with the page, rather than on initial load. Explicit width and height attributes were added to every product image and the promotional banner causing the largest CLS shifts, and a handful of long JavaScript tasks in the product gallery script were split into smaller chunks.
Within one quarter, LCP on product pages dropped to 2.1 seconds and INP dropped to 175 milliseconds, both comfortably in the "good" range. The share of "Poor" URLs in Search Console fell from 82 percent to 9 percent. Mobile cart abandonment on product pages dropped from 71 percent to 54 percent, and organic sessions to product pages rose 38 percent over the same quarter, with no change to the keywords the pages were already ranking for. Nothing about the products or the rankings had changed. What changed was whether the page let a visitor actually reach the buy button.
ecommerce website design malaysia covers the fuller stack and cost picture for Malaysian e-commerce builds, including where Core Web Vitals performance fits into the broader platform decision.
How to choose a digital agency for Core Web Vitals work
For Malaysian businesses evaluating a partner for Core Web Vitals improvement specifically, four criteria separate an agency that fixes the score from one that fixes the underlying user experience the score is actually measuring.
| Criterion | What good looks like | Red flag |
|---|---|---|
| Diagnoses the specific failing element, not just the score | The agency identifies the exact image, script, or layout shift causing the failure before proposing a fix | The pitch is a generic "site speed audit" with no mention of which specific element is failing |
| Prioritises by real-user impact, not lab score alone | Fixes are ranked by 75th-percentile field data (CrUX or Search Console), matching how Google actually evaluates the page | Success is measured only in a Lighthouse lab score, which can look good while real users still have a poor experience |
| Treats INP and CLS as seriously as LCP | All three metrics get dedicated diagnostic work, since INP and CLS fail pages just as often as LCP does | The engagement focuses almost entirely on load speed and treats interactivity and layout stability as an afterthought |
| Ships fixes without breaking the design | Core Web Vitals improvement work is tested against the actual UI before and after, not just the score | Fixes technically pass the audit but visibly degrade the page, a stripped-down hero image or a broken layout |
A digital agency Malaysia businesses can trust with Core Web Vitals work is one that treats the score as a proxy for a real visitor's experience, not the end goal itself. For Malaysian businesses ready to close the gap between a failing report and a passing one, our digital agency Malaysia team has been building and optimising digital experiences for 400+ businesses across Malaysia and Southeast Asia since 2007.
Core Web Vitals Improvement: Where to Start
If none of this has been touched yet, core web vitals improvement work should start in this order: pull the Search Console report to see which of the three metrics is actually failing and on which pages, fix the LCP element and any blocking third-party scripts first since those two moves account for most of the score gain, then close out layout shift and long JavaScript tasks. That sequence, not a full platform migration, is what moved the case study above from 82 percent Poor URLs to 9 percent in a single quarter.
FAQ
Q: What is Core Web Vitals improvement, and where should a team actually start?
Core Web Vitals improvement is the process of diagnosing and fixing the specific technical causes behind a failing LCP, INP, or CLS score, rather than making broad, unfocused performance changes. The right place to start is Google Search Console's Core Web Vitals report or a PageSpeed Insights test, which identifies which of the three metrics is actually failing and on which pages, before any fix work begins.
Q: How do I improve Core Web Vitals without a full site rebuild?
Most teams asking how to improve Core Web Vitals can get most of the way there with five specific fixes: compressing and preloading the LCP element, deferring blocking third-party scripts, reserving layout space for elements that load late, breaking up long JavaScript tasks, and serving static assets from a CDN. None of these require a platform migration or a design overhaul.
Q: What belongs on a practical Core Web Vitals checklist?
A useful core web vitals checklist starts with identifying the specific LCP element and confirming it's compressed, sized correctly, and preloaded; auditing every third-party script for whether it blocks the main thread before the user has interacted; confirming every image, ad, and embed has reserved layout space; and checking Search Console's field data, not just a single lab test, before calling any fix complete.
Q: What's the fastest way to approach interaction to next paint optimization?
Interaction to next paint optimization almost always starts with identifying which scripts are running long tasks on the main thread, since INP problems are caused by JavaScript blocking the browser's ability to respond to input, not by network speed. Deferring non-essential scripts until after the user's first interaction, and breaking any remaining long tasks into smaller chunks, resolves most INP failures without removing functionality.
Q: What counts as a good Core Web Vitals score in 2026?
A good core web vitals score means all three metrics land in the "good" band at the 75th percentile of real visitor sessions: LCP at 2.5 seconds or less, INP at 200 milliseconds or less, and CLS at 0.1 or less. A page needs all three passing simultaneously; a strong LCP score does not compensate for a failing INP or CLS score in Google's overall assessment.