Google Search Console sent an email saying your site has "poor" Core Web Vitals on mobile, with a count of affected URLs. Or a web designer quoted a rebuild and pointed at a PageSpeed score of 31 as the reason. Either way, you are looking at three abbreviations and a red bar and trying to work out whether this is a real problem or a sales pitch.
Core Web Vitals are Google's chosen measurements of how a page feels to a real person: how long until the main thing appears, how quickly the page reacts when tapped, and whether things jump around while it loads. They are one ranking input among many, and for a law firm the honest framing is that bad scores hurt a little, good scores do not win rankings on their own, and the person waiting on a slow page is a prospective client who may just call the next firm.
Reading the report in Search Console without a developer
Open Search Console, then Core Web Vitals under Experience. You get two reports, mobile and desktop, and each groups your URLs into Good, Needs improvement and Poor. Click into a status and Search Console shows which metric failed and a group of example URLs that share the same template, because pages built from one template usually fail together.
The numbers come from the Chrome User Experience Report, which is real Chrome users visiting your site over the previous 28 days. That has two consequences. A page needs enough traffic before Google has data on it at all, so a small firm may see "not enough data" on most pages. And fixes take up to 28 days to show as passing, because the old visits are still in the window.
LCP, INP and CLS in plain terms
Largest Contentful Paint is how long until the biggest visible element on the screen, usually your hero image or headline, has finished rendering. Google wants it under 2.5 seconds. On law firm sites the biggest element is almost always a large photo of the attorneys or the courthouse, and that photo is often a 4 MB file straight off a camera.
Interaction to Next Paint measures how long the page takes to respond visibly after someone taps or clicks. The threshold is 200 milliseconds. High INP usually comes from JavaScript: chat widgets, consent banners, tracking scripts and page builders all competing for the phone's processor while the visitor is trying to tap "Call now."
Cumulative Layout Shift measures how much the page moves after it starts showing. The target is 0.1 or below. The classic law firm version is a phone number that shifts down when a top banner or an ad-style review badge loads late, so the visitor taps the wrong thing.
Why PageSpeed Insights and Search Console disagree
Run a URL through PageSpeed Insights and you see two sections. The top, "Discover what your real users are experiencing," is the same field data Search Console uses. Below it is a Lighthouse lab test run once from a Google server on a simulated slow phone. The lab score is the number designers quote, and it can be 30 points lower than what your visitors actually experience.
The field data is what counts for search. Use the lab test for diagnosis, because it lists the specific images, scripts and fonts that are slowing things down, but do not panic over a lab score if the field data says Good.
The usual culprits on law firm sites, in the order we fix them
Images first. Resize hero photos to the size they display at, export as WebP or AVIF, and set explicit width and height attributes so the browser reserves the space (that also fixes most CLS). Most WordPress hosts and plugins like ShortPixel or Imagify can do this in bulk.
Third-party scripts second. Make a list of every script the site loads: chat, call tracking, heat mapping, Facebook pixel, multiple analytics tags, embedded video. Each one should justify itself. The ones that stay can usually be deferred so they load after the main content.
Fonts third. Self-host the two font files you actually use, and set font-display: swap so text shows immediately in a fallback font rather than staying invisible while the custom font downloads.
Hosting last, but not least. If the server takes 800 milliseconds to send the first byte, no front-end tuning will get LCP under 2.5 seconds. Moving from a shared plan to a managed WordPress host or adding a CDN is often the single biggest LCP improvement. Our site speed optimization page covers the hosting question in more detail.
Where Core Web Vitals sit in the bigger picture
Speed is one branch of technical SEO for law firm websites, and technical SEO is one part of a full law firm SEO audit. If your practice-area pages are thin and you have eleven reviews, passing Core Web Vitals will not get you into the map pack. If everything else is sound and the site is slow on phones, fixing it is one of the cheaper wins available.
A fast, uncluttered site pays off beyond Google too. AI crawlers fetching your pages to answer questions get clean HTML they can parse, which is the same principle behind publishing an llms.txt file for them. The whole SEO for lawyers program benefits when the site simply loads.
Questions we get
Our score is "Needs improvement." Is that worth fixing?
Usually yes, if the fix is images and scripts, because that is a day of work. If getting to Good requires a new theme, weigh it against what else the budget could do. Needs improvement is not a penalty; it is a nudge.
Will a new website automatically pass?
Only if it is built with speed in mind. We have seen brand new sites with worse Core Web Vitals than the ones they replaced, because the designer used a heavy page builder and full-screen video. Ask for the PageSpeed field data of the developer's last three law firm sites before signing.
How do we know the fix worked?
Rerun PageSpeed Insights immediately for the lab view, then watch Search Console over the following four weeks as the 28-day window rolls over. Set a reminder; nobody remembers to check on their own.
If you want someone to read your report and tell you which of the three metrics is actually costing you clients, tell us what you are working with.