Fix a Slow Website: Find the Cause, Then Fix It

To fix a slow website, measure it first, find the one or two things causing most of the delay, fix those, and test again. Most slow sites for nonprofits, churches, farms and home service companies come down to oversized images, too many scripts, or a slow server. If you would rather never think about any of this, our monthly subscription bundles design, hosting and updates, and we handle every change for you.
This guide walks through the full process in plain language. You can follow it yourself, or hand it to whoever manages your site.
TL;DR
- Record a baseline first. Run a speed test, write down the numbers, and change one thing at a time so you know what worked.
- The usual culprits are large images, third-party scripts (chat widgets, trackers, embeds) and a slow server, in roughly that order of effort to fix.
- Aim for a server response (Time to First Byte) of 0.8 seconds or less, according to Google’s web.dev guidance.
- Test as a first-time visitor on a phone, because that is how many of your visitors arrive.
- If the cause is hosting, code or a pile of plugins, it is time to hand the site to someone who manages it for you.
Table of Contents
- Why a slow site costs you more than patience
- Step 1: Measure before you touch anything
- Step 2: Fix the biggest files first, usually images
- Step 3: Put the visible content first
- Step 4: Trim scripts, plugins and third-party add-ons
- Step 5: Check the server and hosting
- Step 6: Confirm the fix worked
- When to stop and get help
- Why a managed site avoids the problem
- What we offer
- Speed and what visitors do next
- FAQ
- Sources
Why a slow site costs you more than patience
A slow site is not just an annoyance. A person looking for a Sunday service time, a donation page, a farm stand’s weekend hours or an emergency plumber on their phone will not wait around. They go back to the results and pick the next option.
For each kind of organization the cost looks different:
- Nonprofits: a donation or volunteer form that takes too long to appear is a donor who never gives.
- Churches: first-time visitors check the site before they visit. A slow page is their first impression.
- Farms: seasonal events, pick-your-own days and online orders depend on visitors loading the page the moment they decide to go.
- Home service providers: people searching for a repair want to call or book now, and a page that stalls loses the job.
The good news is that speed problems are very diagnosable. They are rarely mysterious once you look at what the browser actually loads.
Step 1: Measure before you touch anything
The most common mistake is to start changing things without knowing what is slow. Google’s web.dev performance audit guide recommends establishing a baseline before changing anything, then testing, recording, fixing and repeating, so you can see whether each change helped or hurt.
Here is a simple way to do it.
- Pick your pages. Test your home page, plus the page that matters most: the donation page, the visit-us page, the events page or the booking page. A fast home page does not mean the rest is fast.
- Run a free speed test. Google’s PageSpeed Insights and Lighthouse (built into the Chrome browser) both give a report on load timings, file sizes and caching. The same audit guide suggests using these tools, including the real-world data from the Chrome User Experience Report that PageSpeed Insights shows when your site has enough traffic.
- Test like a first-time visitor. The audit guide advises testing in a private window or with caching disabled and storage cleared, because returning visitors have parts of your site saved in their browser and your own visits look faster than a new visitor’s.
- Test on a phone-like connection. Test on devices and connections that match your audience. Most local-search visitors are on phones, often on mobile data.
- Write the numbers down. Save the scores and the load time for each page in a note or spreadsheet. This is your baseline.
Find the slow part, not just the score
A score tells you that something is wrong. It does not tell you what. Cloudflare’s troubleshooting guide for slow websites says to identify which specific pages, files or API requests are slow, measure how slow, and reproduce the problem before choosing a fix.
You can do this in your browser:
- Open your page in Chrome, right-click, choose Inspect, and open the Network tab.
- Reload the page.
- Click the column that shows how long each request took and sort the list.
- Look at the top of the list.
Cloudflare’s guide suggests looking in particular for large images or videos, slow calls to other services, third-party scripts and files that block the page from displaying. If one 6 MB photo or one embedded video is at the top, you have found your first fix.
Step 2: Fix the biggest files first, usually images
Images are often the largest files on a page. Cloudflare’s guide to speeding up a website recommends reducing image dimensions and resolution and compressing image files for this reason.

This matters a lot for the kinds of sites you run. A church homepage with a hero photo straight from a phone camera, a farm gallery of harvest pictures, a nonprofit’s event photos and a contractor’s before-and-after shots are all typically uploaded at full camera size, several megabytes each.
What to do:
- Resize to the size it is shown. If the image displays 1200 pixels wide, a 4000-pixel original is wasted data.
- Compress it. Photos can usually be compressed substantially with little visible change.
- Use modern formats. MDN’s web performance article recommends WebP or AVIF with appropriately sized images.
- Load images below the first screen later. The PRPL pattern in web.dev’s guide to instant loading recommends lazy-loading noncritical assets, meaning images the visitor has not scrolled to yet do not slow down the first view.
For video, avoid autoplaying a large file in the page header. Embed it so that it loads only when someone presses play.
Step 3: Put the visible content first
Visitors judge speed by what they see, not by when the last file finishes loading. Google’s PageSpeed guidance on above-the-fold content recommends loading the content visible without scrolling first and deferring everything not needed for that first screen.
In practice, that means the headline, the main button (Donate, Plan Your Visit, Book Now, Call Us) and the key photo should arrive before the chat widget, the social feed and the footer map. If you are a home service business and want a deeper look at why that first screen matters for leads, this piece on local SEO for roofing companies covers how local searchers behave, and the same logic applies to plumbers, HVAC and electricians.
MDN’s speed guidance adds that performance is a user-experience question, including how fast the page feels, and not only a raw load-time number. A page that shows its main message quickly feels fast even if some extras load afterward.
Step 4: Trim scripts, plugins and third-party add-ons
Every script is extra work for the visitor’s browser. Cloudflare’s speed guide recommends limiting unnecessary HTTP requests, because each resource request adds a trip between the browser and the server. It also suggests removing unnecessary render-blocking JavaScript and external scripts, minifying CSS and JavaScript, and periodically removing unneeded redirects.
Small organizations pile up add-ons over the years. Make a list of everything your site loads and ask of each item: does someone actually use this?
| Common add-on | Typical slowdown risk | Question to ask |
|---|---|---|
| Chat widget | Loads its own scripts on every page | Does anyone use it? Does it need to be on every page? |
| Social media feed embed | Pulls in outside files and images | Could a simple link to your page do the job? |
| Several analytics or ad trackers | Multiple scripts firing at once | Do you read all those reports? |
| Slider or carousel | Loads several large images up front | Would one strong image do better? |
| Extra fonts | Each font style is another file | Can you use two weights instead of six? |
| Old plugins | Extra code, sometimes unused | Is it still needed after the last redesign? |
MDN’s best-practices guide says to keep JavaScript to the minimum the page needs and to use async or defer so scripts do not block the page from rendering.
Fonts
Custom fonts are a quiet cause of slow first views. MDN recommends using the font-display setting (swap, optional or fallback) so text shows right away in a backup font, and preloading a web font when the CSS would otherwise delay its discovery. If your site uses decorative fonts, ask the person who maintains it to check this.
Technical changes to leave to the builder
Some front-end changes are for a developer: tree-shaking and splitting code so noncritical JavaScript loads later, splitting long JavaScript tasks (over 50 milliseconds) or moving them to a Web Worker, and preloading critical resources, all listed in the MDN article above. You do not need to do these yourself. You need to know they exist so you can ask for them.
Step 5: Check the server and hosting
If your site is slow even after the images are trimmed, look at how fast the server responds. The HTML page has to arrive before the browser can discover and load anything else, so a slow first response delays everything after it.
The measure is Time to First Byte (TTFB): how long the browser waits before the first piece of the page arrives. Google’s web.dev recommends that most sites aim for 0.8 seconds or less. Cloudflare’s guide uses the same 800 millisecond target and advises checking the DNS, connection, security handshake and TTFB timings in the request details.
If TTFB is high on every page, the guide points to these likely fixes:
- more hosting capacity (the site is on a plan too small for its traffic);
- optimizing database queries (common on sites built on content management systems with many plugins);
- server-side caching, so the server does not rebuild each page for every visitor;
- a content delivery network (CDN), which serves copies of your pages from data centers near the visitor.
MDN also recommends HTTP/2, a CDN, and Brotli or gzip compression as standard good practice. These are settings on your hosting, not something most staff members should be editing.
This is also where cheap, shared hosting shows its limits. A host that crowds many sites on one server can respond slowly during busy times, such as a Sunday morning, a fundraising push or a farm’s opening weekend.
Step 6: Confirm the fix worked
Repeat the same tests you ran in Step 1, on the same pages, the same way, and compare. The web.dev audit guide’s loop of test, record, fix and repeat is how you catch both improvements and regressions.
Two kinds of data are worth knowing apart. Cloudflare’s guide explains that real-user monitoring reflects what your visitors’ actual browsers experienced, while lab tests like Lighthouse are better for debugging but may not match visitors’ devices and connections. Use the lab test to find the problem and real-user data (shown in PageSpeed Insights when available) to confirm that visitors feel the improvement.
A simple record to keep:
| Page | Test date | Load time | TTFB | What changed |
|---|---|---|---|---|
| Home | Before | Baseline | ||
| Home | After | Images resized | ||
| Donate / Visit / Book | Before | Baseline | ||
| Donate / Visit / Book | After | Removed chat widget |
Change one thing at a time where you can. If you change five things and the page is faster, you will not know which one mattered. If it gets slower, you will not know which to undo.
When to stop and get help
You can handle image resizing and removing unused add-ons yourself. Hand the problem to a professional when:
- TTFB is slow on every page, which points to hosting or server configuration;
- the site depends on many plugins and every update breaks something;
- the Network tab shows large scripts that you do not recognize;
- you have fixed the obvious items and the scores barely move;
- nobody on staff has the time to keep checking, which is the most common reason sites slow down again.
That last point matters most. Speed is not a one-time project. Every new event photo, embedded form and tracking tool adds weight. A site that was quick at launch drifts slower as people add to it. Our guide to website content management for small organizations covers how to keep updates from piling up that way.
Why a managed site avoids the problem
Most slowdowns come from the day-to-day: someone uploads a large photo, someone adds a plugin, nobody watches the hosting. The simplest way to avoid that cycle is to remove the need for staff to touch the site at all.
We build websites for nonprofits, churches, farms and home service businesses, and the pattern we see in the brief is always the same: the people running the organization are busy running the organization. Nobody has time to audit file sizes.
That is why we set up our service the way we did. Design, hosting and monthly updates come in one subscription, and you never have to manage a dashboard or make updates yourself. All changes are handled by us, so the person adding a new event does not need to know what a render-blocking script is.
A site is also easier to keep clean when the same team that designed it hosts it and updates it. There is one place to look when something feels slow, and one team accountable for fixing it, with no surprise bills when it happens.
Speed is part of how a website serves the people who visit it. We would rather you spend your time on your congregation, your donors, your harvest or your customers.
Grayson
What we offer
Our plans bundle custom design, hosting and monthly updates, with sites built for your sector. Published monthly pricing is $29 for Launch, $99 for Growth, $199 for Systems and $399 for Scale. Church plans are also offered with annual pricing: $319, $1,089, $2,189 and $4,389 per year respectively, on our church website page. Marketing sites can go live in as little as two days.

If your current site is slow and you would rather have it rebuilt and managed than patched, see the plans on our main page or book a call. We also have sector pages for nonprofits, farms and orchards and home service businesses.
Speed and what visitors do next
Speed matters because of what it lets visitors do: give, sign up, find the service time, book a visit, call for a repair. Once the site loads quickly, the next question is whether visitors take that action. Our guide on calculating and improving your site conversion rate picks up from here. If your main worry is being found in the first place, read about local business visibility, or, for congregations, SEO for churches.
FAQ
How fast should my website load?
There is no single magic number, but a good server response is 0.8 seconds or less to the first byte, per Google’s web.dev guidance. After that, what matters is that the main content and your key button appear quickly on a phone. Test your most important page as a new visitor and compare against your own baseline over time.
What is the quickest fix for a slow website?
Compress and resize your images. Images are often the largest files on a page, so shrinking an oversized hero photo or gallery usually gives the biggest gain for the least effort. Removing add-ons nobody uses, such as an old chat widget or social feed, is the next quickest.
Why is my site slow even though my internet is fast?
Your connection is only one part. The delay can come from the server taking too long to respond, from large files, or from scripts that block the page. Open the Network tab in your browser, reload the page and sort by duration to see which request takes longest.
Do I need a developer to fix it?
Not always. Resizing images and removing unused add-ons are things staff can do. If the server response is slow on every page, or the site relies on many plugins that break when updated, a professional who manages the site and hosting can fix the cause. With our subscription, that work is part of the service.
Sources
- Audit performance, web.dev
- Troubleshooting a slow website, Cloudflare Speed docs
- Tips to improve website speed, Cloudflare
- Reduce the size of the above-the-fold content, Google PageSpeed Insights
- Monitoring and optimizing website performance, MDN
- Web Performance best practices and tips, MDN
- Optimize Time to First Byte, web.dev
- Apply instant loading with the PRPL pattern, web.dev