Website review, no card needed

ace-ortho.com logo

ace-ortho.com website review

Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 82 checks

This review found 35 issues worth fixing on ace-ortho.com, 11 of them high impact, across 82 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

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

How it loaded on a phone

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

Speed

7 to fix70
  • Use efficient cache lifetimes

    7.1 s · 3.7 MB

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

  • Reduce unused JavaScript

    4.7 s · 581 KiB

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

  • Improve image delivery

    1.5 s · 1.2 MB

    26 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 70

    70/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and patientpop.com and others), adding 1.7 MB and 595 ms of main-thread time.

  • Google Tag Manager adds 543 ms

    543 ms

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

  • FontAwesome CDN adds 52 ms

    52 ms

    FontAwesome CDN costs a phone 52 ms of main-thread work and 361 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.

  • Font display

    150 ms

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    86 KiB

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

  • Minify CSS

    23 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 566 ms of it running JavaScript. That is comfortably low.

  • Server response: 119 ms

    119 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 22.6 s

    22.6 s

    Your largest element takes 22.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 25.6 s

    25.6 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 8 images without width and height

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

2 checks passed
  • Total Blocking Time: 91 ms

    91 ms

    Scripts block the page for only 91 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.5 MB in 148 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 148 requests on a phone: images 3.4 MB (113), scripts 1.3 MB (12) and fonts 618 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.57 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 5984
  • Input buttons must have discernible text (9 elements)

    Input buttons must have discernible text: 9 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 36 text elements with low contrast

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

  • 17 tap targets too small

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

  • 17 images without alt text

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

  • All page content should be contained by landmarks (53 elements)

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

  • No main landmark

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

  • Zoom is disabled

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

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8378
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “Donna Chang, DDS, MS: Orthodontist Merrifield Falls Church, VA: Ace Orthodontics”.

  • Meta description is long (171 characters)

    Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Dentist) but with 1 problem, for example “Dentist: sameAs is an empty list”.

  • 16 links crawlers can't follow

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

  • No robots.txt

    There is no robots.txt at ace-ortho.com/robots.txt, the first file search crawlers ask for.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 33 internal links, 10 external

    The homepage links to 33 pages on ace-ortho.com and 10 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Donna Chang, DDS, MS”.

  • Canonical URL set

    The canonical URL is https://ace-ortho.com/index.html.

  • XML sitemap found

    Your XML sitemap is reachable at https://ace-ortho.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 linked page hidden from search

    https://ace-ortho.com/your-privacy.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share a meta description

    https://ace-ortho.com/contents/new-patients/free-consultation.html, https://ace-ortho.com/contents/new-patients/cost-of-orthodontic-treatment.html, https://ace-ortho.com/contents/new-patients/office-policies.html, https://ace-ortho.com/contents/new-patients/emergencies.html, https://ace-ortho.com/contactus.html and https://ace-ortho.com/your-privacy.html use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7383
  • 16 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'length')”.

  • 11 distorted images

    11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

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

  • 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 1,009 words of copy

    The homepage carries about 1,009 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST APPOINTMENT” and “Book Online”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Request Appointment” and “Contact Us”.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • 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

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 ace-ortho.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 © 2020.

Stack

Analytics
Google Analytics | Google Tag Manager
Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on ace-ortho.com, including 12 speed issues and 5 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