Performance optimisation
Optimise the customer task, then protect it from regression.
The dashboard says the site is slow. Before funding a rebuild, we need to know which customers are affected, which task suffers and whether the delay sits in the network, page, browser or application.
Performance optimisation is a diagnosis and control discipline. It can involve images, fonts, JavaScript, HTML, caching, database queries, third-party services or product design. The result we aim for is a customer journey that responds within an agreed budget and stays there as the product changes.
We begin with evidence from the real route and finish with a regression guard. Otherwise the same weight returns a few releases later.
A useful performance goal names the customer task
“Make the website faster” is too broad to estimate or accept. A visitor reading an article, an editor saving a page and a customer completing checkout exercise different systems.
We choose a small set of journeys tied to commercial or operational value: see the primary product content, filter a catalogue, add to basket, submit an enquiry or open a daily dashboard. Each gets a device, network condition, geography and timing budget.
This prevents easy work on an already-fast landing page from masking a slow conversion path. It also gives product decisions a cost. A new review widget may be valuable enough to consume part of the interaction budget, but that trade should be visible before release.
Synthetic scores help compare builds. The acceptance remains a human task on the environment customers use.
Field data and laboratory tests answer different questions
Chrome User Experience Report data reflects eligible real Chrome visits over time. It can reveal device and connection diversity that a developer machine misses. It is historical and may not identify which line of code caused the change.
Lab tools such as Lighthouse run a controlled page load. They are repeatable, rich in diagnostics and useful in development. They cannot reproduce every interaction, login state, browser extension or customer journey.
Google’s Core Web Vitals workflow recommends using field tools to find affected pages and lab tools to diagnose reproducible problems. We follow that split. If public field data is unavailable for a smaller site, consent-aware real-user measurement and server timings can provide product-specific evidence.
One number should not merge field and lab results. We record source, date, URL group and percentile so the comparison stays fair.
Largest Contentful Paint crosses the full delivery path
Largest Contentful Paint measures when the largest relevant content element becomes visible. A slow server can delay it, but so can redirect chains, render-blocking CSS, a late-discovered hero image, font behaviour or client-side rendering.
We break LCP into stages: initial server response, resource discovery, resource download and render delay. The fix follows the largest part. A CDN may reduce delivery time for a cacheable image; it cannot make a hidden image discoverable earlier if JavaScript inserts it after startup.
Priority hints and preloads are used sparingly and confirmed in the network waterfall. Marking every asset high priority forces the browser to choose among competing claims.
WordPress and commerce sites are tested with realistic content. A carefully cropped demonstration image is weak evidence for templates that editors will fill with large uploads.
Interaction to Next Paint exposes main-thread competition
Interaction to Next Paint measures responsiveness across a page’s observed interactions. The current “good” threshold is 200 milliseconds at the 75th percentile, according to Google’s Core Web Vitals thresholds. That classification is useful, but the product still needs to identify which interaction is slow.
Long JavaScript tasks, large component updates, synchronous storage, third-party scripts and expensive layout can all delay visual feedback. Reducing the initial bundle helps only if downloaded code was the competing work.
We profile the specific click, keypress or tap and preserve user feedback while longer work continues. Sometimes the best optimisation is product design: process fewer rows, postpone a non-essential calculation or move work off the main thread.
Framework optimisation begins after evidence. Blanket memoisation and code splitting can add complexity while leaving the customer-visible delay untouched.
Layout stability depends on content and component rules
Cumulative Layout Shift captures unexpected movement while the page is visible. Images without reserved dimensions, late banners, font swaps and components inserted above existing content are common causes.
The repair is often a design-system rule rather than a one-page patch. Media components reserve aspect ratio. Notices have a planned slot. Loading placeholders match the eventual content. Ad and embed areas declare sensible bounds.
Editors and marketing tools are part of the system. A template can pass in development and shift after a consent banner, campaign embed or uncropped image enters production. Monitoring representative page types catches that operating reality.
User-initiated changes can be expected, so zero movement is the wrong target. The useful distinction is whether the interface moves without the customer asking it to.
Server and database delay need their own trace
When time to first byte is poor, frontend changes have limited room to help. The request may be waiting for application boot, database queries, an external API, file storage, locks or an exhausted worker pool.
We trace a representative slow request through Nginx, application and database, retaining a request identifier. Median latency alone can hide the customers who experience a timeout; higher percentiles and error rates show the tail.
Caching is considered after correctness. Full-page caching can transform public content, while logged-in dashboards and baskets require safer keys and invalidation. Query and application work still matter on every miss.
Capacity and code are tested separately. More server resource can buy time, but it does not repair an unbounded query or downstream call with no timeout.
A performance budget belongs in the release process
One optimisation project decays as images, packages and third parties return. We turn the chosen measurements into release constraints: maximum critical image weight, JavaScript budget, server latency for a key API, or a lab threshold on representative templates.
Budgets need tolerances and an exception process. A test that fails randomly will be ignored; a test that permits every exception will do the same. We establish a stable baseline, alert on material regression and require the feature owner to explain the trade.
Field monitoring then checks whether controlled tests predicted customer experience. A release can pass the lab and still encounter a slow geography, device or external service. Server monitoring and browser evidence meet at the user journey.
Questions to answer before funding performance work
- “Which customer task is too slow, and what is the business effect?” Prioritise a route, not a score.
- “Is the evidence field data, a lab test or a support report?” Keep the sources distinct.
- “Which device, connection and geography represent the affected users?” Test that constraint.
- “Where is the time spent across server, network and browser?” Profile before choosing the fix.
- “Which third parties and editorial choices can alter the result?” Include operating content.
- “What measurable budget will this work achieve?” Define acceptance before implementation.
- “Which check will stop the regression returning?” Make performance part of release.
When a performance programme is worth the investment
Fund the work when slow tasks affect conversion, retention, accessibility, search visibility or staff throughput and evidence can isolate the constraint. The highest-value fixes often improve several outcomes at once: smaller images reduce bandwidth and LCP; less main-thread work helps responsiveness and battery use.
The programme is credible when it includes measurement after release and a prevention mechanism. It leaves the product team able to see the next regression without commissioning another broad audit.
When optimisation is becoming score theatre
Do not rebuild a functioning product to chase a perfect lab number without evidence that customers suffer. Use the smallest intervention that improves the important journey within its budget.
Avoid comparing unrelated URLs or competitor scores as if they shared audience, content and infrastructure. Public tools are useful prompts, but they do not make a commercial case on their own.
Stop adding infrastructure when the delay is product work in the browser, or trimming frontend bytes when an uncached database request dominates. The measurement should decide which team acts.
Optimise a real customer task and leave a budget behind.
I do not sell a page-speed score as the outcome. I want field evidence where it exists, a repeatable lab case and a profile showing where the time goes. Once the important journey meets its budget, I put the check into delivery so the business does not buy the same improvement twice.
Alexander De Sousa · Founder, Digital Royalty · LinkedIn
What turns website speed work into a controlled product decision
Field experience finds the affected customers; laboratory and profiling tools find causes. A release budget protects the value after the first repair.
The performance commitment in six decisions
- Decision unit
- A named customer task on a representative route, device, connection and region, rather than a site-wide score without context.
- Customer effect
- Earlier useful content, faster interaction and stable layout where the work is tied to lived journeys rather than easy demonstration pages.
- Adoption cost
- Low for measurement and focused fixes; higher when architecture, third parties, content workflow or slow backend design must change.
- Ongoing owner
- Product and engineering teams jointly responsible for budgets, third-party cost, template behaviour, field alerts and justified release exceptions.
- Failure mode
- A one-off score improvement regresses as assets and scripts return, or work moves a metric without improving the customer task.
- Proof required
- Before-and-after evidence on the same journey, a diagnostic trace or profile, and a stable automated or field regression signal.
Measurement routes to use for different performance questions
-
Public Chrome field data
Right when: An eligible public origin or URL has enough real Chrome traffic to reveal device and connection experience over time.
Watch for: CrUX is aggregated and historical; it may not identify a recent release or a specific product interaction.
-
Product real-user monitoring
Right when: The team needs route, release or customer-segment evidence beyond public datasets and can collect it with appropriate consent and sampling.
Watch for: Protect privacy, record attribution context and control telemetry volume before turning browser observations into a data product.
-
Repeatable lab and CI tests
Right when: Developers need diagnostics and a stable comparison between builds before code reaches customers.
Watch for: A simulated load cannot represent every device, interaction or production dependency; keep lab and field results labelled.
-
Targeted browser and server profiling
Right when: A repeatable slow task needs its main-thread, network or backend cause located before implementation is estimated.
Watch for: Profile production-style builds and data; development mode and empty fixtures can point at work customers never experience.
Research behind this performance position
-
Official metric guidance
Core Web Vitals thresholds
Defines LCP, INP and CLS thresholds at the 75th percentile and explains the methodology behind the current classifications.
-
Official workflow
Core Web Vitals workflows with Google tools
Separates field discovery from laboratory diagnosis and shows why several tools are needed for a reliable performance investigation.
-
Official field dataset
Chrome UX Report documentation
Explains the real-user dataset, eligibility and aggregation that determine which conclusions public field data can support.
-
Official implementation
GoogleChrome web-vitals library
Provides a small reference implementation for measuring current Web Vitals in real pages, subject to the product's consent and attribution design.
-
Public web dataset
HTTP Archive 2025 performance chapter
Gives broad evidence about page weight, metrics and web performance patterns; it supplies context rather than a diagnosis of one site.
-
Official diagnostics
Chrome DevTools Performance panel
Documents main-thread, rendering and network analysis used to connect a slow interaction to work in the browser.
-
Practitioner discussion
Stack Overflow: field and lab layout-shift differences
The question reflects a common attempt to reconcile unlike datasets. The tool documentation should define what each number represents.
-
Community experience
Reddit: a frontend release performance checklist
Developers describe CI limits and monitoring approaches. The thread is anecdotal and useful for implementation ideas rather than target thresholds.
Tell us what you need
A few quick questions, then a straight answer from a real person — usually within a few hours.
What happens next
- 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
- 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
- 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.
Tell us what you're working on
Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.