Someone just got rear-ended on a Tuesday afternoon. They are sitting in their car with a sore
neck, searching for a lawyer on their phone, on one bar of signal. Your site comes up. They tap it. Nothing
happens for a few seconds, so they hit back and tap the next firm.
That is what a slow website costs. Not a ranking position. A phone call you never knew about.
Key Takeaways
- Google’s benchmark for a good load is 2.5 seconds or less on mobile.
- Speed is a real ranking factor, but a modest one. It mostly decides close calls.
- The bigger loss is visitors who leave before the page appears.
- Test with PageSpeed Insights and read the mobile numbers first.
- Big images, extra plugins, and cheap hosting cause most of the problem.
Where the 2.5 seconds comes from
Google measures three things about how a page feels to use, and calls them Core Web Vitals. The one people
talk about most is Largest Contentful Paint: how long until the main image or block of text actually shows up.
Under 2.5 seconds is rated good. Between 2.5 and 4 seconds needs improvement. Over 4 seconds is poor.
The other two cover how quickly the page responds when someone taps, and whether things jump around while
it loads. That last one is why a visitor sometimes taps your phone number and gets a cookie banner instead.
How much it moves your ranking
Less than most people selling speed work will tell you. Google has been clear that relevance wins: a slow
page with the right answer still beats a fast page with the wrong one. Speed acts as a tiebreaker between
pages that are otherwise close, and it counts for more on mobile searches, which is where most legal searches
happen.
So treat it as maintenance rather than a growth strategy. It protects the traffic your content earns
instead of creating new traffic on its own.
Do this today
Open Google PageSpeed Insights, run your home page, your busiest
practice area page, and your contact page, and look only at the mobile tab. Write down the load time for each.
Five minutes of testing tells you whether this is a real problem for your firm or a distraction.
What usually slows a small firm site
The causes are boring and repeatable. In the sites we look at, it is almost always some mix of these:
- Photos uploaded straight off a camera or phone. A 4 MB hero image is the single most
common cause. The same picture at the right dimensions is often a tenth of the size. - Plugins nobody uses anymore. Every active plugin can add its own scripts and styles to
every page, including the ones it has nothing to do with. - Page builder overhead. Builders load a lot of shared code up front. That is a fair trade
for easy editing, but it means the rest of the page has less room to spare. - Chat widgets, tracking tags, and embedded video. Each one is a request to somebody
else’s server, and your page waits on it. - Shared hosting at the bottom of the price list. When the server is slow to answer, no
amount of front-end tuning fixes it.
Fonts belong on that list too. Three font families with several weights each is a surprising amount of
download for something a reader never notices.
Worth knowing
PageSpeed Insights gives you two different things. The top
section, when it appears, is data from real visitors over the last 28 days. The score below it is a lab
simulation on a throttled connection. The real-visitor numbers are the ones Google uses, so start there and
treat the score as a to-do list.
A fix order that makes sense
- Compress and resize the images on your top five pages. This alone solves many sites.
- Turn on a caching plugin, or confirm your host already handles caching.
- Deactivate and delete plugins you are not using, one at a time, with a backup in place.
- Cut the number of fonts and weights to what the design actually shows.
- Remove any tracking tag or widget you cannot name a purpose for.
- Retest after each step so you know which change did the work.
- If the server response time is still high after all of that, the host is the problem.
Retesting matters more than it sounds. Without it you end up guessing, and guessing is how firms spend a
few thousand dollars on a rebuild that was never needed.
When to stop optimizing
A perfect score is not the goal. Getting your main pages under 2.5 seconds on a phone, with a contact form
and a click-to-call button that work on the first tap, covers what matters to a client. Past that point, your
time is better spent on the pages themselves and on your local listing.
Kevin Brown Design
Not sure if your site is fast enough?
We work with small law firms on websites and local search. Send us
your firm’s address and we will test your key pages on mobile and tell you what is slowing them down and what
it would take to fix.
Frequently Asked Questions
How fast does my law firm website need to be?
Google’s own benchmark is 2.5 seconds or less for the largest piece of content on the screen to appear. That measure is called Largest Contentful Paint, and it is one of the three Core Web Vitals Google reports on. Anything past four seconds is treated as poor. The target applies to real visitors on real phones, not to a test run on your office fiber connection.
Does site speed really affect my Google ranking?
It is a small factor, not a big one. Relevance, local signals, and links still decide most of the outcome. Speed works more like a tiebreaker between pages of similar quality, and it carries more weight on mobile. The bigger effect is on people: a visitor who waits too long leaves before your phone number ever loads.
How do I test my own site?
Open Google PageSpeed Insights, paste in your page address, and read the mobile tab first. Test your home page, your main practice area page, and your contact page, since they are often built differently. If Google has enough traffic data for your site, the top section shows what actual visitors experienced over the past month, which matters more than the simulated score below it.
What usually makes a small firm site slow?
Oversized images are the most common cause, followed by too many plugins, a page builder loading scripts it does not need, chat widgets and tracking tags, and shared hosting that is stretched thin. Fonts and video backgrounds add up too. Most sites we look at have three or four of these at once rather than one dramatic problem.
Is a slow site a reason to rebuild from scratch?
Usually not. Image compression, caching, trimming unused plugins, and a better host fix most of it without touching the design. A rebuild makes sense when the theme itself is bloated or the site is old enough that it needs work anyway. Get it measured first so the decision is based on numbers instead of a hunch.
Last reviewed September 18, 2026 by Kevin Brown.