How to Speed Up a Slow Website: A Beginner's Effort Checklist

Most slow websites are not failing because of complex backend code or server architecture. They are dragging because someone uploaded a 6-megabyte photo directly from a phone onto a page that only needed a small thumbnail.

Before changing a single file or paying for speed plugins, you need to fix problems in the order that gives you the biggest performance boost for the least amount of work.

Measure your baseline with free diagnostic tools

You cannot fix what you do not measure, but running tests repeatedly without understanding the output will just waste your afternoon.

Google PageSpeed Insights gives you two types of information: lab data and field data. Lab data simulates a visitor on a throttled mobile connection, while field data aggregates real user performance over the last month using metrics like Largest Contentful Paint (LCP) and Interaction to Next Paint (INP).

WebPageTest takes a different approach by generating a visual waterfall chart. That chart shows every single file your website requests in chronological order, revealing exactly which image, script, or font is stalling the page load.

Run both tools on your homepage and your primary lead page before making any edits. Save those baseline reports so you can compare real progress instead of guessing whether a change made a difference.

Resizing oversized images provides the biggest immediate win

Image optimization is almost always the highest-payoff task on any website speed checklist. A modern smartphone takes pictures that are thousands of pixels wide and several megabytes in size, which causes massive slowdowns on mobile networks.

If your layout displays an image at 800 pixels wide, uploading a 4000-pixel image forces your visitor’s phone to download millions of useless bytes before scaling it down on screen.

Start by resizing your photos to their actual display dimensions before uploading them. Next, convert JPGs and PNGs into modern web formats like WebP or AVIF, which routinely cut file sizes down significantly without visible quality loss.

Free tools like Squoosh or bulk image compression plugins can handle this in minutes across your entire media library. On a cluttered small business homepage, optimizing hero banners and gallery images often removes more page weight than every other technical tweak combined.

Page caching eliminates unnecessary database calls

Every time a visitor opens an un-cached page on a dynamic site like WordPress, your web server has to run database queries, execute PHP scripts, and stitch together HTML code from scratch. Doing that for every single visit drags down server performance.

Page caching creates a pre-built static HTML version of your page the first time it loads. When the next visitor arrives, your server delivers that saved static file instantly without touching the database.

Most modern hosting control panels include built-in server-level caching that you can turn on with a single toggle. If your host does not provide server-level caching, lightweight caching plugins can set up browser caching headers and static file storage for you.

Here is the trade-off to keep in mind: caching can occasionally serve older content after you edit a page. Whenever you make design or text updates, remember to clear your cache so visitors see the newest version.

Removing extra plugins and tracking scripts restores browser responsiveness

Every tracking pixel, live chat widget, custom font, and extra plugin you add adds JavaScript that your visitor’s browser must download, parse, and execute.

Even if your server sends the page quickly, heavy JavaScript blocks the browser from making the page interactive. Visitors tap buttons or try to scroll, but the page freezes until the script finishes running.

Auditing your script stack requires being brutal about what actually drives business value. Disable plugins you are not using, remove old analytics pixels from marketing tests you finished six months ago, and load non-essential scripts asynchronously so they do not block the initial page render.

When I audited my own site’s code, I deleted one library and cut mobile blocking time by 500ms without changing how the page looked to visitors.

Cheap shared hosting places a firm ceiling on your speed

If you have compressed your images, enabled caching, and trimmed your plugins, but your site still takes over two seconds just to respond, your web server is likely the bottleneck.

On budget shared hosting, your website shares CPU cores, memory, and disk access with hundreds of other sites on the same physical machine. If a neighboring site gets a sudden surge in traffic, your site’s response time suffers regardless of how clean your code is.

You can spot a host bottleneck in your WebPageTest results by looking at Time to First Byte (TTFB). If TTFB is consistently long, your server is taking too long to start sending data back to the browser.

Moving to a managed host, a virtual private server, or an edge platform requires migration effort, but it fixes the foundational delay that no plugin can solve. If you are comparing your options, I broke down the trade-offs in my guide on what web hosting actually does for a small business.

Your 20-minute site speed action plan

Do not try to fix everything at once. Work down this checklist in order to get the highest speed gains with the least friction:

1. Test baseline: Run your URL through PageSpeed Insights and WebPageTest; save the reports.
2. Compress media: Downscale images to max display size and convert them to WebP or AVIF.
3. Turn on caching: Enable page caching through your host dashboard or a caching plugin.
4. Audit scripts: Deactivate unused plugins and remove inactive tracking pixels.
5. Re-test page: Run your speed tests again to verify your improvements against your baseline.