SpeedCurve

Web performance consultant for SpeedCurve

Discipline frontend performance with SpeedCurve

Optimizing once isn't enough — performance regresses with every unmeasured release. I install SpeedCurve to track Core Web Vitals over time, set performance budgets and block regressions before they ever reach production.

100% satisfied clients Data 2023-2026 8+ years XP 35+ clients partnered
View my client cases

They trust me

CHANEL
DIOR
Decathlon
April Moto
SiriusXM
Make Up Forever
Camif
RIMOWA
Jimmy Fairly
Wecasa
Chronovet
CHANEL
DIOR
Decathlon
April Moto
SiriusXM
Make Up Forever
Camif
RIMOWA
Jimmy Fairly
Wecasa
Chronovet

Symptoms that justify SpeedCurve

📉 Core Web Vitals drifting without the team noticing

PageSpeed at a single point in time isn't enough. SpeedCurve records history, spots per-deployment regressions, correlates synthetic and RUM. The exact cause of every degradation becomes identifiable.

🎯 A release can degrade performance without an alert

Without performance budgets, a new JavaScript dependency or an unoptimized image ships unnoticed. SpeedCurve blocks the regression before it reaches users.

🔬 Synthetic alone doesn't reflect real experience

WebPageTest under the hood paired with the LUX (RUM) module. The performance users actually live appears alongside the lab measurement. The gaps are instructive.

💼 The product team doesn't feel concerned by performance

LUX correlates Web Vitals with conversions, bounce, pages per session. Data replaces intuition with product and marketing. Performance becomes a business topic.

🏷️ Competitor performance tracking still done by gut feel

SpeedCurve automatically compares your URLs against chosen competitor URLs. Drift over time, alerts when a competitor overtakes your LCP on a key template.

🚦 CI doesn't block a release that degrades Web Vitals

The SpeedCurve API hits at every build, returning metrics to the pipeline. If a budget breaks, the build fails. Regressions caught at the source, not two days into production.

SpeedCurve leverage methodology

4 steps to transform your performance

1
Step 1

1. Strategic page scoping

Identify LCP-critical templates (home, product page, cart, checkout). Limit scope to stay within the billing budget.

2
Step 2

2. Synthetic test configuration

Define target connections (4G, Cable), browsers, geolocations. Set assertions on LCP, INP, CLS, TBT and budgets per asset category.

3
Step 3

3. RUM setup and calibration (LUX module)

LUX snippet in the head, custom conversions configuration (add to cart, form submission, order). Performance and business connected.

4
Step 4

4. Workflow integration

Slack alerts on every regression, shared dashboard per template, monthly budget review. Web performance becomes a routine topic.

Mission commitments

10+ strategic pages under monitoring
6+ active performance budgets
RUM correlated with business conversions
CI/CD integrated into team workflow
FAQ

Frequently asked questions

SpeedCurve vs Lighthouse CI: why pay for it?
Lighthouse CI measures a build's score at a single moment, in a test environment. SpeedCurve measures real public URLs over time, with automated history and integrated RUM. The two complement each other, but SpeedCurve brings the product discipline Lighthouse CI can't deliver.
Which CMSs does SpeedCurve work with?
The tool is backend-agnostic. It tests public URLs like a user. WordPress, Drupal, Magento, Shopify, custom: no difference. The LUX module is a snippet in the head, compatible with every frontend framework.
Does SpeedCurve RUM impact site performance?
Light LUX snippet (under 10 KB minified), async-loaded, executed post-onload. Measurable but marginal impact (under 5ms on the main thread). The analytical benefits widely outweigh the technical cost.
How does SpeedCurve help improve Core Web Vitals?
Three mechanics: fast regression detection via daily synthetic tests, regression blocking via performance budgets in CI, perf × conversion correlation to prioritize optimizations that pay off. The most complete tool to steer frontend performance over time.

Make SpeedCurve your Core Web Vitals guardrail

Synthetic + RUM configured
Active performance budgets
Product discipline embedded
100% satisfied clients
Data 2023-2026
Testimonials

What my clients say

Excellent work.
Paul has significantly improved the site's speed and perfectly aligned it with Google's recommendations.
Professional, thorough, and efficient, I highly recommend.

Nicolas - April Moto

Digital & E-commerce Director

We are very satisfied with Paul's work. He is quick, available, and particularly effective. Since his arrival, very good results have been observed, both in terms of performance and responsiveness. A real asset for our team.

Léo - Luxury brand

E-commerce Product Owner

I don't know if we've said it enough.
But if you want to improve your loading speed,
Make Google happy and get your Core Web Vitals in the green,
Contact Paul Delcloy.

Florian Darroman - Les Makers

Co-founder

SpeedCurve, the Core Web Vitals guardrail

Web performance isn't a one-time project — it's a discipline. A team that ships fast without measuring performance regresses every sprint without noticing. A JavaScript asset added here, an unoptimized image there, a third-party script dropped without testing — and three months later, Core Web Vitals are in the red on Search Console.

SpeedCurve solves that. The tool combines daily synthetic tests (built on WebPageTest) and Real User Monitoring (LUX module) for a full picture of frontend performance over time. Every strategic template gets tested, every budget tracked, every regression alerted before shipping.

Performance budgets and team discipline

On a SpeedCurve mission, I start by scoping strategic pages (home, product page, cart, checkout) and setting performance budgets tuned to each template's profile. Total JS, CSS, images, fonts, LCP, CLS, INP: every category gets its threshold. When a budget breaks, the team knows before production — not after CrUX turns red.

That discipline turns web performance into a team reflex. A developer adding a JavaScript dependency sees the bundle impact in the pipeline, and the trade-off happens at the right moment.

RUM to connect performance and business

The LUX module (Real User Monitoring) complements the synthetic approach by capturing the performance your users actually experience. Paired with custom conversions (add to cart, form submission, order), it ties Core Web Vitals to business indicators. Performance becomes a business argument, not just a technical topic. That's the angle that makes a web performance audit defensible to product and marketing, data in hand.