Skip To Content
Header Logo: Digitup Solutions Pvt. Ltd

Core Web Vitals Benchmarks by Industry: What "Good" LCP, INP & CLS Look Like Now

Core Web Vitals Benchmarks by Industry
Core Web Vitals Benchmarks by Industry
Listen to this blog

In this article

Quick answer: This breakdown of Core Web Vitals benchmarks by industry 2026 shows one thing clearly: Google's Core Web Vitals thresholds are the same for every industry. LCP must stay under 2.5 seconds. INP must stay under 200 milliseconds. CLS must stay under 0.1. What changes is how many sites in each sector actually hit those numbers. Tech sites pass the most. News and media sites pass the least. Most e-commerce stores still fail on LCP.

What are Core Web Vitals, and do the "good" thresholds change by industry?

No. The thresholds don't move. Google grades every site the same way. Largest Contentful Paint must be 2.5 seconds or under. Interaction to Next Paint must be 200 milliseconds or under. Cumulative Layout Shift must be 0.1 or under. A page passes only when 75% of real visits clear all three at once. Google tracks this over a rolling 28-day window, using real user data called CrUX. Miss even one metric and the whole page fails. It doesn't matter how well the other two scores look.

What changes by industry is how hard that bar is to hit. A news homepage full of ads is fighting a different battle than a product page full of photos. Both get graded on the same three numbers. So "benchmarks by industry" isn't about different rules. It's about different bottlenecks and different odds of passing.

How do Core Web Vitals pass rates actually differ across sectors?

Data from HTTP Archive and CrUX shows a clear pattern. Tech and SaaS sites pass the most often. Content-heavy publishers pass the least. The Core Web Vitals pass rate by industry looks like this:

Industry

Typical Pass Rate(All 3 vitals)

Most common Bottleneck

Realistic 2026 target

Technology/SaaS

Highest among sectors,around 65%

Dashboard-heavy INP on logged in screens

LCP 1.8–2.2s, INP under 180ms 

E-commerce / Retail 

Roughly 4 in 10 pass all three 

LCP from hero banners and product images 

LCP 1.6–2.0s, CLS near 0 

Travel & Hospitality 

Below average, INP-heavy 

Booking widgets, calendars, filters 

INP under 170ms 

BFSI / Finance 

Mixed, form-heavy pages struggle most 

CLS from disclaimers, consent banners, dynamic forms 

CLS under 0.05 

News & Media 

Lowest pass rate, under 40% 

Ad slots and third-party scripts blocking LCP and CLS 

LCP under 2.2s, CLS under 0.08 

B2B / Enterprise 

Weak on mobile, average LCP around 7 seconds 

Bloated JS from CMS plugins and marketing tags 

LCP under 2.5s is already a win 

These numbers shift every quarter as CrUX refreshes. Treat the table as a guide, not a fixed scoreboard. The goal isn't to memorize a percentage. It's to know which metric is most likely to be your weak spot before you run an audit.

Why do e-commerce and retail sites struggle most with LCP?

Core Web Vitals for e-commerce almost always comes down to LCP first. Product pages are built around images. A category grid, a zoomable product photo, and a hero banner all compete to load first. The browser has to pick one as the "largest contentful element." Add unoptimized image formats, missing lazy-load rules, and scripts that load before the main content, and LCP creeps past 3 or 4 seconds. Most teams don't notice until conversions start dropping.

Retail is also where the business case is clearest. A joint study from Deloitte and Google found that a 0.1-second improvement in load time lifted retail conversion rates by about 8.4%. Travel sites saw an even bigger lift, at 10.1%. That's not a rounding error. On real traffic volumes, that's revenue sitting behind a technical fix.

Which industries fail INP the most, and why?

Most sites, in every sector, still struggle with INP. But it hits hardest on pages built around heavy interaction: filters, booking calendars, cart drawers, dashboards, and checkout forms. Travel platforms feel this. So does any e-commerce site with live filtering or a multi-step checkout. INP tends to spike right where the shopper is closest to buying. That's the worst possible place for a delay.

The fix is rarely one big change. It usually means breaking up long JavaScript tasks, deferring scripts like chat widgets and analytics tags, and keeping the main thread free the moment someone taps a button. One regional example is worth noting. Indian travel platform redBus cut INP sharply on its booking flow and saw a real lift in completed sales. Responsiveness fixes pay off fastest at the exact moment someone is trying to buy.

What does CLS look like across industries, and why does finance struggle here?

CLS problems usually come from content that loads late and pushes everything else down. Think images without set dimensions, embedded ads, cookie banners, or forms that expand after a field validates. Finance and BFSI sites run into this often. Compliance rules mean disclaimers, consent widgets, and dynamic form fields, get added after the page first renders. A shopper tapping the wrong button because the page shifted isn't just annoying. In checkout, or on a loan application, it can mean a lost conversion or a support ticket.

The fix is simple but exact. Reserve space for every image, video, iframe, and ad slot with a set width and height. Avoid adding layout-shifting elements above the fold after the page loads.

What's a realistic Core Web Vitals target for an Indian e-commerce or D2C brand in 2026?

These Core Web Vitals benchmarks for Indian e-commerce websites start from one reality: Indian retail traffic skews heavily mobile. A large share of that traffic comes from mid-range Android phones on 4G, not the fast Wi-Fi most teams test on. That gap matters. A site can look fast on a founder's iPhone and still feel slow to a shopper on a crowded evening connection in a Tier 2 city. CrUX field data catches this gap. Lab tools like Lighthouse often miss it.

Here's a realistic Core Web Vitals target for D2C brands India can work toward in 2026. Keep LCP under 2 seconds on product and category pages, not just the homepage. Keep INP under 180 milliseconds on cart and checkout interactions. Keep CLS near zero all the way through checkout. Test each template on its own. A fast homepage can hide a slow, script-heavy checkout, and checkout is what most mobile shoppers actually experience.

How do you find out where your site actually stands?

Lighthouse and PageSpeed Insights give you lab data. That's a simulated snapshot from one test run. Your real Core Web Vitals score comes from field data instead, the actual 28-day average from real visitors on real devices. The two can disagree a lot, especially for sites with heavy Indian mobile traffic on inconsistent networks.

If your team already knows CLS is fine, but LCP or INP keeps failing on mobile, that's usually a sign it's time for a structured Core Web Vitals audit and optimization  instead of another round of isolated fixes.

Ready to see where your site actually stands?

Benchmarks are a useful reference point. But the only number that really matters is your own. A structured Core Web Vitals audit and optimization engagement gives you a template-by-template breakdown of where LCP, INP, and CLS are costing you conversions, plus a prioritized fix list instead of a generic checklist.

Written by

Profile image of Meghana Prakash

Meghana Prakash

CMS Content Author, Digitup

  • Core Web Vitals
  • Technical Seo

FAQs