The short answer
In a dental group, office pages usually share one template. Google rates pages with a similar layout as a group, so fix the template, not one office page at a time.
Read the numbers carefully. A quiet office page often has no data of its own, and the tools show numbers for the whole site instead.
Then check what each office adds to the template: the top photo, the map, booking and chat widgets, and review embeds. Those are common places for a page to slow down or jump.
One template, many pages
The Core Web Vitals report in Search Console sorts your pages into URL groups: pages with a similar layout. The rating applies to the whole group, and Google assumes the pages in a group share the same cause when they are slow.
For a group with 20 office pages on one template, that is useful. One fix to the template can move every office page at once. It also means one slow add-on in the template slows every office.
A group's status is its worst number. If LCP and INP are good but CLS is poor, the group is poor. Search Console shows a group only when it has enough data for both LCP and CLS.
Where the numbers come from
Google's numbers come from real visits by Chrome users who share usage data, over the last 28 days. A page is counted only if it returns a normal page, is not set to noindex, and has had enough visits. Google does not publish the minimum.
Busy page
Page data
The page has enough Chrome visits of its own, so PageSpeed Insights shows numbers for that address.
Similar pages
URL group data
Search Console puts pages with a similar layout in one group and rates the whole group, such as your office pages.
Quiet page
Whole-site data
A new or quiet office page lacks its own numbers, so the tools fall back to the whole site, called the origin.
When an office page lacks its own numbers, PageSpeed Insights shows origin-level data instead. That number describes the whole site. Label it that way on any report, so nobody reads it as one office's speed.
Lab tests, such as the lower half of PageSpeed Insights, load one page once on a simulated phone. They help find the cause, but they cannot measure INP, because nobody taps the page.
The three targets
Google rates each number at the 75th percentile of visits, separately for phones and computers. A page passes when all three are good.
Largest Contentful Paint (LCP)
Loading. How long until the biggest photo or block of text shows.
Good: 2.5 seconds or less
Poor: Over 4 seconds
Interaction to Next Paint (INP)
Response. How long the page takes to react when someone taps or types.
Good: 200 milliseconds or less
Poor: Over 500 milliseconds
Cumulative Layout Shift (CLS)
Stability. How much the page jumps while it loads.
Good: 0.1 or less
Poor: Over 0.25
Anything between good and poor is rated needs improvement. The single-practice basics of each number are in Core Web Vitals for practice websites.
What office pages add
The parts below are what each office tends to bring to the shared template. Google lists images without a size, embeds without a size, late-loading content, and web fonts as common causes of layout shift.
The top photo or video
On many office pages this is the largest thing on screen, so it often sets LCP. Google says never to lazy-load it, and one image can be marked fetchpriority high so it loads first.
The map
Map embeds do not always reserve their space, so text below them can jump when they load. Give the map a set height, or show a plain directions link and load the map when someone opens it.
Booking and chat widgets
These can add a lot of script to the first load. Chrome's docs describe a facade: a still image that looks like the widget until someone taps it, so the script loads only when it is needed.
Review and video embeds
Like maps, these can arrive late without a set size. Give each one a fixed box so the page holds still.
Office photos added later
A team photo uploaded without width and height makes the page jump. Set both, or an aspect ratio, in the template.
Fonts
Web fonts that arrive late can shift text. Use the same fonts on every office page, so one fix covers them all.
What belongs on each office page in the first place is covered in building location pages for a multi-office site.
Page template speed check
List each page template with its page count and the numbers from Search Console or PageSpeed Insights. The check rates each number against Google's targets, flags whole-site and missing data, and puts the templates in fix order: worst rating first, then the most pages.
Fixing a template
- Open the Core Web Vitals report in Search Console and start with mobile.
- Open an issue and look at its example pages. Search Console lists pages in a group by impressions, so the pages at the top affect the group most.
- Match the group to a template, such as office pages or service pages.
- Test a busy page from that template in PageSpeed Insights and read what the lab test points to.
- Fix the template, not the single page, and ship it to every office page at once.
- Click Validate fix. Search Console watches for 28 days and marks the issue fixed if no page still has it.
When to check
Every template change
New hero, new widget, or a redesign: test a page from the template before and after it ships.
Every new office
Test the new office page in PageSpeed Insights before launch. It will not have its own field data for a while.
Every month
Open the Core Web Vitals report, update your template list, and run the check.
Red flags
Fixing one office page at a time
Search Console rates pages in groups that share a layout. A fix to one page may not move the group. Fix the template.
Trusting a lab score alone
Lab tests run once on one simulated phone and cannot measure INP. Google rates pages on real visits.
Reading whole-site numbers as an office's
When a page lacks its own data, PageSpeed Insights shows the origin. That number is not about the office page.
A lazy-loaded top photo
Google says never to lazy-load the LCP image. It always delays it.
Maps and widgets with no set size
These are among the common causes of layout shift that Google lists.
Office pages left out of the index
A page that returns an error or carries noindex gets no numbers of its own in Chrome's data, and the Search Console report shows only indexed pages.
Checklist
Office page speed checklist
0 of 12 done
Related guides
Setting up Search Console for the group, with a folder property for each office, is in Search Console for dental groups. Fixing the shared template for accessibility is in website accessibility for dental groups.
The map of the other group jobs is marketing a multi-location practice or DSO.
For a multi-office group
DDS Web Solutions builds websites and runs search, ads, and reporting for dental practices. Our team has been building websites since 2014, we have served 100+ practices, and our offices are in Sacramento and San Mateo.
For a group, we can list every template, match it to its Search Console group, fix the template every office uses, and test each new office page before launch.
FAQ
Why does our new office page show no speed data?
Chrome's data includes a page only after it has had enough visits from opted-in Chrome users. Until then, PageSpeed Insights shows numbers for the whole site, or none. Test the page in PageSpeed Insights and use the lab results as a guide while it builds up visits.
Search Console says Poor, but PageSpeed Insights says Good. Which is right?
They measure different things. Search Console rates a group of similar pages over the last 28 days. PageSpeed Insights usually shows one page, and its lab test is a single simulated load. One page can be better than its group.
Does every office page need to pass on its own?
Google rates groups of similar pages, so fix the template first. Search Console still shows example pages for each group, and an office page with very different add-ons, like a heavy video, may sit in a group of its own.
Do Core Web Vitals decide where our offices rank?
Google says good Core Web Vitals line up with what its core ranking systems seek to reward, and it recommends reaching good scores. It does not say speed outweighs relevance. A fast page still needs the right content for the search.
How long until Search Console shows the fix?
Search Console uses the last 28 days of visits. When you click Validate fix, it watches for 28 days and marks the issue fixed if no page on the site still has it.
Do iPhone visitors count?
Not in Chrome's public data. Google says it comes from Chrome on computers and Android phones. Chrome on iOS is not included, and neither are other browsers. Your iPhone visitors still feel a slow page, so fix the template for everyone.
Sources
- Search Console Help: Core Web Vitals report
- web.dev: Web Vitals
- Google for Developers: About PageSpeed Insights
- Chrome for Developers: CrUX methodology
- web.dev: Optimize Largest Contentful Paint
- web.dev: Optimize Cumulative Layout Shift
- web.dev: Optimize Interaction to Next Paint
- Chrome for Developers: Lazy load third-party resources with facades
- Google Search Central: Understanding Core Web Vitals and Google search results