How to speed up your website (Core Web Vitals for solos) (2026)

A slow website quietly taxes everything you do. It costs you visitors who bounce before the page paints, it costs you the conversion of the ones who stay, and it costs you a little ranking ground against faster competitors. The good news for a solo: speed is one of the most fixable parts of a site, and the highest-impact fixes need no developer. This is the practical version — what to fix, in what order, and when to stop. It pairs with the technical SEO checklist for a solo site and sits inside the wider SEO for solopreneurs playbook.

Why speed matters — for rankings and revenue

Two separate reasons, and the second is the bigger one.

For SEO, page experience including Core Web Vitals is a confirmed ranking signal — a modest one. Great content on a slightly slower page can still rank, but between two comparable pages, the faster, steadier one tends to win. It matters most on mobile, where most searches happen and where a page that flies on your desktop fibre can crawl on a phone over patchy 4G.

For conversions, the effect is blunter. A visitor who waits too long simply leaves — and they leave before they’ve read your headline, seen your offer or had any chance to be persuaded. Every hundred milliseconds you trim is a few more people who actually arrive. That’s why speed pays even on pages that don’t depend on search traffic.

Core Web Vitals in plain English

Google distils “how fast does this feel” into three measurable things. Learn these three and you understand most speed advice you’ll ever read.

• LCP — Largest Contentful Paint (loading). How quickly the main content — usually the hero image or headline — appears. This is “how long until the page looks ready.” Big uncompressed images are the usual villain here.
• INP — Interaction to Next Paint (responsiveness). How fast the page reacts when someone taps a button, opens a menu or types. A page can look loaded but freeze on the first tap — that’s a heavy-script problem.
• CLS — Cumulative Layout Shift (stability). Whether the layout jumps as things load — the classic “you go to tap a link and an ad shoves it down.” Caused by images and embeds without reserved space, and by fonts swapping in late.

The fixes that move the needle most

You don’t need to do everything. A handful of changes account for most of the gain on most solo sites, and none of them require code.

• Optimise and compress images. This is the single biggest win. Export images at the size they actually display (a 4000px photo in a 800px slot is pure waste), compress them, and use a modern format like WebP. One bloated hero image can outweigh the entire rest of the page.
• Lazy-load below-the-fold media. Tell the browser to load images and embeds only as the visitor scrolls to them, so the initial paint isn’t waiting on things nobody has seen yet. Most platforms do this automatically now — confirm yours does.
• Get a fast host and a CDN. Cheap, overloaded shared hosting adds latency to every request. A reputable host plus a CDN (which serves your files from a location near each visitor) lifts the whole site’s baseline. This is a buy-it-once decision that keeps paying off.
• Cut scripts and heavy plugins. Every analytics tag, chat widget, font loader, embed and “nice to have” plugin is weight — and third-party scripts are the usual cause of poor INP. Audit honestly and delete what you don’t truly need.
• Turn on caching. Caching serves a ready-made version of your page instead of rebuilding it on every visit. Most CMSs offer it via a setting or plugin; static-built sites get much of it for free.

Build light from the start

The cheapest speed is the speed you never have to claw back. The fastest sites tend to be the ones that were built lean, not the ones that bolted on optimisation later.

• A lightweight theme or a clean build. A bloated multipurpose theme stuffed with sliders, page-builders and demo content ships kilobytes you’ll spend months trying to remove. A simple, well-built theme — or a static build that outputs minimal HTML, CSS and JavaScript — starts fast and stays fast. This is part of choosing your stack well in the first place, which the build a website solo guide walks through.
• System or self-hosted fonts. Web fonts pulled from a third party are a sneaky drag: an extra connection, a download, and often a layout shift as the text re-renders (hurting CLS). Using the visitor’s system fonts costs nothing and renders instantly; if you want a custom font, self-host it so it loads from your own fast server.

How to measure — and when to stop

You only need two free tools, and they answer different questions.

• PageSpeed Insights. Paste a URL and it gives you a lab score plus, where available, real-world field data and specific, prioritised suggestions (“properly size images”, “reduce unused JavaScript”). Use it as your diagnostic — it tells you what to fix and where the weight is. Check the mobile tab first.
• The Core Web Vitals report in Search Console. This is your scoreboard — real visitors, grouped into good / needs improvement / poor, across your whole site rather than one page at a time. It’s the honest ground truth, and it’s covered as part of using Search Console as a solo.

Then the discipline that saves solos hours: stop at “good”. The returns on speed drop off sharply once you’re in the green. Going from a slow page to a fast one is transformative; going from a fast page to a perfect-100 page is usually hours of effort for a gain no human will feel — and it often means fighting your own platform. Pass Core Web Vitals on mobile, confirm it in the field, and redirect that energy into content and offers, which move the business far more. Speed is a foundation, not the whole house — get it solid, then go win the page itself.

The takeaway

• Speed is two wins in one — a modest ranking signal and a real conversion lever — and it matters most on mobile.
• Learn the three vitals: LCP (loading), INP (responsiveness), CLS (stability).
• Fix images first — compress, size correctly, use WebP, lazy-load. It’s the biggest payload and the easiest fix.
• Then trim the rest: a fast host plus CDN, fewer scripts and heavy plugins, caching on, a lightweight theme or clean build, and system or self-hosted fonts.
• Measure with PageSpeed Insights (diagnostic) and Search Console (scoreboard) — and stop at “good” rather than chasing a perfect score that nobody can feel.

Get the speed foundation right once and it keeps paying off while you focus on the parts that grow the business. It’s one line in the wider technical SEO checklist — but it’s the line your visitors feel first.

Part of the complete SEO for solopreneurs guide.

Part of the complete SEO for solopreneurs guide.