Website speed is a kindness before it is a ranking factor

The state your visitors arrive in

Nobody browses funeral home websites at leisure. They arrive from a hospice hallway, a highway shoulder, a kitchen table at dawn — on a phone, often on one bar of signal, often on the older phone that has ridden in a coat pocket for three years. A homepage that takes eight seconds because of a hero video and three tracking scripts is, to that person, a door that would not open.

Picture the actual hand holding the phone. A son has stepped out of the room where his mother just died, into a corridor with bad reception, and typed your town’s name and the word “funeral” because he does not know what else to do. He is not evaluating your photography. He is looking for a phone number and a feeling — that whoever answers will know what to do, because he does not. In that moment a page is not a brochure. It is the first thing your funeral home says to him, and it is saying it while he waits.

What he sees while he waits is the whole message. A white screen with a spinner says not yet. A video that begins to play — sound on, in a silent corridor — says we were not thinking of you. A page that appears at once, with the number large and the address plain, says we are here, and this is simple. He will not put those reactions into words. He will simply call the funeral home whose page felt like an answer, and the load time decided which home that was before he read a single sentence.

What slow costs you now

The mechanical costs are real, and worth naming plainly. Google’s page-experience signals take into account how quickly a page loads on a phone; a slow site is quietly placed below a faster one offering the same thing. Crawlers give less attention to pages that make them wait, so your newest obituary — the page you most want found this week — is indexed later. And the engines that fetch pages live to compose an answer, ChatGPT and Perplexity among them, give up on a page that stalls and quote a faster one, however good the writing underneath. If you are working toward being the answer an AI gives, speed is the quiet precondition — a page that cannot load in time cannot be quoted at all.

But the mechanical costs are not the headline. The headline is the family that closed the tab. They did not file a complaint or leave a review; they saw a spinner, felt the small refusal in it, and called the funeral home whose page simply appeared — often the corporate group two towns over, with a fast, templated site and none of your care. You lost that call before your own homepage finished loading, to a competitor who is worse at everything except this one thing. That is the cost that shows up in no report, and it is the expensive one.

The funeral home speed budget

Think of your page as having a budget — a few seconds, a few hundred kilobytes over a weak connection — and every element on it spends from that budget. You do not need a web engineer’s toolkit to stay inside it. You need restraint, and a clear sense of what each decoration is costing you.

The heaviest items are almost always the ones added to impress:

• An autoplaying hero video. A two-minute drone shot of the building is, by itself, larger than every word and photograph on the rest of the site combined — and the family did not come to watch the building. Replace it with one real photograph.
• A rotating slideshow. A carousel loads a dozen large images to show one at a time. Choose the single best photograph and let it be still.
• Third-party widgets — chat bubbles, popups, social feeds, review carousels. Each fetches its own code from somewhere else, on its own schedule, and any one of them can hold the whole page hostage while it loads.
• Photographs straight from the camera. A phone photo is several megabytes; the same image sized for the web is a few hundred kilobytes and looks identical on screen. Nobody should download a print-resolution chapel photo in order to read on a phone.
• PDF obituaries. A family on a phone should never wait for a whole document to open in order to read one name. Publish the obituary as text with a modest photograph — faster, and something an answer engine and a search page can actually read. Your obituary page is your most important page; it should also be your lightest.

Here is the whole method in one before-and-after. Before: a homepage that opens with a video, cycles a slideshow of the grounds, floats a chat bubble, and embeds a live social feed. After: one photograph of the front entrance, the phone number large enough to tap, the address, a single line saying the phone is answered at any hour, and a clear link to the obituaries. The second page finishes loading before the first has finished measuring itself — and it says everything the family needed to know. Most funeral home sites are slow from decoration, not from content, and the decoration is not what families came for.

The test that matters

There are tools that will hand you a number — Google’s PageSpeed Insights will grade your homepage as a phone sees it and name the slowest element for you, usually the one you already suspected. Run it; it is free, and it tells you where to cut first. But the number is not the test.

The test is this: take the oldest phone in the office, turn off the Wi-Fi so you are on cellular like everyone else, walk out to the parking lot where the signal is honest, and load your own site. Count the seconds from tap to the moment you could actually read the number and place the call. Count them the way the family counts them — while waiting, at the worst hour of their year.

That count is the experience you are offering at the hardest moment someone will have. You answer your phone on the first ring because a family in that state should not have to wait through a second one. Your website is the same phone, held by the same hand, and it should open just as quickly — like being answered on the first ring.