productivedentist.com website review

About 673 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

Your mobile performance score is 39 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.5 MB and 1.4 s of main-thread time.

About 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

8 images could be 284 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

Google Tag Manager costs a phone 564 ms of main-thread work and 500 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google CDN costs a phone 494 ms of main-thread work and 733 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

33 KiB could be saved by minifying JavaScript.

13 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.

15 files are served with short cache lifetimes, so returning visitors download them again (177 KiB).

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Annual Momentum Planning for 2027”.

The page becomes fully interactive after 19.4 s. Good is under 3.8 s.

Visually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.9 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 821 ms in total while the page loads. Good is under 200 ms.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.6 MB in 120 requests on a phone: scripts 1.7 MB (36), images 1.0 MB (35) and fonts 420 KiB (8). Under 2 MB keeps phones on slow connections fast.

8 images further down the page (554 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

7 images (428 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

Your title is 74 characters, so Google will cut it off around 60: “Maximize The Value of Your Dental Practice with Productive Dentist Academy”.

The homepage links to 54 pages on productivedentist.com and 38 external pages.

There is no https://productivedentist.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://productivedentist.com/category/case-studies is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://productivedentist.com/podcasts/the-productive-dentist-podcast, https://productivedentist.com/podcasts/investment-grade-practices-podcast, https://productivedentist.com/podcasts/everyday-practices-dental-podcast, https://productivedentist.com/about-us/our-team, https://productivedentist.com/category/case-studies and https://productivedentist.com/blog/case-study-tiger-family-dental have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://productivedentist.com/case-study-dr-devin-giron, whose canonical is https://productivedentist.com/case-studies/dr-devin-giron. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://productivedentist.com/podcasts/the-productive-dentist-podcast, https://productivedentist.com/podcasts/investment-grade-practices-podcast and https://productivedentist.com/podcasts/everyday-practices-dental-podcast have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

The homepage carries about 295 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 16 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.