Performance and reliability · fixed-price first step
Performance and Core Web Vitals audit
A fixed-price audit of one web application: server response times, database queries, caching, infrastructure and front-end Core Web Vitals (LCP, INP and CLS). You get a written report with each problem measured, its cause and a fix, ranked by impact and effort. The first fixes are often small.
- Timeline
- Agreed per project
- Price
- Fixed price
- Engagement
- Fixed-price
Is it a fit?
For
- SaaS and e-commerce teams whose pages or APIs feel slow, and whose conversion rates show it
- Sites failing Core Web Vitals in Google Search Console
- Teams about to pay for bigger servers without knowing where the time goes
Not for
- Sites without real traffic yet: there's nothing real to measure
- Teams who want fixes without a report: that's a retainer, not an audit
What you get
- Measurements of the pages and endpoints that matter, from real-user data where available
- Profiling of the slowest requests, down to queries and code paths
- A ranked list of fixes with expected impact, effort and risk
- Core Web Vitals findings for mobile and desktop
- A walkthrough of the report with your team
How it runs
- 01
Day 1: access and baselines
Read access to the code, the database's slow-query log and your analytics; baseline measurements of the key journeys.
- 02
Days 2 to 4: profile and trace
Follow the slowest requests through every layer, from the browser and CDN to the application, queries and infrastructure.
- 03
Day 5: report and walkthrough
The written report, then a call with your team to go through it and answer questions.
Typical stack: Lighthouse · Chrome DevTools · WebPageTest · Search Console · Blackfire · New Relic · EXPLAIN · Redis
Questions
What access do you need?
Read access to the repository, the database's slow-query log or a read replica, your analytics or Search Console, and your monitoring tool if you have one. An NDA covers it all if you'd like one.
Will you fix the problems too?
The audit ends with the report. Most teams then ask me to implement the top fixes, as a fixed-scope follow-up or on a retainer.
Which Core Web Vitals targets do you aim for?
Google's "good" thresholds at the 75th percentile of real users, for Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, on mobile first.
Sources
More in performance and reliability
- Launch-day readiness: Your biggest day shouldn't be your first real load test.
- Cloud, DevOps and cost: Deployments you don't dread, backups you've actually tested, and a cloud bill that makes sense.
Tell me about your project.
A short brief is enough to start. I’ll reply with questions, a suggested first step and when I could begin.