Page speed affects two things every merchant cares about: search rankings and conversion. Google uses Core Web Vitals as a ranking signal, and shoppers abandon slow pages, especially on mobile. Many SuiteCommerce and SuiteCommerce Advanced (SCA) sites score poorly on these metrics. This guide explains why, what you can fix in place, and when a new frontend is the better investment.
Core Web Vitals in one minute
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps while loading | 0.1 or less |
Google measures these from real Chrome users (field data). Lighthouse and PageSpeed Insights also give lab scores that help you diagnose problems.
Why many SuiteCommerce sites are slow
Not every SuiteCommerce site is slow. Well-maintained, current sites with disciplined customization can perform well. The common causes we see on slow ones:
1. A large single-page application
SuiteCommerce is built as a single-page application. The browser downloads and runs a large JavaScript bundle before the page becomes fully interactive. On mid-range phones, that work hurts both LCP and INP.
2. Years of customization
SCA sites accumulate custom modules, extensions, and third-party scripts. Each one adds JavaScript, and old code is rarely removed. Bundle size grows release after release.
3. Running behind on releases
Because SCA upgrades require merging customizations, many sites stay several releases behind and miss performance improvements in newer versions.
4. Third-party tags
Chat widgets, review widgets, analytics, ad pixels, and personalization scripts often load early and compete with your own content.
5. Images
Large product images without modern formats, responsive sizes, or lazy loading are one of the biggest LCP problems on any store.
6. Hosting and caching
Where pages are rendered and cached affects how quickly the first byte arrives, especially for shoppers far from the data center.
What you can fix without replatforming
Start here. These changes help on any platform:
- Audit third-party scripts. Remove what you do not use. Load the rest after the page is interactive, through a tag manager with consent controls.
- Optimize images. Serve WebP or AVIF, size images for the device, and lazy-load images below the fold.
- Reserve space. Give images, banners, and embeds fixed dimensions to stop layout shift.
- Trim custom modules. Remove dead code and unused extensions.
- Upgrade. If you are several SCA releases behind, a current release may help, though it can be a project.
- Measure field data. Use the Core Web Vitals report in Search Console to see which templates real users struggle with.
When a new frontend is the better answer
Fixes in place have limits. If your bundle is large because of the architecture, and upgrades are expensive because of customization, you are paying twice to stand still. A modern frontend changes the starting point:
- Server rendering. Content arrives as HTML, so LCP does not wait for a large script.
- Code splitting. Each page loads only the code it needs; heavy features such as checkout, reviews, and modals load on demand.
- Edge delivery. Pages are served from a global network close to shoppers.
- Image optimization. Modern formats and responsive sizes by default.
- Performance budgets. Bundle size can be tracked and capped on every release.
AwaCommerce Next storefronts are built this way, on Next.js, while NetSuite stays your ERP. See the SuiteCommerce alternative overview and the NetSuite B2C ecommerce page.
How to measure your own site
- Open PageSpeed Insights and test your home page, a category page, and a product page on mobile.
- Note the field data (top section) and the lab score.
- Open the Core Web Vitals report in Search Console to see which URL groups fail.
- Record the results; they are your baseline for any change, including a migration.