Slow main content
Hero images and fonts, render-blocking CSS and JS, server response time and caching.
Performance engineering services
Epsilon Delta Wizard is a performance engineering service. Our engineers baseline your site, fix what slows it down and report the measured gain. Fixed term, fixed cost, and every gain measured on real users.
LCP p75 so far
Engineer's note · Hero image preloaded and two tag scripts deferred. LCP is already past the 30% target.
How it works
Every engagement has a fixed term and a fixed cost, agreed before we start. You always know what is being worked on and what it has changed.
Week 1
We record real-user Core Web Vitals for your key pages with Gemini, or Orion for apps, then audit the code, scripts, images, fonts and servers behind them.
You get Baseline report and a fix list ranked by impact
Weeks 2–4
Our engineers work with your team on the biggest wins first, through pull requests or pairing, and check each change against the baseline as it ships.
You get Shipped changes, each with its measured effect
Week 5
We compare the same pages and the same real-user metrics with week 1, so the gain is measured, not estimated.
You get Impact report: before, after and what drove it
After
Complimentary follow-up support and long-term coaching, so new releases keep the speed you paid for.
You get Guardrails and alerts for future releases
We start where real users feel it most: the slowest metric on the pages with the most traffic.
Hero images and fonts, render-blocking CSS and JS, server response time and caching.
Long main-thread tasks, heavy third-party and tag-manager scripts, costly re-renders.
Images, ads and banners without reserved space, late fonts and injected content.
CDN and cache rules, redirects, backend calls and edge rendering.
Bundle size, unused code, hydration cost and script loading order.
Cold start, screen load, jank and API time on Android, iOS and Flutter, measured with Orion.
Impact report
Real-user p75 values for the same pages, before and after. These numbers are a sample, not a customer result.
| Metric | Baseline | After | Change |
|---|---|---|---|
| LCP p75 | 3.6 s | 2.2 s | ▼ 39% |
| INP p75 | 340 ms | 190 ms | ▼ 44% |
| CLS p75 | 0.21 | 0.06 | ▼ 71% |
| TBT | 820 ms | 410 ms | ▼ 50% |
| Gemini Score | 58 | 81 | ▲ 23 pts |
Insight · Two changes delivered 70% of the gain. They shipped in week 2.
A faster site that delights users and passes Core Web Vitals, which Google uses in search ranking.
Faster pages lift engagement and conversions. A fixed cost means you know the price before the gain.
Complimentary support and long-term coaching after the engagement, so the gains last.
*[Confirm the terms of the 30% commitment: which metric, which pages, and how it is measured.]
| Capability | Wizard | Lighthouse or PageSpeed report | One-off consultant audit |
|---|---|---|---|
| Based on | Real users on your site | One simulated load in a lab | Usually lab tests |
| Fixes implemented | Yes, with your team | No, a list of suggestions | Sometimes, billed by the hour |
| Gain measured | Before and after, on real users | Lab score only | Often not measured |
| Cost | Fixed, agreed up front | Free | Usually time and materials |
| After the project | Coaching, support and alerts | None | New engagement needed |
Lighthouse and PageSpeed Insights are useful lab tools; we use them too, alongside real-user data.
Engineers who find what makes your site slow for real users, fix it with your team and measure the result. Wizard does all three in a fixed term at a fixed cost.
A typical engagement is five weeks: one week to audit and baseline, three to implement fixes and one to report the impact. [Confirm typical range for larger sites.]
With real-user p75 values for the same pages, before and after, collected by Gemini for websites or Orion for apps. We commit to a minimum 30% improvement; most customers see 50% or more.
We use Gemini or Orion to baseline and measure the gain, and set it up as part of the engagement. [Confirm whether it is included in the price.]
Yes, read access is enough for the audit. Fixes go through your normal review, as pull requests or by pairing with your developers.
Each engagement has a fixed cost agreed before we start, based on the size of the site or app. Talk to us for a quote.
Last updated 7 Nov 2026 · Reviewed by [Name], [Role]