This website speed optimization checklist gives you a repeatable way to improve loading performance, protect Core Web Vitals, and identify whether the problem is caused by images, code, hosting, fonts, caching, or third-party tools.
Overview
Website speed optimization is not a single setting. It is a maintenance process that starts with measurement, continues through practical technical changes, and ends with another round of testing. A site can feel fast on one device while remaining slow for visitors using a different phone, connection, or browser, so avoid judging performance from one personal browsing session.
Core Web Vitals provide a useful framework for reviewing the experience of real users. Largest Contentful Paint (LCP) relates to how quickly the main content becomes visible, Interaction to Next Paint (INP) reflects how responsive a page is after interaction, and Cumulative Layout Shift (CLS) focuses on unexpected movement during loading. These metrics should be considered alongside overall page weight, server response time, accessibility, and usability.
Before changing anything, record a baseline for your most important page types: the home page, a standard article, a product or service page, and any high-traffic landing page. Use a performance testing tool, browser developer tools, and—when available—real-user data from your analytics or search platform. Save the page URL, test date, device type, major warnings, and the change you plan to make. This makes it easier to tell whether an optimization actually helped.
For related setup work, see the complete website launch checklist and the guide to connecting a domain to hosting. Domain configuration does not directly optimize page code, but incorrect DNS, redirects, or hosting setup can affect availability and the path visitors take before reaching your site.
Checklist by scenario
For every website
- Test representative pages rather than only the home page.
- Run tests on both mobile and desktop conditions when the tool supports them.
- Record the largest files, slowest requests, render-blocking resources, and any layout shifts.
- Confirm that the site uses HTTPS consistently and does not create unnecessary redirect chains.
- Remove unused plugins, themes, scripts, widgets, and tracking tags that no longer serve a clear purpose.
- Retest after each meaningful group of changes so you know which change produced the result.
For image-heavy sites
- Resize images to the maximum display dimensions required by the design instead of uploading oversized originals.
- Compress images before uploading and choose a modern format when it is supported by your platform and workflow.
- Use responsive image variants so a small phone does not download a large desktop asset.
- Lazy-load images below the initial viewport, but avoid delaying the primary image that establishes the page’s main content.
- Set width and height attributes or reserve space with CSS to reduce unexpected layout movement.
- Review background images, sliders, decorative videos, and image galleries separately; these are often overlooked.
For WordPress and other CMS sites
- Audit plugins and extensions for overlap, especially where several tools provide caching, image optimization, analytics, or page-building features.
- Keep the CMS, theme, plugins, and server software maintained according to a tested update process.
- Use page caching where appropriate and confirm that cached pages are refreshed after important content changes.
- Reduce database clutter, revisions, expired transients, and other unused records only with a reliable backup and a tested maintenance method.
- Check whether the page builder creates excessive markup or loads assets site-wide when they are needed on only one page.
If hosting is part of the problem, compare the limits and caching features of your current plan rather than choosing solely by introductory price. The guide to managed WordPress hosting versus shared hosting can help frame that decision, while the review of reliable cheap web hosting is useful when budget is the main constraint.
For landing pages and marketing campaigns
- Keep the first screen focused: limit large video backgrounds, animated effects, and unnecessary pop-ups.
- Load only the form, analytics, advertising, and consent scripts required for that campaign.
- Compress the hero image and verify that the call to action remains visible while the page finishes loading.
- Test the complete conversion path, including form submission, confirmation messages, and redirects.
- Use a fast, stable template and check its mobile behavior before duplicating it for additional campaigns.
What to double-check
Fonts: Limit font families and weights, preload only a font that is genuinely needed for the initial view, and use a sensible fallback so text remains visible while fonts load. Check for layout changes caused by different font dimensions.
Caching: Confirm that browser and server caching are configured intentionally. A cache that never refreshes can show stale content, while a cache that is bypassed by query strings or cookies may provide little benefit. After configuration changes, test logged-out and logged-in views separately.
Code and scripts: Minification can reduce file size, but it is not a substitute for removing unnecessary code. Defer or delay nonessential JavaScript only when it does not break navigation, forms, consent controls, or accessibility. Review third-party scripts because each external service can add DNS lookups, requests, processing, or layout changes.
Hosting and server response: Look for slow initial responses, intermittent failures, resource limits, and poor performance at busy times. A content delivery network can help serve static assets closer to visitors, but it must be configured with correct cache rules and HTTPS settings. A CDN will not fix an oversized page, slow database query, or inefficient application code by itself.
Testing: Compare results over more than one run. Network conditions, server load, cached assets, and testing location can affect lab results. Pair synthetic testing with real-user measurements when possible, and prioritize repeated issues on important pages over a single unusual score.
Common mistakes
- Optimizing only the score: A better score is useful, but a broken menu, delayed form, or unreadable page is not an improvement. Test the user journey as well as the report.
- Uploading original media: Large photographs, videos, and animated files can dominate page weight. Create a media-size rule for everyone who publishes to the site.
- Installing too many optimization tools: Multiple caching or compression systems can conflict and make troubleshooting harder. Keep one clearly configured solution where possible.
- Delaying every script: Aggressive script delay can improve a lab result while preventing analytics, consent, navigation, or interactive elements from working correctly.
- Ignoring fonts and layout space: Even a visually simple page can shift when fonts, ads, banners, or images load without reserved dimensions.
- Changing hosting too soon: Upgrading may help when the server is consistently limiting performance, but it should follow basic image, cache, code, and database checks.
- Never documenting changes: Without a baseline and change log, it is difficult to identify regressions or repeat successful fixes on other templates.
When to revisit
Run this checklist before major seasonal campaigns, product launches, redesigns, or publishing periods when traffic is expected to change. Revisit it after changing hosting, a CMS theme, a page builder, a CDN, image workflow, analytics setup, or consent system. New plugins and third-party embeds also justify a focused performance review.
For routine maintenance, review your most important templates on a regular schedule that fits your publishing volume. A monthly check may suit an active content site; a less frequently updated brochure site may need a review around each significant change. In either case, watch for gradual page growth rather than waiting for a visible outage.
Finish each review with three actions: fix the highest-impact issue, record what changed, and schedule a follow-up test. If performance remains poor after front-end cleanup, inspect server response time, database work, hosting resources, and CDN behavior. Then repeat the measurement on the same page types. This simple loop—measure, improve, verify, and document—keeps website speed optimization practical and prevents Core Web Vitals work from becoming a one-time launch task.
For a broader final review, combine this guide with the website launch checklist, especially when a new domain, template, or hosting environment is involved.