Speed as infrastructure: Core Web Vitals as ranking, Discover, and timeout

Open PageSpeed Insights on a competitor. Poor LCP, a sluggish INP, a layout that jumps while the hero loads: this is still the common case on mobile, on desktop, in retail and in publishing.

A homepage that takes five seconds on an iPhone over 4G loses the reader before the offer. A cart button that waits half a second loses the click. Google's crawler records the same delay. An agent with a budget of milliseconds will not wait. It will fetch the next candidate.

Core Web Vitals are part of the Page Experience signals. Content and relevance still come first. When two pages are equal in substance, performance is the tie-breaker. In a competitive niche that gap is the difference between a position that receives traffic and one that does not.

The work at Glorics is not to make a slow stack look fast. It is to build sites in which speed is a property of the architecture.

LCP under 2.5s, INP under 200ms, CLS under 0.1.

01Three field metrics

LCP is the time until the largest visible element paints: the hero, the headline, the dominant block. Beyond four seconds Google reports a poor experience. Studies of bounce against load time have put the share of people who leave at five seconds in the high thirties. Treat the exact percentage as a range, not a law. The direction is not in dispute.

INP is responsiveness across the session, not only the first tap. It replaced First Input Delay in 2024 for that reason. Google's threshold is 200 milliseconds.

CLS is visual stability. A button that moves because an advert or an image without dimensions arrived late is the classic failure. It is also the failure users remember.

A system that has to complete a purchase needs the control to respond inside that 200ms window. A system that has to extract the main content needs it on screen inside 2.5 seconds. Latency is not a nuance. It is a filter.

02Discover is not search

Google Discover is recommendation. The product chooses to show a URL to someone who did not query it. The traffic can be large. Eligibility, as Google documents it, requires passing Core Web Vitals. Poor LCP, INP or CLS is not a ranking haircut. It is exclusion. The piece, however good, does not enter the stream.

03Speed and conversion

The conversion literature around delay is old and often loosely cited. The pattern is stable: extra hundreds of milliseconds cost completions; a page that paints in two seconds keeps more of the session than a page that paints in five. The arithmetic below is an illustration, not a measurement from a named shop.

An agent at checkout has a timeout. If the endpoint does not answer inside it, the transaction is cancelled. There is no second visit tomorrow. The protocol is binary.

04The structural handicap

WordPress still powers a large share of the web. Shopify runs millions of stores. Both are capable platforms. On Core Web Vitals they start behind, because of how they ship JavaScript.

Each plugin adds a script: SEO, commerce, the theme slider, chat, a pixel. The main thread is busy executing instead of painting. Shopify's Liquid is compiled, but third-party apps still stack in the head. The result is the same.

The platforms are not the enemy. Client-side rendering is: an empty HTML shell that must run megabytes of JavaScript before a reader, a crawler or an agent can see the document. What those systems want is the opposite. HTML already rendered, immediately readable, with no script that is not doing work on this page.

05HTML first, islands where needed

Glorics sites are rendered on the server as HTML. There is no client framework on the critical path, no virtual DOM for the article, no runtime required to read the page. The browser paints what it received.

Where a page needs a form, a control, an instrument, we load islands: only that component's JavaScript, and only when it is visible. The rest of the document stays HTML.

A typical WordPress page on mobile 4G still spends seconds parsing script before the largest element paints. A Glorics page is dominated by time to first byte, not by parse, because there is almost nothing to parse. Those figures are the architecture, not a tuning pass.

06Speed in service of the graph

A fast empty page is still empty. A Knowledge Graph on a slow page is a graph nobody fetches. The same response that serves the HTML injects the JSON-LD built in the Entity Graph Builder: @graph for Organization, Person, Product, FAQPage, linked by stable @id and, where it exists, Wikidata. One request. Pre-rendered markup and the node. An agent does not need a second round trip.

07What does not copy

Any shop can compress images, minify CSS and lazy-load scripts. The gains last until the next plugin, the next tag, the next theme update.

What does not copy is an architecture that does not generate that debt. JSON-LD is text in the head. It does not delay paint, shift layout, or block the thread. Speed here is not a purchase. It is a property of the stack.

What to remember

If the largest element does not paint inside Google's window, the page is already weaker in ranking, weaker in Discover, and weaker as a fetch. That is the first filter. Content still matters. It never gets read if the document does not arrive.