My WordPress site is slow

WordPress can be fast or it can be molasses. The default Flashcloud caching stack handles the server-side work for you (see The cache stack we ship with every WordPress install and How we make your site fast). What's left is the application-level stuff — themes, plugins, content, and configuration.

Quick wins to check first

Before tuning, run through the obvious culprits:

1. LSCache plugin active

Open wp-admin → Plugins. Confirm LiteSpeed Cache is installed and active. Without it, WordPress isn't talking to the server-level cache.

If it's not active, activate it. If it's not installed, install it from Plugins → Add New → search "litespeed cache."

2. Heavy plugins

WordPress is fast; heavy plugins slow it down. Audit:

• Page builders (Elementor, Divi, WPBakery) — render-time costly. Often necessary, but pick one and lean on caching.
• All-in-one security (Wordfence Premium, etc.) — runs queries on every page load. Caching mitigates but doesn't eliminate.
• Backup plugins running on schedule — if scheduled during business hours, they slow live traffic. Move to off-hours.
• Live chat / push notifications / "engagement" widgets — every script loaded delays page rendering.

Tool: wp-admin → Plugins → Plugin Performance Profiler (or any speed-test plugin) shows which plugins contribute most to load time.

Disable plugins you don't actively use. If a plugin you "need" is hurting performance, look for a lighter alternative.

3. Image weight

Big images are the #1 frontend slowdown. Audit:

• Original size — uploaded a 4MB DSLR photo for a thumbnail? That's 4MB visitors download.
• Format — modern WebP is 30% smaller than JPEG at equivalent quality.
• Lazy loading — images below the fold should load only when scrolled into view.

The LiteSpeed Cache plugin's image optimization handles all three automatically once turned on:

1. Open wp-admin → LiteSpeed Cache → Image Optimization.
2. Click Send Optimization Request.
3. The plugin requests optimized versions from LiteSpeed's CDN; replace originals with optimized versions.

Initial optimization can take a few minutes for large media libraries; subsequent uploads are processed automatically.

4. Theme bloat

Some themes load 20+ JavaScript files and 10+ stylesheets, half of which aren't used on most pages. Indicators:

• Long load time even on cached pages.
• Lighthouse "Reduce unused JavaScript" warning.
• Network tab shows hundreds of requests per page.

Options:

• Switch to a lighter theme (GeneratePress, Astra, Kadence, Hello are all under 100KB).
• Use the LiteSpeed Cache plugin's CSS/JS optimization to combine and minify.
• For builders that allow it, configure to only load styles for elements actually on the page.

5. Database bloat

Over time, WordPress databases accumulate junk: post revisions, transients, spam comments, expired sessions.

To clean up:

• Plugin route: install a database cleanup plugin (WP-Optimize, WP-Sweep). Run a cleanup pass.
• Manual route: in phpMyAdmin, delete from wp_posts where post_type = 'revision', etc. Be careful — back up first.

A clean database queries faster, and Redis object cache effectiveness goes up.

Beyond the basics

If the basics are handled and you still want more:

CDN for static assets

We have Cloudflare integrated automatically. To get more out of it:

• Turn on Cloudflare proxy mode for your domain (the orange cloud in DNS).
• Cloudflare now caches images, CSS, JS at its edge globally.
• See the Cloudflare panel in the portal's services area.

Critical CSS

The LiteSpeed Cache plugin can generate "critical CSS" — only the styles needed for above-the-fold content, inlined for instant render.

wp-admin → LiteSpeed Cache → Page Optimization → CSS Settings → Generate Critical CSS. Click the button; it crawls your pages and creates critical CSS automatically.

Visual benefit: site appears to load instantly, even before all CSS finishes downloading.

Defer or async JavaScript

Most WordPress JS doesn't need to block page render. The LiteSpeed plugin's Page Optimization → JS Settings → Defer/Async handles this. Test after enabling — some interactive scripts misbehave when deferred, requiring an exclusion list.

Database indexes

For high-traffic sites, missing database indexes on frequently-queried columns cost real time. WP-Optimize and similar plugins can audit; or have a developer review the slow query log.

Heavy WooCommerce stores

WooCommerce sites have specific needs:

• Don't cache cart/checkout pages (LiteSpeed handles this automatically).
• Object caching matters more — Redis is critical for product, customer, and order queries. Confirm Redis is wired in (it's auto on our hosting).
• Disable WooCommerce features you don't use — analytics tracking, REST API endpoints, etc.

Off-page caching

Caching at the page-rendering level only goes so far. Some sites benefit from:

• Static-site generation for content-heavy sites (LSCache plugin's "ESI" feature is the closest WordPress gets to this).
• Headless WordPress + a static frontend (Next.js, Astro) for sites that primarily serve content. Significant rebuild but huge speed wins.

Diagnosing what's slow

Use these tools to identify bottlenecks:

• GTmetrix (gtmetrix.com) — full waterfall, identifies slow resources.
• PageSpeed Insights (pagespeed.web.dev) — Google's tool, weights mobile heavily.
• WebPageTest (webpagetest.org) — most detailed; configurable network/device profiles.

Run these before and after each change so you know what's helping.

When to upgrade hosting

If you've optimized everything and the site is still slow under load, your hosting plan may be the bottleneck. Indicators:

• CPU spikes during normal traffic.
• "504 Gateway Timeout" errors during peaks.
• Lighthouse "Reduce server response times" warning persistent.

Upgrade to a higher plan for more CPU and memory, or move to a VPS for dedicated resources.

Power-user note

For granular profiling, install Query Monitor (a free WordPress plugin). It shows which queries are slow, which hooks fire repeatedly, which plugins consume the most time per request. Especially useful for identifying that one plugin running 50 queries per page load. Install it on a staging copy if you don't want to risk live performance.