LCP
≤ 2.5sIAN DIKHTIAR / RESEARCHTHE WEB IS A SERVICE2026
A field note for owners who need the site to pull its weight
A website
has a job.
Not “look impressive.” Not “rank somehow.” A website should help the right person understand, trust, and complete the next useful step.
Read the assignmentTHE WORK IS A JOURNEY
question→confidence→action
01Can I find myself here?02Can I believe this?03Can I finish?
01
THE JOB
THE JOB
Start with the person, not the page
A site is a
working surface.
The best website is not the one that says the most. It is the one that removes the right uncertainty at the right moment.
Every visitor arrives with a question. Is this for a business like mine? Can these people solve the problem? Is the next step safe, worth the effort, and likely to go somewhere? A visual identity can earn attention, but the service has to carry the person through the question.
GOV.UK’s service guidance uses a useful standard: people should be able to complete what they came to do, from start to finish, with as few unnecessary steps as possible. It explicitly includes the online and offline parts of the service, the devices people use, and the support they may need later. [6] That framing applies to a local firm, a B2B offer, a portal, or a product landing page.
It also changes the owner’s brief. “Make it beautiful” becomes “make the important decision easier.” The page can still be expressive; its expression now has a job.
THE OWNER’S BRIEFOne page. One audience. One next useful action.
02
THE EVIDENCE
THE EVIDENCE
Four constraints, no magic score
Good experiences
leave signals.
The web has shared measures for parts of the job. They are useful because they turn vague complaints into specific questions. They are limited because no metric knows whether the promise is relevant.
INP
≤ 200msCLS
≤ 0.1These are field metrics, not a single page-speed grade. Google classifies a page or origin using the 75th percentile of page views; a lab run on one laptop cannot stand in for the real audience. [2]
WHAT THE WEB ALMANAC ADDS
HTTP Archive’s 2025 analysis uses a July 2025 dataset spanning millions of websites, combining controlled page tests with Chrome real-user data. It describes a broad population, not the audience of a particular business. Its performance chapter treats loading, responsiveness, and visual stability as different signals; its accessibility chapter shows why automated checks are useful patterns rather than a complete human review. [4][5]
03
THE JOURNEY
THE JOURNEY
Turn the metric into a moment
Design the
decision path.
A website earns its keep when its promises, evidence, interaction, and handoff line up. The visible page is one layer of a service that continues after the visitor clicks.
01Arrive
“Am I in the right place?”
→02Orient
“What happens here?”
→03Trust
“Why should I believe it?”
→04Act
“Can I finish cleanly?”
Match the intent.
A search result, referral, or direct visit carries context. The page should confirm the audience and problem before it asks for attention.
Show the reason.
Proof can be a specific process, a real example, a named person, or a clear boundary. It should answer the doubt that blocks the next step.
Make the handoff real.
Forms, checkout, calendars, and portal links are part of the product. The visitor should know what happens after the action and who owns it.
The recommendation here is a synthesis: the sources describe measurable performance, accessibility standards, and end-to-end service design; the sequence above is XT3’s practical way to join those constraints for a business website. It is not a measured conversion funnel. [3][6][7]
04
THE AUDIT
THE AUDIT
A working review, not a vibe check
Give the site
a shift to work.
Use these prompts with a page, an actual task, and a real device. The checkboxes are local to this report: they save nothing and do not produce a score.
THE FASTEST USEFUL REVIEWChoose one high-value journey and follow it on a slow phone.
Write down the first question, the first doubt, the first delay, and the handoff after completion. Fix the obstruction that changes the finished outcome.
Make the next step easier
A website can be
beautiful and useful.
Ian helps business owners turn a page, portal, or customer journey into a dependable working surface: clear promise, credible proof, accessible interaction, and a handoff that someone owns.
05
SOURCES
SOURCES
Sources & methodology
Follow the
working evidence.
This report was researched September 8, 2026. It combines standards, official documentation, service guidance, and the HTTP Archive’s published analysis. It does not include a new survey or claim conversion lifts, revenue effects, or client performance.
Thresholds are reproduced with their units and percentile caveat. The journey, audit prompts, and owner recommendations are XT3’s synthesis. Accessibility remains a human and task concern even where automated tools report a pass.
Download the threshold data (CSV) ↓
- [1]Understanding Core Web Vitals and Google search results ↗
Google Search Central · Updated December 10, 2025
Google’s current reference for LCP, INP, and CLS. It recommends these thresholds for a good user experience and says they align with search page-experience systems; it does not promise a ranking or conversion result.
- [2]How the Core Web Vitals metrics thresholds were defined ↗
Google web.dev · Updated May 7, 2025
Explains the research and 75th-percentile method behind the thresholds. The page distinguishes user-perceived loading, responsiveness, and visual stability instead of treating “speed” as one number.
- [3]Web Content Accessibility Guidelines (WCAG) 2.2 ↗
W3C Web Accessibility Initiative · Recommendation published October 5, 2023
The web standard’s testable success criteria for accessible content across devices. Conformance is a structured target, not a guarantee that every person’s needs are met.
- [4]Performance · The 2025 Web Almanac ↗
HTTP Archive · Published January 15, 2026; July 2025 dataset
Analysis of HTTP Archive and Chrome UX Report data. The chapter combines controlled measurements and Chrome real-user data across millions of websites; it is a population-level view, not a benchmark for one site.
- [5]Accessibility · The 2025 Web Almanac ↗
HTTP Archive · Published January 15, 2026; July 2025 dataset
Large-scale Lighthouse and axe-core analysis with methodological caveats. Automated checks expose patterns and omissions; they do not replace a keyboard, screen-reader, or task test.
- [6]Make the service simple to use ↗
Government Digital Service · GOV.UK · Published May 8, 2019; standard updated May 30, 2022
Service Standard guidance to test the whole experience, support first-time completion, work across devices, and keep the service consistent from start to finish.
- [7]Designing good government services: an introduction ↗
Government Digital Service · GOV.UK · Updated December 7, 2023
A service-design reference that treats the journey from beginning to end and front to back, including internal processes and aftercare, as part of the user experience.