{"id":7990,"date":"2026-08-01T00:40:02","date_gmt":"2026-08-01T00:40:02","guid":{"rendered":"https:\/\/dextora.agency\/insights\/core-web-vitals-speed-competitive-advantage\/"},"modified":"2026-08-01T08:35:45","modified_gmt":"2026-08-01T08:35:45","slug":"core-web-vitals-speed-competitive-advantage","status":"publish","type":"insight","link":"https:\/\/dextora.agency\/en\/insights\/core-web-vitals-speed-competitive-advantage\/","title":{"rendered":"Speed as a Competitive Advantage: Why Core Web Vitals Matter More Than Design"},"content":{"rendered":"<p>Site speed usually comes up last. Design first, then content, then &#8220;we should probably make it faster&#8221;. The real order is the reverse: a page that never opened has neither design nor content. The visitor simply did not wait.<\/p>\n<p>Core Web Vitals are Google&#8217;s attempt to measure not abstract seconds but what a person actually feels: when the main thing appeared, whether the page responds to a tap, and whether the layout jumps under their finger.<\/p>\n<h2>Three metrics and their thresholds<\/h2>\n<table>\n<thead>\n<tr>\n<th>Metric<\/th>\n<th>What it measures<\/th>\n<th>Good<\/th>\n<th>Poor<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>LCP<\/td>\n<td>When the largest element of the screen appeared<\/td>\n<td>under 2.5 s<\/td>\n<td>over 4 s<\/td>\n<\/tr>\n<tr>\n<td>INP<\/td>\n<td>Delay in responding to user interaction<\/td>\n<td>under 200 ms<\/td>\n<td>over 500 ms<\/td>\n<\/tr>\n<tr>\n<td>CLS<\/td>\n<td>How much the layout shifts while loading<\/td>\n<td>under 0.1<\/td>\n<td>over 0.25<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Scoring uses the 75th percentile of real visitors. That matters: if three quarters of people have a good experience and one quarter does not, the metric still fails. Testing on your own laptop over a wired connection is meaningless.<\/p>\n<h2>LCP: what actually slows it down<\/h2>\n<p>In 90% of cases the largest element is either a big image or the first-screen headline. The causes of delay come from a short list:<\/p>\n<ul>\n<li><strong>A heavy image in an outdated format.<\/strong> A 1.5 MB JPEG where WebP would deliver 200 KB at the same quality.<\/li>\n<li><strong>Lazy loading on the first screen.<\/strong> A <code>loading=\"lazy\"<\/code> attribute on the hero image defers precisely the thing that must appear first.<\/li>\n<li><strong>Fonts that block text.<\/strong> Without <code>font-display: swap<\/code> the headline waits for the font to download.<\/li>\n<li><strong>A slow server response.<\/strong> If the server thinks for a second, nothing downstream will save you.<\/li>\n<li><strong>Video on the first screen.<\/strong> Beautiful, and expensive in seconds.<\/li>\n<\/ul>\n<h2>INP: why a page feels sticky<\/h2>\n<p>INP replaced FID and measures not the first response but the worst one across the session. That is a more honest metric: people remember exactly the moment they tapped and nothing happened.<\/p>\n<p>The cause is almost always the same &#8211; long JavaScript tasks. While a script computes for 300 milliseconds, the browser cannot process the tap. Usual suspects: heavy third-party scripts, handlers firing on every scroll pixel, synchronous work on click, several analytics systems running at once.<\/p>\n<h2>CLS: layout jumps<\/h2>\n<p>The most irritating problem from the user&#8217;s point of view and the easiest to fix. Causes:<\/p>\n<ul>\n<li>Images without declared width and height. The browser does not know how much space to reserve and pushes content down once the image loads.<\/li>\n<li>Ads and widgets injected after load.<\/li>\n<li>Font swapping: different letter widths shift paragraphs.<\/li>\n<li><a href=\"https:\/\/dextora.agency\/en\/insights\/analytics-without-cookies-measuring-with-less-data-guide\/\">Cookie consent<\/a> banners appearing over the content.<\/li>\n<\/ul>\n<p>The rule is simple: anything that will appear later must reserve its space in advance.<\/p>\n<h2>Lab data versus real data<\/h2>\n<p>This is a common source of confusion. Tools like Lighthouse give a lab run: one execution, stable conditions, simulation. For ranking, Google uses field data &#8211; real visits by real people on real devices.<\/p>\n<p>So a green Lighthouse score alongside failing Core Web Vitals in Search Console is entirely normal. Lab data is for finding causes; field data is for judging the state. Trust the second.<\/p>\n<h2>What this gives the business<\/h2>\n<p>Speed affects money in two ways. Directly: someone who did not wait will never see your offer or your button. Indirectly: speed is a ranking factor, and slow sites are crawled less often.<\/p>\n<p>A practical benchmark: most of the loss from a slow site falls on mobile users with poor connections. That is exactly the audience nobody sees when testing in the office.<\/p>\n<h2>A sequence of work that produces results<\/h2>\n<ol>\n<li><strong>Look at field data.<\/strong> Search Console, Core Web Vitals section. That is the starting point, not Lighthouse.<\/li>\n<li><strong>Find the worst page template.<\/strong> The problem is usually not site-wide but confined to one page type.<\/li>\n<li><strong>Start with images.<\/strong> Modern formats, correct dimensions, no lazy loading on the first screen. The cheapest win available.<\/li>\n<li><strong>Remove unnecessary third-party scripts.<\/strong> Count how many you actually have and whether all are needed.<\/li>\n<li><strong>Reserve space for everything that loads late.<\/strong> CLS can be cured in a day.<\/li>\n<li><strong>Return to field data after 28 days.<\/strong> Changes need that long to accumulate.<\/li>\n<\/ol>\n<h2>The most common mistakes<\/h2>\n<ul>\n<li><strong>Chasing a perfect Lighthouse score.<\/strong> The difference between 85 and 98 is often invisible to users and consumes more time than everything else combined.<\/li>\n<li><strong>A plugin instead of a cause.<\/strong> A caching plugin hides the symptom but will not remove three megabytes of images.<\/li>\n<li><strong>Optimising without a baseline.<\/strong> Without before-numbers you cannot say what helped.<\/li>\n<li><strong>Testing on desktop only.<\/strong> The real losses are always on mobile.<\/li>\n<\/ul>\n<p>Speed is rarely the main reason a site fails to generate enquiries. But it is almost always a multiplier: everything else performs worse while the page takes four seconds to load. Which is why it is worth starting there, rather than after the <a href=\"https:\/\/dextora.agency\/en\/insights\/website-redesign-without-losing-traffic-rankings\/\">redesign<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>LCP, INP and CLS in plain terms: which thresholds count as good, what actually slows a page down, how lab data differs from field data, and the order of work that produces measurable results.<\/p>\n","protected":false},"author":5,"featured_media":7986,"template":"","insight_category":[154],"insight_tag":[178,172,162],"class_list":["post-7990","insight","type-insight","status-publish","has-post-thumbnail","hentry","insight_category-guides","insight_tag-performance","insight_tag-seo","insight_tag-web-development"],"acf":[],"_links":{"self":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight\/7990","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight"}],"about":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/types\/insight"}],"author":[{"embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/users\/5"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/media\/7986"}],"wp:attachment":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/media?parent=7990"}],"wp:term":[{"taxonomy":"insight_category","embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight_category?post=7990"},{"taxonomy":"insight_tag","embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight_tag?post=7990"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}