Measure the bottleneck before changing code

Core Web Vitals and Website Performance

I investigate slow websites with production measurements and browser traces, then fix the parts of the stack that the evidence identifies. The work can cover frontend assets, rendering, caching, data requests, and server response time.

Start with field and lab evidence

Search Console and CrUX can show how real visits perform when enough field data exists. Browser traces and Lighthouse help reproduce problems under controlled conditions. I use both where available because a single lab score does not describe every device, route, or visit.

Trace loading and rendering

The investigation can cover the largest content element, interaction delay, layout shifts, JavaScript execution, image sizing, fonts, third-party scripts, request chains, hydration, API calls, and cache behavior. Each proposed fix should point back to a measured bottleneck.

Verify changes against important routes

A homepage improvement can leave a lead form or application route slow. Verification includes representative templates, mobile conditions, warm and cold cache behavior, and regression checks for content, analytics, and accessibility.

Document remaining constraints

Some costs come from third-party tools, CMS response time, hosting configuration, or required functionality. The final report records what changed, the before-and-after evidence, and the constraints that remain instead of promising a perfect score.

Related services and work

Continue with the service or project context that best matches your next decision.

Performance Optimization questions

What is included in a website performance audit?

The scope can include field data, browser traces, Core Web Vitals, JavaScript, images, fonts, rendering, caching, third-party scripts, API timing, and server response time.

Can you improve an existing Next.js website?

Yes. Work can include rendering strategy, data fetching, bundle review, images, fonts, caching, third-party scripts, route-level testing, and deployment configuration.

Do you guarantee a Lighthouse score?

No. Scores vary with the page, device, network, content, third-party scripts, and test conditions. I report measured improvements and remaining constraints.

Does better performance guarantee higher rankings?

No. Performance can support page experience and crawling, but search visibility also depends on relevance, competition, content, reputation, and other systems.