Share the site and market context
Share your production URL and tell us where your users are, so the test is calibrated to the market you actually serve.
From real-user evidence to confidence-ranked decisions
A 3-second delay can wipe out
30% of your revenue.
Most teams still cannot see what poor site performance is costing the business or which fixes matter first. Stroma turns that blind spot into evidence and a revenue-ranked path forward. Most teams still cannot see what poor performance costs or which fixes matter first. Stroma makes it measurable.
Scroll
Your product loads in 2s in DevTools. Real users in Lagos wait 18s.
Every decision makes sense on its own. At scale, they compound into lost conversion: higher bounce rates, lower ad ROI, and users who leave before they convert. We diagnose the system, not just the symptoms. Each decision looks harmless alone. Together, they drag conversion down. We diagnose the system, not the symptom.
4.2s to 8.7s mobile load gap R0.85 per-visit data burden 63% mobile / mid-range usage 17–41% mobile conversion delta 53% bounce when mobile load exceeds 3s
Indicative figures from HTTP Archive, CrUX, StatCounter and industry conversion studies
Free Snapshot
See what your site may be costing you.
Free Snapshot. No call required. Delivered in 2–3 business days.
How It Works
From one URL to a commercial decision in three steps
You give us the site. We test it against the users you actually serve. You get a decision-ready Snapshot that shows whether deeper work is justified.
Run the site against customer reality
We test against real devices, real networks, and the conditions your customers actually experience, not office broadband or synthetic defaults.
Turn the gap into a decision
You get scores, revenue-at-risk ranges, and a clear recommendation on whether the evidence justifies deeper work.
Free. No call required. Delivered within 2–3 business days.
Inside The Snapshot Report
What lands in your hands
Every Snapshot is a web performance diagnostic structured to support a go or no-go decision, not just deliver a technical readout.
-
01
Bleed Index severity score
A 0–100 score showing how much performance is costing you, with severity tier and urgent barrier summary.
-
02
Where revenue friction is showing up
Drop-off patterns and likely friction sources: slow content, interaction delays, device mismatch, and third-party drag.
-
03
How your market context changes the picture
Mobile versus desktop performance plus benchmark gaps calibrated to the region you serve.
-
04
Diagnostic evidence behind the gap
The technical causes behind the slowdown: oversized scripts, third-party tags, render-blocking resources, and how they compound under real network conditions.
-
05
Commercial range and next-step recommendation
Directional revenue-at-risk ranges with the assumptions behind them, plus a clear recommendation on whether deeper work is justified.
-
06
Evidence gate, not manufactured urgency
If the numbers do not justify investment, the report says so. The point is decision clarity, not pressure.
If the evidence is strong enough to go deeper
If the evidence justifies it
The work after the Snapshot builds assets, not dependency Build assets, not dependency
Each layer answers a different decision. You commit more only when the previous layer proves the case, and every asset transfers to your team. Each layer answers a decision. You only go deeper when the evidence earns it.
01
Gate 0 foundation
Measure
What your customers actually experience
Instrument the real customer environment so you can see who users are technologically.
- Asset
- Customer infrastructure profile
- Unlocks
- Is the gap material?
02
Gate 1 commercial case
Quantify
What the gap is costing you
Model the gap with your own traffic, conversion, and value data so every assumption can be challenged.
- Asset
- Gap model + assumptions
- Unlocks
- Is the opportunity worth a full diagnosis?
03
Gate 1 diagnostic evidence
Diagnose
Why it is happening and which causes have the strongest evidence
Trace vendor drag, payloads, and friction back to estimated commercial impact so causes are prioritised by consequence and evidence strength.
- Asset
- Attributed findings ranked by impact
- Unlocks
- Which causes deserve engineering time?
04
Gate 2 decision architecture
Decide
What to fix first and how to prove it worked
Turn the evidence into a revenue-ranked backlog, success criteria, and a playbook your team can run.
- Asset
- Revenue-ranked backlog + playbook
- Unlocks
- What enters Wave 1, and how success is measured
You keep the measurement infrastructure, commercial model, prioritised backlog, and decision playbook.
- Paid channels losing qualified traffic
- Quote flows underperforming on mobile
- SEO visibility dragged by CWV gaps
- Teams shipping fixes without evidence
Common questions
FAQ
Who is this for?
Anyone accountable for digital revenue, including CTOs, CMOs, product leaders, and founders, who ships web products to users on mobile or in markets with real infrastructure constraints. Engineering leaders get technical root causes. Marketing leaders get revenue impact tied to ad spend. Product leaders see which UX trade-offs are costing real performance.
How is this different from running Lighthouse ourselves?
Lighthouse gives you a lab score. The Snapshot shows what real-user performance is likely costing you in the market you actually serve.
It is designed to support a commercial decision, not just expose a technical issue. If you go deeper, the next layer replaces external benchmarks with your own measured data and a commercial model your team can challenge line by line.
Is the Snapshot really free? What's the catch?
Yes. The Snapshot is free because it is the first decision screen, not a teaser deck.
You get the report, the evidence summary, and the recommendation either way. If the numbers justify deeper work, we tell you what the next gate would build. If they do not, you still keep the Snapshot and the recommendation.
How accurate are the revenue estimates?
For the free Snapshot, they are directional ranges, not guarantees. We use published speed-to-conversion research, market calibration, and observable site evidence to size the gap conservatively.
If you go deeper, the next layer replaces external benchmarks with your own traffic, conversion data, and product economics. Every model is scenario-based, assumption-led, and explicit about correlation versus causation.
What happens after the Snapshot?
If the Snapshot shows meaningful revenue at risk, the next step is an evidence-gated system: measure what your customers actually experience, quantify what the gap is costing you, diagnose what is driving it, and decide what to fix first.
Each stage produces assets your team keeps. If the numbers do not justify deeper work, you still keep the Snapshot report, the evidence summary, and the recommendation.
What do we keep if we stop after the Snapshot or Gate 0?
If you stop after the free Snapshot, you keep the report, the evidence summary, and the recommendation.
If you proceed to Gate 0 and stop there, you keep the deployed measurement infrastructure, the Customer Infrastructure Profile, and the directional commercial assessment. Stroma builds capability that transfers to your team, not dependency on ours.
How is this different from a dev agency audit or a RUM tool?
A dev agency audit usually gives you generic recommendations. A RUM tool gives you ongoing symptom monitoring.
Stroma builds the layer between them: measurement infrastructure, a commercial model, diagnostic evidence, and a revenue-ranked decision system your team can operate independently. That is why the assets still matter after the engagement ends.
Do we need Stroma to implement fixes?
No. The goal is to hand your team or delivery partner a prioritised backlog, success criteria, and a decision playbook tied to measurement infrastructure.
Your internal team is often the right executor once the evidence is clear. Stroma can stay involved if useful, but the system is designed to be operated without us.
Jonathan Booysen
Founder, Stroma
Eleven years at MultiChoice, building products like DStv Stream and MyDStv across design, development and engineering management for millions of users across Africa.
When your product reaches that many people on 3G and entry-level devices, you learn where performance actually breaks. It's rarely where dashboards point first. It shows up in compounded decisions that look fine in high-bandwidth offices but fail on real networks. That gap between what gets measured and what gets experienced is where I work.
That experience became the foundation for Stroma's approach: measure what's real, quantify what it costs, diagnose why, and prioritise fixes in waves that pay for themselves.
Eleven years at MultiChoice, building DStv Stream and MyDStv for millions of users across Africa, taught me where performance really breaks: on real networks and entry-level devices, not in office conditions.
That became Stroma's approach: measure what is real, quantify the cost, diagnose the cause, and prioritise fixes that pay for themselves.
Start here
Ready to see where you stand?
Response time
Same business day (GMT+2)