Website review, no card needed

aabraces.com logo

aabraces.com website review

Visit site (opens in a new tab)Reviewed 3 November 202625 issues · 77 checks

This review found 25 issues worth fixing on aabraces.com, 8 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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 aabraces.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix57
  • Reduce unused JavaScript

    3.3 s · 690 KiB

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

  • Use efficient cache lifetimes

    1.8 s · 198 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. 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 (Google Tag Manager, Facebook and Clarity and others), adding 1.2 MB and 724 ms of main-thread time.

  • Google Tag Manager adds 534 ms

    534 ms

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

  • Improve image delivery

    450 ms · 76 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • Reduce unused CSS

    110 ms · 11 KiB

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

  • 7 long tasks on the main thread

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

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

6 to fix62
  • Largest Contentful Paint: 15.9 s

    15.9 s

    Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME TO COLORADO ORTHODONTICS REQUEST AN APPOINTMENT EXP…”.

  • 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: 7.3 s

    7.3 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Total Blocking Time: 220 ms

    220 ms

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

  • 1 image without width and height

    1 image 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.

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 110 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 110 requests on a phone: scripts 1.4 MB (37), images 838 KiB (20) and HTML 83 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9194
  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

  • 11 links without text

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

  • 2 tap targets too small

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“Welcome to Colorado Orthodontics” and “Smiles Built with Precision. Care Designed for Yo…”). One clear main headline is easier for people and search engines.

  • 164 internal links, 6 external

    The homepage links to 164 pages on aabraces.com and 6 external pages.

7 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Discover expert orthodontics in Thornton, Aurora, Parker & Lakewood with family-focused care. Schedule your free consul…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Colorado Orthodontics | Thornton, Aurora, Parker & Lakewood”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 2 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://coortho.com/wp-includes/css/wave-ortho-inquiry-form.min.css' because its MIME type…”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

  • About 1,424 words of copy

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

5 checks passed
  • Clear next step on the first screen

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

  • 24 calls to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call 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 Microsoft Clarity (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 20 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on aabraces.com, including 13 speed issues, 1 SEO issue 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