Website Performance Testing for Digital Agencies

Web performance is increasingly a core agency deliverable. Clients are more aware of Core Web Vitals as an SEO factor, and agencies that build fast sites differentiate themselves from those that don’t. Here’s how to make performance testing a repeatable, client-facing practice.

The Agency Performance Workflow

1. New Client Audit

The first step with any new client is establishing a baseline. Run their site through debugutils.dev immediately — it takes 2 minutes and gives you:

• Current Lighthouse Performance score
• LCP, CLS, INP with Good/Needs improvement/Poor ratings
• CrUX field data (real user performance)
• Full request waterfall
• Prioritized list of improvements with estimated time savings

Share the report URL with the client as part of your initial audit document. For tips on presenting results, see How to Share Speed Reports with Clients. A visual, interactive report is more compelling than a written summary of numbers.

Look at their CrUX field data — this is what Google actually uses for ranking decisions, and clients respond to “your Core Web Vitals are failing, which is hurting your Google rankings” more than “your Lighthouse score is 45.”

2. Competitive Benchmarking

Run the same tests on 2–3 competitor sites. If the client’s site scores 40 and their top competitor scores 85, the performance gap becomes a clear business problem.

Use the shareable URLs from each test to create a visual comparison in your proposal or audit document.

3. Pre-Launch Testing

Before every site launch, performance should be part of the QA checklist. Run tests on the staging environment and against your target thresholds before going live. Our pre-deploy performance checklist covers this in detail.

Checklist items:

• Lighthouse Performance score ≥ 70 (mobile)
• LCP < 2.5s
• CLS < 0.1
• INP < 200ms (check by using the page manually)
• No render-blocking resources on critical pages
• Images in WebP/AVIF format with explicit dimensions
• Fonts preloaded and using appropriate font-display

If the site fails, that’s a production issue to fix before launch — not after.

4. Post-Launch Monitoring

For ongoing retainer clients, include a monthly performance check. Run tests on key pages, compare to last month’s baseline, and flag regressions. If the client added a new plugin or third-party script that hurt performance, catch it before it affects rankings.

Incorporating Performance into Client Proposals

Frame it around SEO and revenue. Clients fund work that produces results. Connect performance to outcomes they care about:

• “Your Core Web Vitals are currently failing — this is a direct ranking factor since 2021”
• “Your LCP is 4.8s — studies show 7% conversion loss per second of delay” (see Core Web Vitals for E-commerce for more data)
• “Your competitor scores 82, you score 41 — we can close that gap”

Scope performance improvements explicitly. Don’t let performance be an afterthought. Add explicit line items: performance audit, image optimization, caching setup, Core Web Vitals remediation.

Set measurable targets. “We’ll bring your LCP from 4.8s to under 2.5s” is a concrete commitment that’s easy to verify and invoice against.

Common Agency Mistakes

Testing only on desktop. Most clients have majority mobile traffic. Always test on simulated mobile (which debugutils.dev does by default).

Only testing the homepage. The homepage is usually the most optimized. Test product pages, blog posts, and landing pages — these often have the worst performance.

Ignoring CrUX. Lab scores are useful for before/after comparison, but Google uses real user field data. If your client’s CrUX data shows poor Core Web Vitals, that’s the problem to fix.

Forgetting about third-party scripts. Marketing teams add tracking pixels, chat widgets, and analytics scripts constantly. One third-party script can add 400ms of TBT. Audit regularly.

Pricing Performance Work

Performance optimization is specialized work — price it accordingly. A full performance audit (baseline testing, competitor comparison, detailed recommendations) is a deliverable worth $500–2000 depending on site complexity.

Ongoing performance monitoring and remediation fits naturally into a technical retainer: 2–4 hours/month of testing, reporting, and optimization work.

Run your reports on debugutils.dev — the shareable URLs make it easy to deliver professional results without building your own tooling. For a full overview of available tools, see Best Website Speed Test Tools.