Website Speed Checklist: How to Make a Slow Site Fast
A slow website loses visitors before they read a single word. People leave pages that take too long to appear, search engines use loading experience as a ranking signal, and every extra second makes a contact form or checkout less likely to be finished. The good news is that most slow sites are slow for the same handful of reasons, and most of them can be fixed without rebuilding anything. This checklist walks through how to measure speed properly, what usually causes the problem, and the fixes that make the biggest difference first.
Measure before you change anything
Guessing wastes time. Start with numbers, and test the pages that matter most: the home page, your most visited article or product page, and any page with a form.
- PageSpeed Insights shows lab results and, for sites with enough traffic, real-user data from Chrome. The real-user data is what Google actually uses.
- The browser's developer tools (Network and Performance panels) show which files load, how large they are and what blocks the page from appearing.
- WebPageTest lets you test from different locations and connection speeds, and shows a filmstrip of how the page appears over time.
Test on a mobile profile. A page that feels instant on office Wi-Fi can take many seconds on a mid-range phone with a weak signal, and that is the experience most visitors have.
The three numbers worth watching
Google's Core Web Vitals turn "fast" into three measurable things:
- Largest Contentful Paint (LCP): how long until the main content, usually the hero image or headline, is visible. Aim for 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Aim for 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the layout jumps while loading. Aim for 0.1 or less.
One more number sits underneath all of them: Time to First Byte (TTFB), how long the server takes to start sending the page. If TTFB is slow, nothing you do in the front end can fully make up for it.
1. Images: the usual suspect
On most small business sites, images make up the majority of the page weight. A single uncompressed photo straight from a camera or a stock site can be heavier than the rest of the page combined.
- Resize to the size it is shown. A hero displayed 1,600 pixels wide does not need a 6,000-pixel original.
- Use modern formats. WebP and AVIF are usually much smaller than JPEG at the same visual quality.
- Serve different sizes to different screens with
srcsetandsizes, so phones do not download desktop images. - Lazy-load images below the fold with
loading="lazy", but never lazy-load the main hero image, because that delays LCP. - Set width and height attributes so the browser reserves space and the layout does not jump.
- Use SVG for logos and icons instead of large PNG files.
For the editing side, see Image Editing for the Web, and for vector graphics, SVG for Web Designers.
2. Hosting and server response
If TTFB is consistently above about 600 milliseconds, look at the server before anything else. Common causes:
- Overcrowded shared hosting. Cheap plans put hundreds of sites on one server. When a neighbour gets busy, your site slows down.
- No page caching. A CMS that builds every page from the database on every visit does far more work than it needs to.
- An old PHP version. Each major PHP release has brought real speed improvements. Check which version your host runs.
- Server far from your visitors. A site for a European audience hosted on the US west coast adds delay to every request.
Fixes, from cheapest to most involved: turn on page caching, update PHP, add a CDN, and if that is not enough, move to a better plan or a better host. Our guides on choosing web hosting and basic server setup cover what to look for. If the hosting terms are unfamiliar, our sister site payless.host keeps a plain-English hosting glossary that explains TTFB, CDN, caching and the rest.
3. Caching and a CDN
Caching means not doing the same work twice. There are three layers worth knowing:
- Page cache stores the finished HTML so the server can send it immediately. On WordPress this is a caching plugin or a host-level cache.
- Browser cache tells returning visitors' browsers to keep CSS, JavaScript, fonts and images instead of downloading them again. It is controlled by cache headers set on the server.
- CDN (content delivery network) keeps copies of your files on servers around the world, so each visitor downloads them from somewhere nearby. Many CDNs have a free tier that is enough for a small site.
4. JavaScript and third-party scripts
JavaScript is the main cause of poor INP and a common cause of slow LCP. The worst offenders are often not your own code but things added over time: chat widgets, several analytics tools, heatmaps, social embeds, pop-up builders and ad scripts.
- List every third-party script on the site and ask whether it is still used. Remove the ones nobody looks at.
- Load scripts with
deferso they do not block the page from rendering. - Delay non-essential widgets, such as chat, until the visitor scrolls or interacts.
- Replace heavy embeds with lightweight placeholders. A YouTube video can show a thumbnail and load the player only when clicked.
- Avoid loading a large library for a small effect. Modern CSS and plain JavaScript handle most menus, sliders and animations.
For more on when JavaScript is worth its cost, see JavaScript for Web Designers.
5. CSS and fonts
- Remove unused CSS. Themes and page builders often load styles for components the site never uses.
- Limit web fonts to the families and weights you actually use. Each weight is a separate download.
- Use
font-display: swapso text appears immediately in a fallback font instead of staying invisible. - Preload the main font file if it is used above the fold.
- Self-host fonts when possible, which avoids an extra connection to another domain.
6. Layout shift
Pages that jump while loading frustrate visitors and hurt CLS. The usual causes are images and embeds without dimensions, banners or cookie notices inserted at the top after the page appears, and web fonts that are much wider or narrower than the fallback. Reserve space for anything that loads late, and add notices as overlays rather than pushing content down. The layout techniques in How to Learn CSS Layout help keep things stable.
7. WordPress-specific checks
WordPress sites slow down in predictable ways:
- Too many plugins, especially ones that load scripts on every page. Deactivate one at a time and measure.
- A heavy page builder or multipurpose theme. A lighter theme can cut page weight dramatically.
- A bloated database full of old revisions, spam comments and expired temporary data.
- No object cache on busy sites with many database queries.
If a speed problem appeared suddenly after an update, work through the WordPress troubleshooting checklist first.
A quick speed checklist
- Test the key pages on mobile in PageSpeed Insights and note LCP, INP, CLS and TTFB.
- Compress, resize and convert images to WebP or AVIF; lazy-load everything except the hero.
- Turn on page caching and browser caching.
- Add a CDN.
- Check the PHP version and server location; upgrade the plan or host if TTFB stays slow.
- Remove unused plugins and third-party scripts; defer the rest.
- Trim fonts and unused CSS.
- Set dimensions on images and embeds to stop layout shift.
- Test again and compare with the first results.
Speed is not a one-time job. New plugins, tracking codes and large images creep back in, so repeat the test every few months or after any major change.
Over to you: What was the single change that made the biggest speed difference on a site you worked on? Share it in the comments below.
Related reading: How to Choose Web Hosting · Image Editing for the Web · WordPress Troubleshooting Checklist
Comments
Post a Comment
Share your experience, add a tip or ask a question. Comments are open to signed-in Google users. Please keep it helpful and on topic.