Halving page-load times for an 8-figure e-learning store
A multi-year performance program for The Great Courses on Adobe Commerce, delivered at Guidance, that cut typical page loads by about half.
- Client
- The Great Courses
- Industry
- E-learning and digital content
- Period
- 2015–2023
- Role
- Principal Adobe Commerce Engineer
Results
- Typical page load
- −50 %
- Years at Guidance
- 8
Challenge
The Great Courses ran a heavily customized Adobe Commerce store with a large digital catalog. Its category and product pages had become slow enough that the conversion funnel visibly suffered.
Custom modules, third-party extensions, integrations and hosting had all grown over time, and each change had made sense on its own. Nobody had a single view of where the time went, so performance work tended to stall on guesses.
Approach
I measured real-user performance first, so every later change could be compared against the same baseline. Then I worked through caching, indexing, database queries, frontend delivery and infrastructure, starting with the changes that would save the most time.
Each fix shipped as a small, reviewable change and was measured again after release. Changes that did not move the numbers were not kept. The work ran alongside the merchant’s regular feature roadmap, so the store kept shipping while it got faster.
At Guidance I also maintained a ScandiPWA headless storefront in production, including the GraphQL layer behind it, and built ERP integrations, subscription billing and custom shipping modules for other 8-figure stores. I reviewed the code of the engineers on those projects and mentored them.
Result
Typical page-load times fell by roughly half. I still start every performance engagement with that baseline.
Services in this project
- 03
Performance optimization
Faster pages without a replatform. A fixed-scope program on your current store, with every gain measured before and after.
- 07
Storefront strategy
A choice between keeping your theme, going headless and going composable, made for the team and budget you have and costed beyond launch day.
- 04
Audits and code review
A senior review of your code, modules and setup that finds the risks before your customers do. Every finding comes ranked by severity, with evidence and an estimate in hours.
Related posts
My Adobe Commerce performance checklist
Twelve checks, in order, that show where most of the page-load time goes on a typical Adobe Commerce store before any code is written.
PerformanceWhen to go headless on Adobe Commerce
Headless pays off only with a frontend team and a budget for two applications. How I decide between Hyvä and a separate storefront on Adobe Commerce.
Headless