A site’s speed isn’t a technical detail reserved for developers: it’s the first visible sign of the care put into building it. A site that appears all at once, with no jolts, no text jumping under your finger, tells your visitor they’re dealing with someone serious, before they’ve read a single line. A slow site says the opposite. Google has set public thresholds to measure all this, the Core Web Vitals, and at Inleven we hold them on every delivery. Here’s what they measure, and above all, what slowness says about you.
What does a slow site say about your business?
A slow site sends a message you didn’t choose: “here, we did it as fast and cheap as possible, without looking at the result.” The visitor doesn’t put it into words consciously. They just feel a vague irritation, a page that lags, a button that slips away at the moment of the click, an image that pushes the text down while they’re reading. And they leave, without knowing why, keeping a faint impression that “it just didn’t feel right.”
This is all the more true in 2026. Producing a site has become trivial: a tool generates a page in thirty seconds, and it shows. The web fills up with sites that look fine, heavy in reality, stuffed with useless scripts, never reviewed. Slop. In that landscape, a site that responds instantly is no longer just pleasant, it’s rare. It signals a human hand behind it, someone who measured, trimmed, refused the superfluous. Speed has become proof of care, because care has become the exception.
What are the 3 Core Web Vitals thresholds?
The Core Web Vitals are three measures defined by Google to quantify the experience quality of a real page, on real devices. Three public thresholds, worth knowing:
- LCP (Largest Contentful Paint): under 2.5 seconds. The time it takes for the largest visible element (often your title or your main image) to appear. It’s the answer to the question “when do I finally see something useful?”.
- INP (Interaction to Next Paint): under 200 milliseconds. The delay between the moment you click or tap and the moment the page visibly reacts. It’s the sense of responsiveness, the “it responds to the touch.” This metric replaced the old FID in early 2024.
- CLS (Cumulative Layout Shift): under 0.1. Visual stability. The lower it is, the less the content moves during loading. A high CLS is the button that slides half a second before you press, and the finger that misses.
Google uses these three measures as a ranking signal, and surfaces them in Search Console based on your users’ real visits. These aren’t lab scores: it’s what people actually experience on your site, aggregated over twenty-eight days.
Why isn’t hitting the threshold enough?
Slipping just under the bar avoids the penalty. That’s not the same as offering a good experience. An LCP at 2.4 seconds is “green” by Google’s standard, but 2.4 seconds of waiting, on mobile, on 4G, you still feel it.
The gap between “compliant” and “instant” is exactly where the perception of quality plays out. And that’s where most sites give up: they aim for the regulatory minimum, because going lower demands work the automatic tools won’t do for you. That work is precisely what sets a site that’s designed apart from a site that’s assembled.
How does Inleven hold these thresholds, concretely?
Not by magic, nor by ticking an “optimize” box in a builder. Through architecture choices made on day one, and held through to delivery. Here’s the detail, because a demanding professional has the right to know how.
A performance budget set before the first line is written. We decide in advance on a page’s maximum weight, the number of scripts tolerated, the size of images. That budget becomes a design constraint, not a last-minute check. If a feature blows the budget, we find another way to do it, or we drop it.
Static, by default. Our sites are compiled into HTML pages served as-is, with no database to query or server to wake on every visit. The browser receives content ready to display. It’s the fastest base there is, and the one that breaks down the least.
Interactive islands, not interactive pages. When part of the page needs JavaScript (an animation, a form), we hydrate only that piece, and only when it becomes visible on screen. The rest of the page stays pure HTML. The result: the browser runs almost nothing on load, which keeps blocking time at zero.
Images processed by Sharp. Each image is resized, recompressed, and served in the right format for the device. A photo that would weigh two megabytes straight out of the camera drops to a few dozen kilobytes, with no visible loss. It’s one of the most rewarding levers on LCP.
Zero shift on the title. The H1 and the top-of-page subtitle are real HTML text, rendered immediately, never hidden then revealed by an animation. The dimensions of images and blocks are reserved before loading, so nothing pushes anything. That’s what gives us a CLS of 0, and not “close to 0.”
The numbers this produces, on our real deliveries: an LCP between 2.0 and 2.4 seconds on mobile, a CLS at 0, a blocking time (TBT) at 0 milliseconds, a Lighthouse performance score between 96 and 99, and an accessibility score of 100 out of 100. That last point counts as much as the others: a fast but screen-reader-unreadable site is not a site built with care.
Speed is the measurable version of care
In an era where anyone can produce a site in a few minutes, what sets you apart is no longer having a site, but having one that holds up under the weight of the detail. Speed is the part of that detail a machine can measure. It doesn’t lie. You can’t fake it with a pretty visual or make up for it with a slogan.
That’s why we treat it as a deliverable in its own right, on the same footing as design. AI helps us move fast in the making, but a human decides what we keep and what we throw out, and it’s that decision that makes the difference between a site that breathes and a site that drags. You can see the detail of how we work on the Method page, and exactly what we build in our services. And because a site built with care is also a site that belongs to you, everything we deliver (domain, content, code) stays yours from day one: it’s explained on the Guarantees page. And if you’d like to talk it over, we’re happy to discuss it via the Contact page.
