Free performance scan · jared.com
Free performance scan · jared.com
Google scores your storefront 8 out of 100. We rebuilt it at 88.
Your server answers in 20 milliseconds, then the page pulls 665 separate requests and 10.9 MB, and sits frozen for three and a half seconds. We built the same store on Alokai to show you the difference.
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.
Requests needed to open one page
Each dot is one round trip. Most of them are JavaScript.
The weight of your homepage on a phone
Roughly five times the median mobile page. Source: HTTP Archive, 2025.
JavaScript alone, across 404 files
2 MB of it is downloaded and never runs.
How long the screen stays unresponsive
Google marks anything past 0.6 seconds as poor. This is more than five times that, and taps do nothing until it catches up.
Core Web Vitals, real visitors
Failing- 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 “slow” for its real mobile visitors: the layout moves under them as it loads.
Why a failing grade matters
Google ranks you below faster stores
Core Web Vitals is a search ranking signal. A site that fails works harder for every visit and pays more for the same traffic.
Shoppers feel every bit of it
A page that moves under their thumb while it is still pulling hundreds of files is how carts get abandoned on a phone.
This is not unique to jared.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 20 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
10.9 MB page, 665 requests to open it
Shoppers can tap and buy the moment it appears
5.6 MB of JavaScript across 404 files, 2 MB never used
A page that stays still while it loads
Fails Core Web Vitals: CLS 0.31
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.
We already built it
We rebuilt your storefront. It scores 88.
Same brand, same catalogue, same pages, on Alokai instead of Spartacus. We built it so you can look rather than take our word for it. Both scored with Google PageSpeed Insights, on mobile, on the same day.
- Page weight
- 10.9 MB
- Requests
- 665
- Main image appears
- 29.1 s
- Layout shift
- 0.374
- Page weight
- 1.2 MB
- Requests
- 64
- Main image appears
- 3.6 s
- Layout shift
- 0
A demo does not carry your full marketing and analytics stack, and part of the gap is that. The rest is the platform: 64 requests against 665, and 404 of yours are JavaScript files.
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.