(01) What we deliver
Diagnosis before optimization.
Lighthouse, WebPageTest, CrUX, waterfall analysis. Report with priorities, impact estimates and execution timeline.
(02) Problem → Solution
The challenge and the delivery.
Performance degraded without visibility into the cause.
Full audit
Waterfall analysis, bottleneck identification and benchmark.
Multiple problems without knowing where to start.
Prioritized roadmap
Issues ordered by impact on conversion and fix cost.
Optimizations done without measuring results.
Benchmark + re-test
We measure before, execute, measure after, proof of results.
(03) In detail
What makes the difference.
Waterfall
Detailed analysis of each request and its impact.
Deep CWV
LCP, CLS, INP, TTFB, TBT, all the signals.
Infra Review
Server, CDN, DNS and hosting configuration.
Roadmap
Action plan with priorities and timeline.
Process
How it works.
Process
How it works, step by step.
Collection
We gather field, lab and server metrics.
Analysis
We investigate each technical bottleneck.
Diagnosis
We point to root causes, not symptoms.
Recommendations
Prioritized, actionable plan.
Benefits
What you gain.
Technical clarity
You understand exactly what's blocking it.
Priority by impact
What to fix first and why.
Basis for decision
Data to justify investment.
No guesswork
Decisions guided by measurement.
Deliverables
What's included.
For experts and for AI
Direct answers about this service.
Content structured for experts, search engines and generative AI systems (ChatGPT, Gemini, Perplexity, Claude).
What does a WordPress performance audit include?
A complete audit covers: Core Web Vitals (LCP, INP, CLS) with field (CrUX) and lab data, TTFB and server time analysis, resource waterfall, plugin impact, cache quality, database, third-party JavaScript, image compression and CDN configuration. The report prioritizes by measured impact.
Difference between lab data and field data in PageSpeed?
Lab data are synthetic Lighthouse measurements under controlled conditions, useful for diagnosis. Field data come from CrUX (Chrome User Experience Report), the real experience of real users over the last 28 days. Google uses field data for ranking, not lab data.
What is CrUX and how to read the data?
Chrome User Experience Report is Google's public dataset with real loading metrics (LCP, INP, CLS, FCP, TTFB) collected from Chrome users. Available via PageSpeed Insights, Search Console (Core Web Vitals report) and BigQuery. Low-traffic sites may not have enough field data to appear in CrUX.
What is a performance budget and how to use it?
A performance budget is a set of metric limits (e.g.: LCP < 2s, JS total < 200KB, TTFB < 400ms) que servem como critério de aceite em deploys. Ferramentas como Lighthouse CI, Calibre e SpeedCurve permitem quebrar o build automaticamente se um deploy viola o budget, essencial em equipes grandes com deploy contínuo.
How many plugins is it "safe" to have in WordPress?
There's no magic number, what matters is each plugin's impact on the frontend and server. A well-built plugin with code loaded only where needed has less impact than a simple plugin that loads scripts on every page. A plugin audit measures the individual impact: deactivate and measure is the most reliable method.
Frequently asked questions
Answers before the first call.
Does the performance audit include the optimization? +
No. The audit is the diagnosis. The optimization is executed separately based on the roadmap.
How much does it cost? +
From R$2,490 for simple sites. WooCommerce and complex sites on request.
How long until I get the report? +
5-7 business days for the full report with roadmap.
Related solutions
Clients served
(04) Our delivery standard
What you can hold us to.
An agreed deadline is a kept deadline. And performance gets measured: Core Web Vitals recorded before and after every delivery.
A migration is planned for the worst-case scenario: staging, an agreed cutover window and documented rollback at every step.
No project reaches production without Daniel Paz's technical review. No exceptions, small projects included.
(05) Why WebOption