Free performance scan · meyerpt.com
Free performance scan · meyerpt.com
Google scores meyerpt.com 38 out of 100.
Your server answers in 191 milliseconds, then the page sends 4.2 MB and the device spends 3.6 seconds working through it before anyone can order rehab and clinic supplies.
Get the full auditWhat that score means for the people ordering from you
The score is just the symptom. Here is what it does to the clinics and practices ordering from you, every time they open the site to order rehab and clinic supplies.
The weight of one page on a phone
Against the 2.1 MB median mobile page. Source: HTTP Archive, 2025.
Most of it comes from your own domain
Not tracking scripts. This is yours to fix.
How long the page stays unresponsive
Google marks anything past 0.6 seconds as poor.
Requests needed to open a single page
Each dot is one round trip before the page is ready.
Core Web Vitals, real visitors
Failing- Largest Contentful Paint (LCP)
- time until the main content shows
- Interaction to Next Paint (INP)
- lag after a tap or click
- Cumulative Layout Shift (CLS)
- how much the page jumps around
Google rates this origin “slow” for its real mobile visitors.
Why this costs you money
Every order takes longer than it should
Seconds of waiting on every page, repeated across every order and every user, is time your customers and your own reps spend doing nothing.
Slow sites generate support calls
When a page stalls, people phone someone. Your service desk absorbs the cost of a frontend problem that has nothing to do with them.
This is not unique to meyerpt.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 191 milliseconds. What follows it is not, and tuning barely dents it. A modern platform sends a fraction of it.
Your catalogue opens fast, on any device and any connection
4.2 MB page, 1.3 MB of it from your own domain
People can search and order the moment the page appears
0.85s of blocked time, 3.6s of main-thread work, 1.3 MB of JavaScript never used
Fewer calls to your service desk about the site being slow
145 requests to open one page
The payoff
Orders go through faster, your customers and your reps stop waiting on the portal, and your service desk fields fewer calls about the site. 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.