Cites Google

Core Web Vitals: Why Your Nashville Law Firm Site Feels Slow

5 min read

  • 5 sections
  • 1 table
  • 7 sources cited

“The site feels slow” can mean three different problems: the main content takes too long to appear, the page does not react when someone taps, or the layout jumps while it loads. Core Web Vitals give each one a number. Google’s web.dev guidance sets the targets: “LCP should occur within 2.5 seconds of when the page first starts loading,” “pages should have a INP of 200 milliseconds or less,” and pages “should maintain a CLS of 0.1” (web.dev on Web Vitals). The thresholds are the same for a Nashville firm as for any site; what differs is which pages matter most, and for a law firm those are the practice pages where people decide whether to call. Finding out which of the three those pages fail, on real visitors’ phones, is the first step; the fix depends on the answer.

The Three Metrics and What Each One Catches

Metric What it measures Good threshold
Largest Contentful Paint (LCP) When the largest image, text block or video in view is rendered 2.5 seconds or less
Interaction to Next Paint (INP) How long the page takes to respond visibly after a tap, click or key press 200 milliseconds or less
Cumulative Layout Shift (CLS) How much visible content moves unexpectedly 0.1 or less

Each threshold is judged at “the 75th percentile of page loads, segmented across mobile and desktop devices.” The check is made metric by metric: LCP passes if at least three out of four page loads meet the LCP target, INP if three out of four meet the INP target, and so on, and the page passes the assessment when all three metrics pass on their own.

LCP is about rendering, not downloading: it “reports the render time of the largest image, text block, or video visible in the viewport, relative to when the user first navigated to the page” (web.dev on LCP). A hero image that has downloaded but waits on a slow script to be painted still counts against LCP.

CLS is not limited to the first seconds of loading. web.dev describes it as a measure of “every unexpected layout shift that occurs during the entire lifecycle of a page” (web.dev on CLS), so a consultation banner or chat bubble that pushes content down after the visitor has started reading counts too.

INP became a Core Web Vital on March 12, 2024. The web.dev announcement says “Interaction to Next Paint is now a stable Core Web Vital metric, replacing First Input Delay” (web.dev INP launch post). Reports and agency audits that still discuss FID are describing a metric Google no longer uses as a Core Web Vital.

Why PageSpeed Insights Can Leave INP Blank

PageSpeed Insights shows two different kinds of data, and a law firm’s practice page may not have one of them.

The field data at the top comes from real Chrome users. Google’s PSI documentation says “A page might not have sufficient data if it has been recently published or has too few samples from real users.” When that happens, “PSI will fall back to origin-level granularity, which encompasses all user experiences on all pages of the website,” and sometimes “the origin may also have insufficient data, in which case PSI will be unable to show any real-user experience data” (PageSpeed Insights documentation). A low-traffic practice page can therefore show the whole site’s numbers, not its own.

The lab data below it is a simulated load with no user. web.dev notes that “Tools like Lighthouse that load pages in a simulated environment without a user cannot measure INP, as there is no user input,” and that “the Total Blocking Time (TBT) metric is lab-measurable and is a proxy for INP.” In the lab section, TBT is the number to watch for responsiveness.

Testing a Chat Widget’s Cost

Intake chat widgets are third-party scripts, and Google’s own Lighthouse documentation names them. It says “video embeds, social button widgets, and chat widgets can all employ the facade pattern,” and lists live chat tools such as Intercom, Drift, Help Scout and Facebook Messenger among the candidates (Lighthouse documentation on third-party facades). A facade shows a lightweight placeholder, such as a chat bubble image, and loads the real widget only when the visitor interacts with it. The same page notes that this specific Lighthouse audit “has been removed as of Lighthouse 13,” but the pattern it describes still applies.

To measure what the widget costs on a real page:

  1. Open the page in Chrome, open DevTools and go to the Performance panel. Its live metrics view shows LCP, CLS and INP for your own session; Chrome’s documentation says “As you load and interact with the page, these metrics will update in real time” (Chrome DevTools live metrics).
  2. Load the page, tap the menu, the call button and a form field, and note INP and CLS.
  3. Repeat on a copy of the page with the widget removed or replaced by a facade.
  4. Compare. If the difference is large, ask the widget vendor for a delayed-load or click-to-load option before deciding to drop it.

Repeat the test with CPU throttling turned on in DevTools to get closer to what a phone experiences.

Other Causes Worth Checking on Law Firm Pages

Places to look for each metric on a law firm page:

  • LCP: a large attorney photo or office image at the top of every practice page, served at desktop size to phones, or loaded after other scripts.
  • INP: tracking scripts, call-tracking tools, review widgets and chat widgets all running on the main thread when the visitor first taps.
  • CLS: images without set dimensions, embedded maps or review carousels that load late, and consultation banners inserted above content.

What to Fix First

Start with the field data. If PSI shows real-user data for the page or the site, fix the metric that fails at the 75th percentile on mobile, and leave a passing metric alone. If PSI shows no field data, use the DevTools live view on a phone-sized, throttled setup and treat TBT in the lab section as the stand-in for INP. Among failing metrics, fix the ones on practice pages before those on pages that receive little traffic. Speed is one half of the phone experience; whether the phone version carries the same content as the desktop page is the other, covered in what Google indexes under mobile-first indexing.