Marketing and Lead Generation

Law Firm Website Speed and Core Web Vitals

Core Web Vitals for law firm websites: the three thresholds, how to measure them, fixes for slow, laggy or jumpy pages, and questions for your vendor.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. Why speed matters more for law firms than it seems
  2. Your visitors are on phones
  3. The three Core Web Vitals
  4. Measure before you fix anything
  5. Quick wins for slow loading
  6. Quick wins for laggy taps
  7. Quick wins for jumpy layouts
  8. Protect the elements that produce inquiries
  9. A worked example
  10. Questions for your web vendor
  11. A monthly speed check
  12. Frequently asked questions
  13. References
Marketing and Lead Generation: Law Firm Website Speed and Core Web VitalsArticle coverMARKETING AND LEAD GENERATIONLaw Firm Website Speedand Core Web VitalsAva for LawyersInsightsMarketing and Lead Generation: Law Firm Website Speed and Core Web VitalsArticle coverMARKETING AND LEAD GENERATIONLaw Firm WebsiteSpeed and Core WebVitalsAva for Lawyers

Key takeaways

  • Good Core Web Vitals mean the main content loads within 2.5 seconds, interactions respond within 200 milliseconds, and layout shift stays at 0.1 or less[1].
  • Google recommends good Core Web Vitals and says they align with what its core ranking systems seek to reward, but relevance still comes first[2].
  • Most visitors arrive on phones: 91% of US adults own a smartphone and 16% rely on one without home broadband[3].
  • The biggest wins on law firm sites usually come from compressing the hero image and cutting third-party scripts.

Why speed matters more for law firms than it seems

People looking for a lawyer are often stressed, short on time and searching on a phone. Someone whose spouse was just arrested, or who has received an eviction notice, does not wait patiently for a slow page to load or tap a button three times because the page did not respond. They go back and tap the next result. Speed is therefore not a technical vanity metric. It decides whether the visitor ever sees your phone number, your reviews or your practice page.

Google measures the experience with three Core Web Vitals. Its documentation recommends that site owners achieve good scores for success with Search, and says this, along with other page experience aspects, aligns with what its core ranking systems seek to reward[2]. A fast page will not outrank a more relevant one, but a slow page wastes the traffic you already earn.

Your visitors are on phones

Pew Research Center reports that 98% of US adults own a cellphone, 91% own a smartphone, and 16% are smartphone-dependent, with a smartphone but no home broadband[3]. Only 78% of adults subscribe to home broadband[4]. Many of your visitors load your site on a mid-range phone over a cellular connection, sometimes with a weak signal. A page that feels instant on the office fiber connection can take several seconds for them.

Mobile device access among US adultsPew Research Center, Mobile Fact Sheet, 2026.
Mobile device access among US adultsBar chart. Own a cellphone: 98%; Own a smartphone: 91%; Smartphone-dependent (no home broadband): 16%.Own a cellphoneOwn a cellphone: 98%98%Own a smartphoneOwn a smartphone: 91%91%Smartphone-dependent (no home broadband)Smartphone-dependent (no home broadband): 16%16%Mobile device access among US adultsBar chart. Own a cellphone: 98%; Own a smartphone: 91%; Smartphone-dependent (no home broadband): 16%.Own a cellphoneOwn a cellphone: 98%98%Own a smartphoneOwn a smartphone: 91%91%Smartphone-dependent (no homebroadband)Smartphone-dependent (no home broadband): 16%16%

Source: Pew Research Center, 2026[3]

Show the data
ItemValue
Own a cellphone98%
Own a smartphone91%
Smartphone-dependent (no home broadband)16%

The three Core Web Vitals

Core Web Vitals thresholds from web.dev and common causes on law firm websites.
MetricWhat it measuresGood thresholdTypical law-site culprit
Largest Contentful Paint (LCP)How fast the main content appearsWithin 2.5 secondsHuge hero photo, slow hosting, sliders
Interaction to Next Paint (INP)How fast the page responds to taps and clicks200 milliseconds or lessChat widgets, tracking scripts, heavy page builders
Cumulative Layout Shift (CLS)How much the layout jumps while loading0.1 or lessImages without dimensions, late banners, web fonts

Google's guidance is to measure these at the 75th percentile of page loads, segmented across mobile and desktop devices[1]. In plain terms, three out of four real visits should meet each threshold. Lab tests on your own computer are useful for diagnosing problems, but the scores that matter come from real visitors.

Measure before you fix anything

  1. Check field data

    Run your home page and top practice pages through PageSpeed Insights and look first at the real-user section, if your site has enough traffic to show it.

  2. Open the Search Console report

    The Core Web Vitals report groups similar pages and shows which fail on mobile and desktop.

  3. Test on a real phone

    Load the site on a mid-range phone over a cellular connection, with the browser cache cleared, and time how long until you can tap the phone number.

  4. List the pages that matter

    Home, contact, and the practice pages that bring the most inquiries. Fix those first.

  5. Record a baseline

    Note the three scores for each key page so you can tell whether changes worked.

Quick wins for slow loading

  • Resize and compress the hero image; serve it in a modern format at the size it is displayed, not the size the camera produced.
  • Replace image sliders with a single image or a plain headline; sliders load several large images and rarely help.
  • Remove autoplay background video on mobile.
  • Use one or two web font weights, not six, and let text show while fonts load.
  • Move to hosting with caching and a content delivery network if the server takes more than a moment to respond.
  • Lazy-load images further down the page, but never the main image at the top.

Quick wins for laggy taps

Slow interaction on law firm sites almost always comes from JavaScript, and much of it is from third parties: chat widgets, call tracking, review carousels, social embeds, multiple analytics and advertising tags, and heavy page builder themes. Each one may be small, but together they keep the phone's processor busy so that a tap on the call button takes a moment to register.

  • List every third-party script on the site and the business reason for each.
  • Remove tags for tools you no longer use; old agencies often leave several behind.
  • Load chat and review widgets only after the main content, or only when the visitor taps to open them.
  • Use one tag manager and one analytics tool rather than overlapping ones.
  • Make sure the phone link is a plain link, not one that waits for a script to load.

Quick wins for jumpy layouts

  • Set width and height on every image and embed so the browser reserves space.
  • Reserve space for cookie and announcement banners, or place them where they do not push content down.
  • Avoid inserting content above what the visitor is already reading, such as late-loading review badges.
  • Match fallback fonts to your web fonts so text does not reflow when fonts arrive.

Layout shift is more than an irritation. On a phone, a page that jumps just as the visitor taps can send them to the wrong link, or make them tap an ad instead of your phone number. For a firm, that can mean a lost inquiry from someone who was ready to call.

Protect the elements that produce inquiries

Speed work should start with the parts of the page that make the phone ring. The tap-to-call link in the header, the contact form and the booking button should load first and respond instantly. Test the form on a phone with autofill, check that the confirmation appears quickly, and make sure the call button works before any script has finished loading. If you use call tracking that swaps numbers with a script, confirm the original number works if the script fails.

A worked example

Example: a fictional three-lawyer criminal defense firm checks its mobile scores and finds the home page fails all three metrics. The main content takes well over the 2.5-second target to appear, taps on the call button lag, and the page jumps when a review badge loads near the top. The diagnosis takes an afternoon.

  • The hero is a full-resolution photo of the courthouse, several megabytes in size. Resized and compressed, it becomes a fraction of that.
  • The site runs two analytics tools, a chat widget, a review carousel, a social feed and three advertising tags left by a previous agency. Four are removed and the chat widget now loads only when tapped.
  • The review badge is moved below the first screen and given a fixed height.
  • The web font is cut from five weights to two.

After the changes, the firm watches the real-user data over the following weeks rather than relying on one lab test. The page passes on mobile, and the intake team notices fewer callers saying they could not get the site to load. The lesson is typical: nothing exotic was needed, only removing weight that had accumulated over years.

Questions for your web vendor

  1. What are our current Core Web Vitals on mobile for the home page and top five practice pages?
  2. Which third-party scripts run on the site, and which can we remove or delay?
  3. How are images resized and compressed when staff upload them?
  4. Does our hosting include caching and a content delivery network?
  5. Will the next redesign or theme update be tested against these metrics before launch?
  6. Who checks the scores each month, and how will we hear about regressions?

A monthly speed check

Once the main fixes are in, speed drifts back through small additions: a new widget, an uncompressed photo on a new bio, a tracking tag for a campaign that ended. Put a fifteen-minute check on the calendar each month. Review the Search Console report, load the home page and contact page on a phone, and confirm the phone link and form still respond instantly. Treat any new third-party script as a decision that needs a reason, not a default.

Frequently asked questions

What are good Core Web Vitals scores?

Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads[1].

Will a faster website rank my law firm higher?

Speed helps, but relevance and quality come first. Google recommends good Core Web Vitals and says they align with what its ranking systems reward, without promising higher placement[2].

What slows law firm websites the most?

Oversized hero images, sliders and video backgrounds slow loading; chat widgets, tracking tags and page builders slow interaction. Fix those before anything else.

References

  1. Google (web.dev) (n.d.). Web Vitals (opens in a new tab) โ†‘

  2. Google Search Central (n.d.). Understanding Core Web Vitals and Google search results (opens in a new tab) โ†‘

  3. Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) โ†‘

  4. Pew Research Center (2026). Americans' Use of Internet, Broadband in 2026 (Internet, Broadband Fact Sheet) (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo