Website Speed Optimization — 14 Proven Fixes
Most websites can load 40-60% faster with three fixes: better hosting (NVMe+LiteSpeed), image optimisation, and caching. This guide covers 14 fixes ranked by impact.
Most websites can load 40-60% faster with three fixes: better hosting (NVMe+LiteSpeed), image optimisation, and caching. Start with hosting because a slow server makes every other optimisation less effective. This guide covers 14 fixes ranked by real-world impact so you can prioritise what moves the needle.
Why speed matters
Website speed directly affects revenue, user satisfaction and search rankings. These numbers explain why website speed optimization should be a priority:
| Metric | Impact | Source |
|---|---|---|
| 1 second delay | 7% reduction in conversions | Akamai |
| 3 second load time | 53% of mobile visitors leave | |
| 0.1s improvement | 8% increase in retail conversions | Amazon |
| Pass Core Web Vitals | Ranking boost in search results |
Beyond the metrics, a fast site builds trust. Users perceive fast-loading sites as more professional and more credible.
How to measure current speed
Before optimising, measure. Use these free tools to get your baseline:
- PageSpeed Insights — Google's official tool. Gives you a score plus Lab Data and Field Data for Core Web Vitals.
- GTmetrix — Detailed waterfall charts showing exactly which resources take longest.
- WebPageTest — Advanced testing from multiple locations and connection speeds.
- Chrome DevTools — Built into the browser. The Network and Lighthouse tabs are enough for most diagnostics.
Run three tests at different times of day and take the median. One-off tests can be misleading. For more on the first meaningful metric, read what is TTFB.
14 fixes ranked by impact
These fixes are ordered by how much they typically improve load times, starting with the biggest wins.
- 1. Upgrade hosting to NVMe + LiteSpeed. This alone cuts TTFB by 40-60%. Old HDD hosting or Apache without caching is the single biggest bottleneck. A modern stack makes every other optimisation more effective.
- 2. Optimise and serve next-gen images. Convert JPEGs to WebP or AVIF. Compress aggressively (80-85% quality is usually indistinguishable). Reduce dimensions to actual display size. This cuts image weight by 50-80%.
- 3. Implement page caching. Serve static HTML copies to first-time visitors. LiteSpeed Cache (LSCache) is the most effective for WordPress. Browser caching with far-future expiry headers for static assets also helps returning visitors.
- 4. Minify CSS, JavaScript and HTML. Remove whitespace, comments and unused code. Combine CSS files where possible. This reduces render-blocking resources.
- 5. Defer non-critical JavaScript. Load above-the-fold JS first and defer everything else with the
deferorasyncattribute. This prevents JS from blocking page rendering. - 6. Enable Gzip or Brotli compression. Compress text-based assets (HTML, CSS, JS) before sending them to the browser. Brotli is more efficient than Gzip and supported by all modern browsers.
- 7. Use a CDN. Serve static assets from servers geographically closer to your visitors. This is especially important if your audience is international. Learn more in what is a CDN.
- 8. Eliminate render-blocking resources. Move critical CSS inline and defer non-critical CSS. Tools like Critical CSS generators automate this process.
- 9. Optimise the critical rendering path. Structure HTML so above-the-fold content loads first. Inline small CSS and JS that is needed for initial paint.
- 10. Reduce server response time (TTFB). A TTFB under 200ms is the target. This requires fast hosting, PHP optimisation, database indexing and a caching layer. See what is TTFB for details.
- 11. Lazy load images and embeds. Load below-the-fold images and iframes only when they are about to enter the viewport. The native
loading="lazy"attribute handles this without JavaScript. - 12. Optimise fonts. Self-host fonts instead of loading from Google Fonts. Subset fonts to only include characters you need. Use
font-display: swapto prevent invisible text during load. - 13. Reduce database queries. One uncached WordPress page can execute 20-50 database queries. Caching, query optimisation and indexing reduce this to single digits.
- 14. Audit plugins and third-party scripts. Each plugin or embedded script (analytics, maps, chat widgets) adds HTTP requests and JavaScript execution time. Remove anything that is not essential.
Core Web Vitals targets
Google's Core Web Vitals are the three metrics that matter most for both SEO and user experience. These are the targets:
| Metric | What it measures | Good target |
|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed of the main content | Under 2.5 seconds |
| INP (Interaction to Next Paint) | Responsiveness to user input | Under 200 milliseconds |
| CLS (Cumulative Layout Shift) | Visual stability during load | Under 0.1 |
Fixes 1-3 above (hosting, images, caching) typically get most sites to pass LCP. CLS is usually fixed by setting explicit width and height on all images and embeds. INP improves with JS deferral and reduced third-party scripts. See our dedicated guide on core web vitals explained.
Hosting impact on speed
Hosting is the foundation of website speed. No amount of front-end optimisation can compensate for a server that responds slowly. Here is how different hosting choices affect speed:
| Hosting type | Typical TTFB | Impact on speed |
|---|---|---|
| Shared hosting (NVMe + LiteSpeed) | 100-250ms | Fast — good for most sites |
| Shared hosting (HDD + Apache) | 400-1200ms | Slow — major bottleneck |
| VPS (properly configured) | 50-150ms | Very fast — dedicated resources |
| Managed WordPress (optimised stack) | 100-200ms | Fast — purpose-built |
If your current site is on outdated shared hosting, the quickest win is migrating to a provider that uses NVMe storage and LiteSpeed servers. Our shared hosting starts at BD 3.5 and uses exactly that stack. If you have outgrown shared hosting, shared hosting vs VPS helps you decide when to upgrade.
Frequently asked questions
Hosting. If the server is slow (old HDD, Apache without caching, overloaded neighbours), nothing you do on the front end will compensate. Moving to NVMe storage and LiteSpeed is the highest-impact single fix.
Image optimisation typically reduces page weight by 50-80% without visible quality loss. For image-heavy pages this can cut load time by 2-4 seconds on mobile connections.
A caching plugin helps, but it is only effective if the server supports it properly. LiteSpeed + LSCache is the most effective combination. A caching plugin on Apache without server-level cache is far less impactful.
Core Web Vitals are Google's three speed metrics: LCP (loading), FID/INP (interactivity) and CLS (visual stability). They are a ranking factor and directly impact user experience. Poor vitals mean higher bounce rates.
Basic optimisation can be done in a few hours. Full optimisation including server migration, image pipelines and code refactoring takes 1-3 days depending on the site size.