WordPress Speed Optimization Checklist (Core Web Vitals)

Start with measurement, not another plugin

WordPress speed work fails when teams install three optimization plugins before measuring anything. Begin with field-relevant checks: mobile load on a mid-range phone, time to first meaningful content, and which requests dominate the waterfall. Lab tools help; real-device checks decide.

This checklist is ordered by impact for typical business and WooCommerce sites. Pair it with Core Web Vitals improvements, technical SEO for WordPress, and commercial WordPress speed optimization when you want a developer-led pass.

Core Web Vitals on WordPress: LCP, INP, CLS

LCP (Largest Contentful Paint)

LCP is usually a hero image, heading block, or large banner. Improve it by:

• Serving a correctly sized hero image (not a 4000px photo in a 1200px slot)
• Preloading only the true LCP image when helpful
• Avoiding late-loading sliders as the first paint
• Reducing TTFB with better hosting/caching so HTML arrives sooner
• Limiting render-blocking CSS/JS above the fold

INP (Interaction to Next Paint)

INP reflects how quickly the page responds to taps and clicks. Heavy main-thread JavaScript from builders, chat widgets, and tag managers is a common cause. Reduce long tasks, defer non-critical scripts, and avoid stacking multiple animation libraries on marketing pages.

CLS (Cumulative Layout Shift)

CLS rises when images lack dimensions, fonts swap late, or injected banners push content. Set width/height (or aspect-ratio) on media, reserve space for ads/embeds, and stabilize cookie banners so they do not shove the hero after load.

1. Hosting and server basics

Hosting sets the floor.

• Prefer PHP versions your stack supports (current stable, not abandoned)
• Confirm enough PHP memory for your plugin set
• Enable HTTPS with a modern TLS setup
• Use object caching (Redis/Memcached) when the host supports it and traffic justifies it
• Keep the database close to the application

If the site has outgrown noisy neighbors, plan a WordPress VPS migration. Faster TTFB from better infrastructure often beats micro-optimizing CSS while the origin is slow.

2. Caching layers that earn their keep

Page caching

Serve cached HTML to anonymous visitors. Exclude cart, checkout, account, and personalized pages.

Browser caching

Set sensible cache headers for static assets. Version filenames when assets change.

Object caching

Helps WordPress avoid repeated expensive database queries. Most valuable on dynamic or high-traffic sites.

CDN (when it fits)

Push images, fonts, and static files to edge locations when your audience is spread out. Keep origin rules clear so HTML caching does not fight logged-in sessions.

3. Images and media discipline

• Compress before upload
• Prefer modern formats where support is fine for your audience
• Size images to the largest display width they need
• Lazy-load below-the-fold media; keep the LCP image prioritized
• Avoid auto-loading video backgrounds on mobile heroes

Page builders amplify media mistakes because every section invites another full-width image. See Elementor vs custom WordPress development.

4. Fonts

Fonts are a frequent LCP/CLS contributor:

• Limit families and weights to what the design actually uses
• Prefer font-display: swap (or equivalent) with stable fallbacks
• Self-host when it reduces third-party connection chains
• Avoid loading an entire icon font for three icons

5. Theme and builder weight (including Elementor)

Audit what the theme loads on a blank page:

• Extra Google Fonts or icon packs unused in the design
• Homepage scripts on interior pages
• Slider libraries for a single fade animation
• Demo content CSS left behind after setup

For Elementor or similar builders: disable unused widgets/features if the product allows it, reduce nested containers, and avoid stacking animation libraries. Custom themes and ACF-driven layouts often win when you need predictable CSS budgets.

6. JavaScript and CSS delivery

• Dequeue scripts on pages that do not need them
• Delay non-critical third-party tags until interaction when acceptable
• Combine only when it reduces requests without creating a megabyte blob
• Remove unused CSS from builders when tooling makes it safe

Critical CSS tricks help, but they are fragile if editors constantly change above-the-fold layouts. Stabilize the hero template first.

7. Plugin audit that actually removes things

List every plugin and ask:

1. Is this still used in production?
2. Does a lighter alternative exist?
3. Can the theme or a small custom snippet replace it?
4. Does it load assets site-wide when it should load on one template?

Typical removals: redundant SEO plugins, duplicate form plugins, social share suites that inject scripts everywhere, and overlapping “security” tools.

8. Database and backend hygiene

• Remove spam comments and unused revisions on a schedule
• Clean expired transients
• Keep autoloaded options under control
• Avoid storing huge serialized blobs in options for convenience

Maintenance is part of ongoing website care.

9. Third-party scripts and marketing tags

Chat widgets, heatmaps, pixel managers, and A/B tools add up. Negotiate with marketing: load chat after idle or click, limit overlapping analytics platforms, and avoid injecting tags through three different plugins.

10. WooCommerce considerations

• Paginate large catalogues
• Optimize product image sizes for shop and single templates
• Cache product archives carefully; never cache cart/checkout for shared users
• Review fragments and AJAX cart behaviors that refresh on every page
• Keep related-product queries reasonable

Cost and scope discussions live in WooCommerce website cost. Speed should be in the brief from day one.

Measurement process

After changes:

1. Re-test mobile and desktop on key templates: home, service/product, blog post, cart
2. Confirm forms, logins, and checkout still work
3. Watch error logs for plugin conflicts after removals
4. Compare field data (CrUX / Search Console) over weeks—not only one lab run
5. Document what you changed so the next update does not undo it

A realistic two-week remediation plan

Days 1–2: baseline — Capture mobile traces for home, a money page, and cart/product if relevant.

Days 3–5: remove and compress — Delete unused plugins, compress heroes, fix obvious LCP images, disable unused builder features.

Days 6–8: cache and host — Configure page cache exclusions, enable object cache if available, confirm TTFB improved.

Days 9–11: script control — Defer chat and secondary analytics, dequeue page-specific assets, stabilize fonts.

Days 12–14: verification — Regression tests, document the allowlist, hand marketing a “do not install without review” note.

How this fits into a service engagement

Speed work often sits beside security hardening and content structure. See WordPress speed optimization, WordPress developer, Elementor developer, and WooCommerce developer. Broader performance packaging: website speed optimization. Local hiring context: hire a WordPress developer in Chandigarh.

Checklist summary

1. Measure mobile reality and Core Web Vitals on money pages
2. Fix hosting and TTFB
3. Configure one coherent caching strategy
4. Compress and correctly size images; protect LCP
5. Slim fonts, theme, and builder weight
6. Remove redundant plugins
7. Clean database autoload bloat
8. Control CSS/JS and third-party tags
9. Special-case WooCommerce templates
10. Re-test and document

Work the list in order. Most business sites gain more from the first five items than from exotic micro-optimizations.