Free performance scan · razer.com
Free performance scan · razer.com
Your server answers in 30 milliseconds. Then the page sends 13.7 MB.
Most of that is your own images. Google scores the page 28 out of 100 on mobile, and on a mid-range phone your main image takes 24 seconds to appear.
Get the full auditWhat that score means for a shopper
The score is just the symptom. Here is how it affects real visitors on their phone, and makes shopping slower and more frustrating for them.
The weight of your homepage on a phone
Roughly six times the median mobile page. Source: HTTP Archive, 2025.
Almost all of it is your own images
From a single asset domain. This is yours to fix, not a vendor problem.
How long the phone spends working before it is done
Main-thread work on a mid-range phone, against the 2 seconds a fast page needs.
Requests needed to open a single page
Each dot is one round trip before the page is ready.
Core Web Vitals, real visitors
Needs work- Largest Contentful Paint (LCP)
- time until the main image shows
- Interaction to Next Paint (INP)
- lag after a tap or scroll
- Cumulative Layout Shift (CLS)
- how much the page jumps around
Google rates this origin “average” for its real mobile visitors: two of the three metrics pass, interaction delay does not.
Why this still matters
You pass today on a thin margin
Your real visitors clear two of the three Core Web Vitals, and interaction delay is already in Google’s “needs work” band. A heavier release or a slower quarter moves that the wrong way.
The lab result is the cheaper phone
Google’s mobile test runs a mid-range device on a throttled connection, and there your page scores 28. That is the shopper you are not seeing in the averages.
This is not unique to razer.com. It is what SAP Composable Storefront (Spartacus) does to almost every site built on it, and this one scores below the average.
Measured with Google PageSpeed Insights, mobile, September 2026.
Your store works fine. That's why the cost stays hidden.
We benchmarked 200+ live SAP Composable Storefront (previously Spartacus) sites on mobile. The two numbers below are the average, and almost every site scores about the same, no matter who built it.
Average mobile Lighthouse score
pass Google’s Core Web Vitals
Source: Alokai benchmark of 200+ public SAP Composable Storefront sites, 2026. Demo scores are single measured mobile Lighthouse runs; scores vary between runs.
What that slowness costs
- +8.4%
- higher conversion, plus 9.2% higher average order value, from a single 0.1s improvement in load time.
- 1%
- of sales lost for every 100 milliseconds of added latency, in Amazon’s own testing.
- 20–42%
- the conversion lift teams report after moving to a modern, lightweight frontend.
Google & Deloitte, “Milliseconds Make Millions”
Amazon
Composable migration benchmarks
Spartacus caps your performance low from the start. Alokai isn't bound by it.
Both demos ran the same mobile Lighthouse test, and both are full storefronts, not stripped-back shells. Spartacus scores lower because of how it's built: a heavy JavaScript bundle it can't shed, so teams fight the framework for every point instead of following it. Great performance comes from the architecture underneath, a BFF and a cloud doing the heavy lifting, which an accelerator doesn't have. You need a platform, not an accelerator.
What fixing this gets you
Your server is fast, answering in 30 milliseconds. What follows it is not, and tuning barely dents it. A modern platform sends a fraction of it.
Your store shows up fast, even on mobile data
13.7 MB page, 10.5 MB of it your own assets
Shoppers can tap and buy the moment it appears
5.5s of main-thread work, 0.9 MB of JavaScript never used
The same experience on a mid-range phone
Scores 28/100 in Google’s mobile test
The payoff
Your store ranks higher, earns more from every visit, and keeps the shoppers it wins. Your team stops fighting the framework and runs the store for less.
The last brand that asked us for an audit
Carolina Herrera came for the audit. They weren’t planning to replace their storefront.
Carolina Herrera, part of the PUIG group, wanted one thing: an independent read on their SAP Composable Storefront. We gave them that, including what they could fix without leaving. They moved to Alokai anyway, and two months after launch the results were already well past the KPIs they had set.
Pages Google now indexes
Every market finally has its own pages instead of one generic set.
Organic clicks from the US
Total organic clicks up 17%. The localised markets are where it compounded.
Localised click-through rate
Brazil doubled too, 0.6% to 1.1%.
Traffic to hero product pages
The pages that actually sell, in the markets that actually buy.
Migrating is not the year you think it is
Your backend doesn’t move. The frontend goes market by market, and because Alokai is AI-native, agents do the Spartacus rewrite in weeks instead of months.
You end up with the store you just saw you don’t have: fast on a phone, and built to stay that way instead of aging out from under you. It also puts you where Spartacus can’t follow, ready for the shoppers arriving through AI assistants instead of search.
The audit is free, and the findings are yours even if the answer is stay.
The full audit goes far deeper than one page
This is just a scan of your homepage. The full audit is an expert going through your actual codebase and telling you, in plain terms, what is costing you the most and what to do about it. It is free, and the findings are yours to keep.
Every page that makes you money
Not just the homepage. We check category, product, cart and checkout, and rank each fix by what it is worth to your revenue.
The real cost of staying on Spartacus
The architecture and upgrade problems that make every SAP release slower and riskier, so you can weigh another year on the platform with your eyes open.
An honest fix-or-move call
Repair what you have, or move the pages that matter most. We show both with the numbers, even when the answer is to stay where you are.
Reviewed by SAP Spartacus's original Tech Evangelist
Mateusz Ostafil has spent his whole career inside this exact stack. He was SAP Spartacus Tech Evangelist from version 1.0, the person who made the technology known, ran the first professional trainings on it, and sat in real implementation projects as the subject-matter expert.
- Tech Evangelist for SAP Spartacus since 1.0
- A dozen-plus code audits, including a global optical leader, a leading eye-care company, and a well-known beauty retailer
- Now Senior Developer Advocate at Alokai
He audited enough Spartacus frontends to see where the platform stops. That's what led him to Alokai, and it's why a full audit tells you the truth about what you have, not a pitch for what we sell.
What happens when you reply
Reply to this audit
Tell us it's useful and who on your team should see it.
15-minute scoping call
We agree what a full audit covers and what access you're comfortable with.
Mateusz reviews your code
Findings tied to your files, impact-rated.
Report plus a team workshop
A document your whole team can act on.
Want this audit on your real code, not just the homepage?
This scan looked at one public URL. A full audit reads your codebase and tells you exactly what to fix first, and whether to fix or migrate.