Website review, no card needed

lancasterfamilydds.com logo

lancasterfamilydds.com website review

Visit site (opens in a new tab)Reviewed 13 November 202636 issues · 75 checks

This review found 36 issues worth fixing on lancasterfamilydds.com, 16 of them high impact, across 75 checks. The most urgent: improve image delivery. 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

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

How it loaded on a phone

  1. lancasterfamilydds.com at 0.7 s0.7 s
  2. lancasterfamilydds.com at 1.4 s1.4 s
  3. lancasterfamilydds.com at 2.2 s2.2 s
  4. lancasterfamilydds.com at 2.9 s2.9 s
  5. lancasterfamilydds.com at 3.6 s3.6 s
  6. lancasterfamilydds.com at 4.3 s4.3 s
  7. lancasterfamilydds.com at 5.1 s5.1 s
  8. lancasterfamilydds.com at 5.8 s5.8 s

Speed

12 to fix26
  • Improve image delivery

    2.3 s · 592 KiB

    6 images could be 592 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • allaccessible.org adds 1.3 s

    1.3 s

    allaccessible.org costs a phone 1.3 s of main-thread work and 638 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 4.2 s

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

  • Use efficient cache lifetimes

    750 ms · 17.2 MB

    53 files are served with short cache lifetimes, so returning visitors download them again (17.2 MB).

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    510 ms · 502 KiB

    About 502 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 510 ms faster on a phone.

  • Reduce unused CSS

    850 ms · 128 KiB

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

  • 13 long tasks on the main thread

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

  • Google Tag Manager adds 286 ms

    286 ms

    Google Tag Manager costs a phone 286 ms of main-thread work and 297 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,713 HTML elements

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

  • Font display

    250 ms

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

  • Legacy JavaScript

    42 KiB

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

  • Minify CSS

    13 KiB

    13 KiB could be saved by minifying CSS.

  • 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.

1 checks passed
  • Server response: 60 ms

    60 ms

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

Core Web Vitals

7 to fix19
  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Player Media error: Format(s) not supported or source…”.

  • Time to Interactive: 15.3 s

    15.3 s

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

  • Cumulative Layout Shift: 0.408

    0.408

    The layout shifts by 0.408 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 888 ms

    888 ms

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

  • Speed Index: 6.1 s

    6.1 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    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.

Images and page weight

1 to fix33
  • Page weight: 19.7 MB in 93 requests

    19.7 MB

    Your homepage downloads 19.7 MB in 93 requests on a phone: media 16.6 MB (2), images 1.3 MB (21) and scripts 1.3 MB (33). Under 2 MB keeps phones on slow connections fast.

  • About 5.6 g of CO₂ per visit

    5.58 g

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

Accessibility

7 to fixGoogle 8469
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • 35 text elements with low contrast

    35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 tap targets too small

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

  • Skip links are not focusable.

    Skip links are not focusable. (1 element).

  • Headings skip levels

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

1 checks passed
  • 9 automated accessibility rules passed

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

SEO

4 to fixGoogle 9286
  • 3 H1 headlines

    There are 3 <h1> headlines (“Bringing smiles to our community Since 2016”, “Patient Experiences That Make Us Proud” and “We offer professional language interpretation for…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Article, Dentist, ImageObject and Organization) but with 1 problem, for example “Person: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 64 internal links, 7 external

    The homepage links to 64 pages on lancasterfamilydds.com and 7 external pages.

5 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Our mission is to help patients live healthier lives. We provide a caring, nurturing environment where your comfort and…”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Home - Lancaster Family Dentistry”.

  • Canonical URL set

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

  • 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://lancasterfamilydds.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://lancasterfamilydds.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.

2 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

Other pages

2 to fix70
  • 5 linked pages are broken

    Your homepage links to https://lancasterfamilydds.com/preventative-care/arestin, https://lancasterfamilydds.com/preventative-care/child-dentistry, https://lancasterfamilydds.com/preventative-care/deep-teeth-cleaning, https://lancasterfamilydds.com/preventative-care/dental-exams-and-check-ups and https://lancasterfamilydds.com/preventative-care/dental-sealants, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without an H1

    https://lancasterfamilydds.com/doctor has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No call to action on the first screen

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

  • Only about 5 words

    The homepage has only about 5 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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.

7 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Call (469) 813-8149”, “Contact Us” and “Book an Appointment”.

  • Social proof on the page

    Social proof on the homepage: 30 testimonial or review blocks and 2 trust badges.

  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 lancasterfamilydds.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Hostinger

Hiring

Hiring
1 open role
Job board
smartrecruiters

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on lancasterfamilydds.com, including 19 speed issues, 4 SEO issues and 2 conversion gaps. 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