Free performance scan · carhartt.com

Faster stores are winning the mobile shoppers carhartt.com loses while it loads.

Amazon found that every 100 milliseconds of delay costs 1% of sales. On a phone, your homepage makes shoppers wait about 5 seconds before they can tap anything, and that gap is where the sales go.

Google Lighthouse · mobile speed

A “poor” result, and below the average even for SAP Spartacus stores.

Get the full audit

Full-page screenshot of the carhartt.com homepage as rendered on a phone

What 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.

6.8 MB

Every phone downloads 6.8 MB to open your homepage

4.2 MB of that is JavaScript, split across 135 separate files. On a normal mobile connection that is a slow, data-hungry first visit.

5.3 s

The phone sits frozen for more than 5 seconds

While it works through all that code, the screen is unresponsive. Taps, scrolls and menu clicks do nothing until it catches up.

1.3 MB

1.3 MB of that JavaScript is never even used

Downloaded, unpacked and parsed on every visit, then thrown away without running. Your shoppers pay the download cost for nothing.

312

312 separate requests to load one page

168 of them go to third-party scripts: analytics, chat, identity. Each one is another round trip before the page is ready.

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 marks the site as not passing Core Web Vitals for its real mobile visitors.

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 tap that lags almost a second, and a layout that jumps as they reach for it, is how carts get abandoned on a phone.

This is not unique to carhartt.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, July 2026.

Your store works fine. That's why the cost stays hidden.

We benchmarked 200+ live SAP Composable Storefront (Spartacus) sites on mobile. The two numbers below are the average, and almost every site scores about the same, no matter who built it.

39/ 100

Average mobile Lighthouse score

0 · poor100

<5%

pass Google’s Core Web Vitals

250+ sites

Source: Alokai benchmark of 250+ public SAP Composable Storefront sites, 2026.

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.

Spartacus caps your performance low from the start. A platform 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.

Mobile Lighthouse · demo vs demo

Alokai89.2

Composable Storefront (aka Spartacus)42

0100

What fixing this gets you

Your server is fast. The slowness comes from all the code Spartacus makes every phone run before your store works, and tuning barely dents it. A modern platform sends a fraction of it. Here is what that gets you.

Your store shows up fast, even on mobile data

6.8 MB page, 4.2 MB of JavaScript (1.3 MB of it never even used)

Each page loads only its own code instead of the whole store, so shoppers see it in a fraction of the download and fewer give up waiting.

Shoppers can tap and buy the moment it appears

5.3s of blocked time on load

There is far less code for the phone to run, so the page responds right away instead of ignoring taps for seconds.

Less third-party weight dragging every visit down

312 requests, 168 to third-party scripts

The page’s data is gathered in one server-side pass, and the full audit shows which tracking scripts you can safely cut.

A smooth experience Google rewards

Fails Core Web Vitals: INP 882 ms, CLS 0.83

You pass the Core Web Vitals check: pages load fast, respond right away and stay put. Fewer shoppers bounce, more reach checkout, and it holds up on the cheaper phones and weaker connections most mobile shoppers actually use.

The payoff

The payoff reaches every part of the business. Your store ranks higher, gets more from search and paid ads, and turns more visits into orders, with shoppers who come back. Your team stops fighting the framework, ships faster, and runs the store for less.

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.