Website review, no card needed

pdtdental.com logo

pdtdental.com website review

Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 77 checks

This review found 32 issues worth fixing on pdtdental.com, 9 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.2 s918 msMay 23Nov 71.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 2026982 ms
Jul 4, 2026964 ms
Jul 11, 20261.0 s
Jul 18, 2026994 ms
Jul 25, 2026989 ms
Aug 1, 20261.0 s
Aug 8, 2026951 ms
Aug 15, 2026986 ms
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.1 s
Nov 7, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
104 ms65 msMay 23Nov 773 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202681 ms
May 30, 202682 ms
Jun 6, 202679 ms
Jun 13, 202673 ms
Jun 20, 202672 ms
Jun 27, 202688 ms
Jul 4, 202688 ms
Jul 11, 202699 ms
Jul 18, 202699 ms
Jul 25, 202681 ms
Aug 1, 202687 ms
Aug 8, 202681 ms
Aug 15, 202681 ms
Aug 22, 202682 ms
Aug 29, 202679 ms
Sep 5, 202674 ms
Sep 12, 202671 ms
Sep 19, 202669 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202671 ms
Oct 17, 202673 ms
Oct 24, 202671 ms
Oct 31, 202671 ms
Nov 7, 202673 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of pdtdental.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pdtdental.com at 0.4 s0.4 s
  2. pdtdental.com at 0.8 s0.8 s
  3. pdtdental.com at 1.1 s1.1 s
  4. pdtdental.com at 1.5 s1.5 s
  5. pdtdental.com at 1.9 s1.9 s
  6. pdtdental.com at 2.3 s2.3 s
  7. pdtdental.com at 2.6 s2.6 s
  8. pdtdental.com at 3.0 s3.0 s

Speed

8 to fix55
  • Use efficient cache lifetimes

    1.9 s · 582 KiB

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

  • Reduce unused JavaScript

    1.6 s · 352 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Hubspot and others), adding 990 KiB and 662 ms of main-thread time.

  • Main-thread work: 2.9 s

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

  • Google Tag Manager adds 168 ms

    168 ms

    Google Tag Manager costs a phone 168 ms of main-thread work and 300 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.

  • 1,964 HTML elements

    The page has 1,964 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    131 KiB

    4 images could be 131 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

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

  • Forced reflow

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.9 s

    14.9 s

    Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PDT Dental”.

  • Time to Interactive: 15.9 s

    15.9 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Total Blocking Time: 361 ms

    361 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 62 ms

    62 ms

    Real visitors wait 62 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 532 ms

    532 ms

    Real visitors wait 532 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 81 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix47
  • 8 images far larger than shown

    552 KiB

    8 images are downloaded at several times the size a phone draws them, for example 1787579678_6a8c4d1eefd4e.jpeg at 512 px wide, shown at 63 px. Resized copies would save about 552 KiB.

  • Page weight: 3.5 MB in 229 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 229 requests on a phone: images 1.1 MB (42), scripts 1.0 MB (51) and other files 728 KiB (93). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    November_2026_Tradeshows_768_x_1110_px_3_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 8 images in older formats

    8 images (591 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.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

Accessibility

5 to fixGoogle 9194
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8576
  • Title is short (10 characters)

    Your title is only 10 characters: “PDT Dental”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (10 characters)

    Your meta description is only 10 characters: “PDT Dental”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“PDT Dental” and “”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ']', ..."dtdental",], "ur"... is not va)”.

  • 13 links crawlers can't follow

    13 links have no real href, so search engines can't follow them.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 248 internal links, 11 external

    The homepage links to 248 pages on pdtdental.com and 11 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://pdtdental.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://pdtdental.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,014 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://pdtdental.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9691
  • 25 small tap targets

    25 of 70 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 578 words of copy

    The homepage carries about 578 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REGISTER NOW”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop All Diagnostic”, “Shop All Endodontic” and “Shop All Hygiene”.

  • 10 short forms

    10 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 2 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 22 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at pdtdental.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Hulk Gdpr Cookie Bar · Google Review Plus By Entangle · Back In Stock · Madgic Checkout Validation · Hulk Product Options

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

Company

Headquarters
Missoula

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on pdtdental.com, including 13 speed issues and 6 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25
pdtdental.com website review: scores and fixes