Platform-specific steps to pass Core Web Vitals on WordPress and Shopify — plugins, themes, images, and code.
To pass Core Web Vitals on WordPress, use a caching/optimisation plugin, a lightweight theme, compressed images, and good hosting. On Shopify, choose a fast theme, remove unused apps, optimise images, and minimise custom Liquid/JS. Here are the complete, platform-specific steps for each.
Why WordPress and Shopify Need Genuinely Different Approaches
WordPress is a self-hosted, highly extensible platform where you control the server, the theme code, and every installed plugin directly — which means both more potential points of failure and more direct control over fixing them. Shopify is a fully hosted platform where the underlying infrastructure and checkout are fixed and outside merchant control, but themes and apps still introduce plenty of room for performance problems within what you can control. Recognizing which platform you're on shapes which of the fixes below are even available to you, and which specific ones deserve your attention first.
Step 1: Measure First
Run the free Website Speed Test and note exactly which Core Web Vital is failing — LCP, INP, or CLS. Fix that specific one first, rather than making broad changes across your whole site without knowing which metric actually needs the attention. See what are Core Web Vitals if you need the full explanation of what each metric measures.
Step 2: WordPress — Install a Caching and Optimization Plugin
A reputable performance plugin handles page caching, minification, and lazy loading in one place, which is usually the single highest-leverage step available on WordPress specifically. Look for one that's actively maintained and widely used, since WordPress performance plugins vary considerably in quality and can occasionally introduce their own conflicts if poorly maintained.
Step 3: WordPress — Optimize Every Image
Pair a compression plugin with modern format support (WebP), and make sure every image has explicit width and height dimensions set, which directly prevents the layout shift that hurts your CLS score. Compressing images is consistently one of the fastest, most reliable improvements available on any WordPress site, regardless of theme or hosting.
Step 4: WordPress — Choose a Lightweight Theme
Avoid bloated, multipurpose themes and page builders wherever a lighter alternative genuinely covers your actual needs — many popular all-in-one themes ship with far more CSS and JavaScript than any single page actually uses, and that unused weight loads on every visit regardless of whether a given page needs it.
Step 5: WordPress — Limit Your Active Plugins
Every plugin adds its own scripts, styles, and often its own database queries — audit your active plugin list and remove anything that isn't earning its cost in load time. This is a five-minute audit that regularly reveals two or three plugins nobody remembers installing, quietly slowing every single page load.
Step 6: WordPress — Upgrade to Genuinely Good Hosting
Managed WordPress hosting, purpose-built for the platform, reliably lowers Time to First Byte (TTFB) compared to generic shared hosting — and no amount of plugin-level optimization fully compensates for a server that's slow to respond in the first place.
Step 7: WordPress — Preload the LCP Image and Defer Non-Critical JS
Explicitly preload whichever image determines your Largest Contentful Paint score, and defer loading of any JavaScript that isn't required for the page's initial render. What you often can't fully fix through plugins alone: heavy third-party scripts baked into a theme, and some categories of page-builder bloat that no plugin can strip out after the fact — sometimes a rebuild really is the more honest, durable answer.
Step 8: Shopify — Choose a Genuinely Fast Theme
Pick a performance-focused theme and actually test it with the speed test before fully committing, since Shopify themes vary considerably in baked-in performance even among ones marketed as "fast." A theme that looks visually appealing in a demo can still carry a meaningfully heavier code footprint than a competing, equally attractive option.
Step 9: Shopify — Audit and Remove Unused Apps
Every installed Shopify app injects its own code into your storefront, whether or not it's actively contributing value — this is consistently one of the most common causes of slow Shopify stores specifically. Audit your installed apps regularly and remove anything not delivering clear, ongoing value relative to its performance cost.
Step 10: Shopify — Optimize Images and Minimize Custom Code
Compress images and use appropriately sized versions for each specific placement — Shopify serves WebP automatically where supported, but that doesn't substitute for starting with a correctly sized, compressed source image. Trim custom Liquid code and JavaScript snippets accumulated over time, and limit sliders and pop-ups specifically, since both are common, often-overlooked sources of poor LCP and CLS scores on Shopify storefronts.
Common Plugin and App Conflicts to Watch For
Installing multiple caching plugins simultaneously on WordPress is a frequent, self-inflicted cause of new problems rather than solutions — they can conflict over how they handle the same cached content, sometimes producing a slower or broken result than having no caching plugin at all. Similarly on Shopify, installing more than one app that modifies the same storefront element (two different "sticky add to cart" apps, for instance) can create both a performance and a functional conflict. Before adding a new performance-focused plugin or app, check whether an existing one already covers that specific function.
What You Can't Change on Shopify
Shopify's core platform and checkout flow are outside merchant control — you can't rebuild the underlying checkout for speed the way you could on a fully custom site. This means Shopify speed optimization should focus specifically on what you can control: theme choice, installed apps, images, and custom code, rather than chasing improvements to parts of the platform that aren't actually adjustable.
What You Can't Fully Change on WordPress Either
Similarly, on WordPress, some constraints are structural rather than fixable through settings alone — a theme's fundamental architecture, or a page builder's underlying approach to generating markup, sometimes can't be optimized away without switching to a different theme or builder entirely. Recognizing when you've hit this kind of structural ceiling, rather than continuing to tweak settings that won't move the needle further, saves considerable wasted effort.
A Worked Example: A WordPress Site Passing All Three Vitals
Say a WordPress business site starts with LCP at 4.5s, INP at 350ms, and CLS at 0.2 — failing all three. Following Steps 2 through 7: installing a reputable caching plugin and enabling image lazy-loading brings LCP down to 3.1s; auditing and removing four unused plugins (a slider, an old SEO plugin replaced by another, and two abandoned form builders) brings INP down to 180ms by reducing overall JavaScript execution; and setting explicit dimensions on the site's testimonial carousel images resolves the CLS issue, bringing it to 0.05. All three vitals now pass — achieved through five concrete, individually verifiable changes rather than one single silver-bullet fix.
Re-Test and Iterate
After each individual change, re-run the Website Speed Test and confirm the specific vital you were targeting actually improved before moving to the next fix. This is what turns a scattered list of general advice into a genuinely systematic, verifiable improvement process specific to your own site.
Headless and Composable Commerce as a Longer-Term Option
For Shopify merchants who've genuinely maximized theme and app optimization and still need better performance — often larger, high-traffic stores with complex custom requirements — a headless or composable commerce architecture (decoupling the storefront frontend from Shopify's backend) can offer a further performance ceiling beyond what any standard theme allows. This is a considerably larger undertaking than the steps above, generally only worth considering once the more accessible fixes are genuinely exhausted and performance is still a limiting business factor, not a first-resort solution for a typical store.
When to Get Help Instead of Continuing to DIY
If you've worked through the platform-specific steps above and your Core Web Vitals are still in the "poor" or "needs improvement" range, that's a reasonably strong signal the remaining issue is structural — a theme, app stack, or hosting plan that's fundamentally limiting rather than something one more plugin setting will fix. At that point, a professional audit or rebuild is typically both faster and more cost-effective than continuing to iterate on settings alone.
Choosing a Hosting Provider Specifically for Core Web Vitals
Not all hosting is created equal for Core Web Vitals purposes specifically — beyond raw server specs, look for providers offering built-in server-level caching, a content delivery network included by default, and modern PHP/HTTP protocol support, all of which reduce the amount of plugin-level or manual configuration needed to achieve good scores. Managed WordPress hosts in particular are often specifically optimized around exactly this goal, bundling caching, CDN, and image optimization as platform features rather than requiring you to configure each one separately through individual plugins.
WordPress Page Builders Specifically: A Special Case
Popular visual page builders (drag-and-drop editors offering extensive design flexibility) are worth calling out separately, since they're one of the most common sources of Core Web Vitals problems that survive even after the standard fixes above. These tools generate considerably more HTML and CSS than a hand-coded or template-based page would to achieve the same visual result, and that extra weight loads on every single visit regardless of whether a given page actually needs the builder's full flexibility. If Core Web Vitals remain stubbornly poor after working through the WordPress steps above, a page-builder-heavy site is a strong candidate for the underlying cause — worth testing a rebuilt page without the builder to isolate whether it's genuinely the bottleneck.
Shopify Theme Customization: Balancing Speed and Design
A frequent tension on Shopify specifically: merchants want visually rich, highly customized storefronts, but every additional custom section, animation, or visual flourish typically adds weight that works against Core Web Vitals. The practical balance most successful stores strike is being deliberate about which customizations genuinely serve conversion (clear product imagery, trust signals, an obvious call to action) versus which are purely decorative — the decorative additions are usually the first candidates to trim when a Shopify store's Core Web Vitals need improvement.
Testing Changes in a Staging Environment First
Before applying any of the steps above to a live, revenue-generating site, test them in a staging environment where available — most managed WordPress hosts and Shopify's theme editor both support previewing changes before they go live. This catches any unintended visual or functional breakage (a caching plugin conflicting with a specific feature, a Shopify theme change breaking a checkout customization) before real customers ever encounter it, which matters considerably more than the marginal speed gain from skipping this step to save time.
Maintaining Passing Scores Long-Term
Passing Core Web Vitals once isn't a permanent state — new content, theme updates, and newly installed apps or plugins can each quietly erode previously good scores over time. Building a simple maintenance habit (checking scores monthly, and immediately after any significant change to the site) catches regressions while they're small and easy to trace back to a specific recent change, rather than discovering months later that scores have drifted back into "needs improvement" with no obvious single cause to point at.
Frequently Asked Questions
Which plugin helps pass Core Web Vitals in WordPress?
A combination of a reputable caching/optimization plugin plus a dedicated image optimizer covers most common needs — though good hosting and a genuinely lightweight theme matter just as much as any single plugin choice.
Why is my Shopify store slow?
Usually too many installed apps, a heavy or poorly optimized theme, or oversized images — auditing installed apps first is typically the fastest way to find the biggest quick win.
Can I pass Core Web Vitals without hiring a developer?
Often yes on both WordPress and Shopify, using plugins, apps, and image optimization — but deeper structural issues (theme architecture, custom code bloat) may genuinely need developer help to resolve properly.
How many apps is too many for a Shopify store's performance?
There's no fixed universal number — the real question is whether each installed app is earning its performance cost in actual value delivered, not simply how many are installed in total.
Does switching WordPress themes always improve Core Web Vitals?
Not automatically — a lighter theme generally helps, but the improvement depends on how bloated your previous theme genuinely was and whether the new theme is properly configured and optimized too.
Is there a single fix that passes Core Web Vitals on both platforms?
Not a single universal one — the common thread across both platforms is images, hosting/apps-and-plugins bloat, and unnecessary custom code, but the specific implementation steps differ meaningfully between WordPress and Shopify.
How often should I re-check Core Web Vitals after passing them once?
Monthly, or immediately after any theme update, new app/plugin installation, or major content change — passing scores can regress silently as a site evolves, without anyone noticing until traffic or conversions are already affected.
Do WooCommerce stores need different steps than a standard WordPress site?
The same core steps apply, with extra attention to product image optimization and plugin auditing specifically, since WooCommerce stores tend to accumulate more plugins (payment gateways, shipping calculators, review widgets) than a typical content-only WordPress site.
Is a Shopify Plus store easier or harder to optimize for Core Web Vitals than standard Shopify?
Similar difficulty in practice — Plus offers more checkout customization options, which can introduce additional performance considerations, but the core theme, app, and image optimization principles remain the same across both tiers.
Can I pass Core Web Vitals on a WordPress multisite installation?
Yes, using the same principles applied consistently across each site in the network — a shared theme and plugin set makes this more manageable, since fixing performance once at the network level benefits every individual site.
Do free WordPress themes perform worse than premium ones for Core Web Vitals?
Not inherently — theme price doesn't determine performance; a well-coded free theme can outperform a poorly optimized premium one. What matters is the theme's actual code quality and feature bloat, not its price tag.
Should I test Core Web Vitals on staging before deploying theme or app changes to my live store?
Yes, wherever possible — testing on staging catches a performance regression before real customers experience it, and lets you compare before-and-after scores directly without risking your live site's actual visitor experience.
What's the single most impactful change most WordPress and Shopify sites can make?
Image optimization, consistently — it's the single change most likely to produce a large, measurable improvement across both platforms, since oversized, uncompressed images are the most common root cause on both WordPress and Shopify sites alike.
Do these steps apply the same way to a brand-new site as to an established one?
Yes, though a new site has the advantage of building with these principles in mind from day one — choosing a lightweight theme and a good host upfront, rather than retrofitting fixes onto years of accumulated content and plugins later.
Want your store or site to pass Core Web Vitals for good, not just temporarily? Scult can help with a proper audit and fix.
