Example Dental Clinic
Website audit: sample report
Overall score: 78of 100, needs work
What to expect from your report
How to read it, what you do and what happens next
How to read it
- The score out of 100 is a snapshot of what we found on the day of the audit. It helps you compare areas and see change over time. It is not a grade of your business and not a guarantee of any result. Rings are green from 80, amber from 50 to 79 and red below 50.
- Severity is how much a finding is likely to cost you: Critical, High, Medium or Low. Each level has its own shape as well as its own colour.
- Confidence is how sure we are: Confirmed means we saw it directly, Likely means strong signs, Needs verification means worth checking on your side.
- Priority order weighs severity and impact against the effort to fix, so a quick fix to a serious problem comes first.
What you do
- Start with Fix first: the open findings with the highest priority.
- When you or your developer have made a change, tick Mark done. It tells us to check the change. It does not change your score.
- If a finding does not fit your business, use “I think this is wrong” under it and tell us why.
What happens next
- We review the items you mark done, then either verify them or reopen them.
- A follow-up audit can compare your site with this report and show what changed.
What we do not do
- We do not change your website unless we have agreed that separately in writing. You decide what to change and who makes the change.
- Findings describe what we could observe at the time of the audit. Your site may have changed since, and no audit finds everything.
- This is not legal, security or compliance advice. The Terms of Service set out the details.
Scores by service
-
UX & conversion score: 75of 100, needs work
UX & conversion
-
SEO score: 90of 100, good
SEO
-
Speed & performance score: 70of 100, needs work
Speed & performance
Progress
- To do4
- Marked done (awaiting verification)1
- Verified2
- Reopened1
Summary
- UX & conversion. Most visitors arrive on a phone, and the path to booking is where the site loses them: the booking button is out of sight and the form rejects common phone number formats.
- SEO. Search engines can crawl the site, but the treatment pages are hard to tell apart in results and the clinic details are not machine-readable.
- Speed & performance. Pages are slow to show anything on phones because of one oversized photo and scripts that load before the content.
Fix first
The 5 open findings with the highest priority, weighing severity and impact against effort.
- Severity: Critical The booking form rejects phone numbers that contain spaces or brackets, so many patients cannot send a request.
- Severity: High On phones, the “Book an appointment” button sits below three screens of photos.
- Severity: High Nine treatment pages share the same title, “Example Dental Clinic | Home”, so search results cannot tell them apart.
- Severity: High A photo slider script and three font files load before anything appears, adding about 1.2 seconds of blank screen on phones.
- Severity: Medium The site has no Dentist structured data, so search engines may not read the address, phone number and opening hours reliably.
Severity: Critical 1 finding
Severity: Critical
Confidence: Confirmed
Service: UX & conversion
Category: Booking journey
Status: Reopened
The booking form rejects phone numbers that contain spaces or brackets, so many patients cannot send a request.
- Page
- https://exampledental.example/book (mobile and desktop)
- Evidence
POST https://exampledental.example/book phone="555 010 4477" -> "Please enter a valid phone number" phone="(555) 010-4477" -> "Please enter a valid phone number" phone="5550104477" -> request accepted Field pattern: ^[0-9]{10}$ (no spaces, brackets, dashes or +)- Proposed fix
- Strip spaces, brackets, dashes and a leading + before checking the number, and loosen the field pattern to allow them. Show an example under the field (“For example 555 010 4477”) so people see the format before they submit.
- How to check it is fixed
- On a phone, send three test bookings using 555 010 4477, (555) 010-4477 and +1 555 010 4477. All three should be accepted and arrive in the clinic inbox. A number containing letters should still show an error next to the field.
Severity: High 4 findings
Severity: High
Confidence: Confirmed
Service: UX & conversion
Category: Booking journey
Status: To do
On phones, the “Book an appointment” button sits below three screens of photos.
- Page
- https://exampledental.example/ (mobile)
- Evidence
GET https://exampledental.example/ viewport 390×844 (iPhone 13) first button "Book an appointment" at y=2,140px
- Proposed fix
- Move the booking button into the first screen and repeat it in the header. Crop the hero photo to half the screen height and keep the photo carousel below the button.
- How to check it is fixed
- Open the home page on a phone (or at 390×844 in your browser’s device view). “Book an appointment” should be visible without scrolling, and the header button should stay in view as you scroll.
Severity: High
Confidence: Confirmed
Service: SEO
Category: On-page
Status: To do
Nine treatment pages share the same title, “Example Dental Clinic | Home”, so search results cannot tell them apart.
- Page
- Whole site
- Evidence
Crawl of 23 pages 9 pages with <title>Example Dental Clinic | Home</title> /treatments/implants, /treatments/whitening, /treatments/aligners and 6 more
- Proposed fix
- Give each treatment page its own title of 50 to 60 characters that names the treatment and the town, for example “Dental implants in Springfield | Example Dental Clinic”. Most site builders set this in each page’s SEO or search settings.
- How to check it is fixed
- Open each treatment page and read the title on the browser tab: all nine should be different. Search engines show the new titles only after they next crawl the pages.
Severity: High
Confidence: Confirmed
Service: Speed & performance
Category: Mobile loading
Status: Verified
The home page photo is a 2.8 MB file sent at full camera size, which delays the main content on phones.
- Page
- https://exampledental.example/ (mobile)
- Evidence
Lighthouse 12, mobile emulation Largest Contentful Paint: 5.1 s (recommended: 2.5 s or less) LCP element: <img src="/uploads/hero-team.jpg"> 4032×3024, 2.8 MB Displayed at 390×293 on a phone
- Proposed fix
- Export the photo at 1600px wide as WebP (or JPEG at 80% quality), under 200 KB, and offer smaller versions to phones with srcset. Keep the width and height attributes so the layout does not jump while it loads.
- How to check it is fixed
- Run PageSpeed Insights (pagespeed.web.dev) on the home page for mobile. The photo should be under 200 KB and Largest Contentful Paint should be below 2.5 s. Run it twice, because single results vary.
Severity: High
Confidence: Confirmed
Service: Speed & performance
Category: Mobile loading
Status: To do
A photo slider script and three font files load before anything appears, adding about 1.2 seconds of blank screen on phones.
- Page
- Whole site (mobile)
- Evidence
Lighthouse 12, mobile emulation, home page Render-blocking: slider.min.js (184 KB), fonts.css with 3 font files (312 KB) Estimated saving: 1,180 ms The slider appears only on the home page but its script loads on all 23 pages
- Proposed fix
- Load the slider script with defer, and only on the home page. Keep at most two font weights, host them yourself as WOFF2 and add font-display: swap so text shows straight away.
- How to check it is fixed
- In PageSpeed Insights (mobile), “Eliminate render-blocking resources” should no longer list slider.min.js or the font files. On /contact, the browser’s Network tab should show that slider.min.js is not requested.
Severity: Medium 2 findings
Severity: Medium
Confidence: Confirmed
Service: UX & conversion
Category: Mobile usability
Status: Marked done (awaiting verification)
Links in the mobile treatments menu are 30px tall with 4px between them, so taps often open the wrong treatment.
- Page
- https://exampledental.example/treatments (mobile)
- Evidence
viewport 390×844 .menu-treatments a: height 30px, gap 4px (10 links) Recommended minimum touch target: 44×44px
- Proposed fix
- Give each menu link at least 44px of height (for example 12px padding above and below the text) and 8px of space between links.
- How to check it is fixed
- Open /treatments on a phone and open the menu. In the browser’s inspector, each link should measure at least 44px high. Tap each link once: every tap should open the treatment you touched.
Severity: Medium
Confidence: Likely
Service: SEO
Category: Structured data
Status: To do
The site has no Dentist structured data, so search engines may not read the address, phone number and opening hours reliably.
- Page
- https://exampledental.example/
- Evidence
Home page and /contact: no application/ld+json blocks No schema.org Dentist or LocalBusiness markup in the HTML Address and phone appear only as plain text in the footer
- Proposed fix
- Add one JSON-LD block of type Dentist to the home page with the clinic name, address, phone number, opening hours and website address, matching your Google Business Profile exactly.
- How to check it is fixed
- Paste the home page address into Google’s Rich Results Test (search.google.com/test/rich-results). It should detect one Dentist item with no errors, and the address and phone should match your Google Business Profile.
Severity: Low 1 finding
Severity: Low
Confidence: Confirmed
Service: UX & conversion
Category: Mobile usability
Status: Verified
Opening hours are shown only as an image, so screen readers, translation tools and search engines cannot read them.
- Page
- https://exampledental.example/contact
- Evidence
<img src="/img/hours-2025.png" alt="hours"> on /contact No opening hours in the page text or the footer
- Proposed fix
- Replace the image with a short text list of days and times, and repeat the hours in the footer of every page.
- How to check it is fixed
- Open /contact and try to select the opening hours: the text should highlight and copy. View the page source and search for “Monday” to confirm the hours are in the HTML.