Your website used to feel snappy. Now pages hang for a few seconds before anything shows up, visitors bounce, and you're not sure whether to blame the hosting, the theme, or that plugin someone installed last month. The good news is that a slow website is almost never a mystery. It's usually one or two specific bottlenecks, and you can find them with free tools and a methodical approach.
This guide walks you through a practical, step-by-step process to diagnose why your website is slow and fix the real cause, instead of guessing and hoping.
Step 1: Measure Before You Touch Anything
Don't start "optimizing" until you have a baseline. Otherwise you won't know whether a change helped, hurt, or did nothing at all.
Run a lab test
Use Google PageSpeed Insights or the Lighthouse panel in Chrome DevTools. Test at least three pages: the homepage, a typical content page (like a blog post), and your heaviest page (a product listing, property search, or gallery). Write down these numbers for each:
Time to First Byte (TTFB): how long the server takes to start responding. Above about 800 ms is a server-side problem.
Largest Contentful Paint (LCP): when the main content becomes visible. Aim for under 2.5 seconds.
Interaction to Next Paint (INP): how quickly the page reacts to clicks and taps. Aim for under 200 ms.
Cumulative Layout Shift (CLS): how much the layout jumps around while loading. Aim for under 0.1.
Total page weight and number of requests.
Check real-user data
Lab tests are a simulation. If your site gets enough traffic, PageSpeed Insights also shows field data from real visitors. When lab and field data disagree, trust the field data: it reflects your actual audience's devices and connections.
Step 2: Decide Whether It's the Server or the Front End
This single question cuts your troubleshooting time in half. Look at TTFB first.
High TTFB (slow before anything downloads): the problem is on the server side: hosting, database, backend code, or missing caching.
Low TTFB but slow LCP: the server is fine, and the browser is struggling with heavy images, render-blocking scripts, fonts, or third-party code.
Open the Network tab in DevTools, reload the page, and look at the waterfall chart. It shows every file the page loads, in order, and how long each one took. The longest bars and the files that block everything after them are your prime suspects.
Step 3: Fix Server-Side Slowness
Turn on page caching
If every visit forces your server to rebuild the page from the database, it will slow down as traffic grows. Full-page caching serves a pre-built copy instead. On WordPress, a caching plugin or host-level cache does this; on custom apps (Laravel, Node.js, Next.js), use response caching, static generation for pages that rarely change, or a reverse proxy like Varnish or Nginx caching.
Find slow database queries
A single unindexed query on a large table can add seconds to every request. Enable your database's slow query log, or use a profiling tool such as Query Monitor (WordPress), Laravel Telescope or Debugbar, or your APM tool. Look for:
Queries that run on every page load but return the same data, which you can cache.
Queries filtering on columns without an index.
"N+1" patterns, where a list page runs one extra query per item instead of one query for all of them.
Check your hosting resources
Cheap shared hosting is a common culprit. If CPU or memory sits near its limit during busy hours, or TTFB is fine at night and terrible at noon, you've outgrown your plan. Upgrading to a VPS or managed host, and making sure you're on a current PHP or Node.js version, often gives an immediate boost.
Use a CDN
If your visitors are spread across countries, a content delivery network serves static files from a location close to each visitor. This cuts latency dramatically for anyone far from your server.
Step 4: Fix Front-End Slowness
Shrink and modernize your images
Images are the number one cause of heavy pages. A single 4 MB photo uploaded straight from a phone can ruin your LCP. Fix it by:
Resizing images to the largest size they're actually displayed at.
Converting to WebP or AVIF, which are often 30 to 50 percent smaller than JPEG at similar quality.
Adding
loading="lazy"to images below the fold, but not to the main hero image.Setting explicit width and height so the layout doesn't jump.
Cut render-blocking CSS and JavaScript
Scripts in the page head that load before content can delay everything. Add defer to non-critical scripts, remove CSS and JS from pages that don't need them, and minify what's left. Many sites load an entire slider or form library on every page when it's only used on one.
Audit third-party scripts
Chat widgets, heatmaps, multiple analytics tags, social embeds and ad scripts add up fast. List every third-party script on the site and ask whether it's still earning its place. Removing two or three unused tags is often the cheapest speed win available.
Optimize web fonts
Load only the font weights you use, host fonts locally where possible, and use font-display: swap so text appears immediately instead of staying invisible while fonts download.
Step 5: Look for the "Something Changed" Problem
If the site was fast and suddenly became slow, something changed. Before deep optimization, check:
Recently installed or updated plugins, packages, or themes.
New tracking or marketing scripts added by another team.
Large new media uploads on key pages.
A traffic spike or bot crawl hammering the server (check your access logs).
An expired cache configuration or a disabled CDN after a migration.
Disable suspects one at a time on a staging copy and re-test. This is often faster than optimizing everything.
Step 6: Re-Test and Keep It Fast
After each fix, re-run the same tests on the same pages and compare against your baseline. Keep a simple log of what you changed and what it did. Then put guardrails in place so the site doesn't slowly regress again:
Set an image size limit or automatic compression on upload.
Review new plugins and scripts before they go live.
Schedule a monthly speed check of your top pages.
Set up uptime and performance monitoring that alerts you when response times climb.
Quick Troubleshooting Checklist
Measure TTFB, LCP, INP and CLS on three key pages.
High TTFB? Check caching, slow queries, and hosting resources.
Low TTFB but slow LCP? Check images, render-blocking files, fonts, and third-party scripts.
Sudden slowdown? Review what changed recently.
Re-test after each change and keep monitoring.
Final Thoughts
A slow website costs you visitors, search rankings and sales, but fixing it doesn't have to be guesswork. Measure first, separate server problems from front-end problems, fix the biggest bottleneck, and re-test. Most sites can cut load times significantly with caching, image optimization and a cleanup of unnecessary scripts alone.
If your site needs deeper work, such as backend refactoring, database tuning or a move to better infrastructure, an experienced web development team can audit the full stack and build a performance plan that lasts.