Website review, no card needed

aesthetics-health.com logo

aesthetics-health.com website review

Visit site (opens in a new tab)Reviewed 17 November 202638 issues · 83 checks

This review found 38 issues worth fixing on aesthetics-health.com, 11 of them high impact, across 83 checks. The most urgent: hcaptcha.com adds 1.3 s. 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 aesthetics-health.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aesthetics-health.com at 0.9 s0.9 s
  2. aesthetics-health.com at 1.8 s1.8 s
  3. aesthetics-health.com at 2.7 s2.7 s
  4. aesthetics-health.com at 3.6 s3.6 s
  5. aesthetics-health.com at 4.5 s4.5 s
  6. aesthetics-health.com at 5.4 s5.4 s
  7. aesthetics-health.com at 6.3 s6.3 s
  8. aesthetics-health.com at 7.2 s7.2 s

Speed

11 to fix60
  • hcaptcha.com adds 1.3 s

    1.3 s

    hcaptcha.com costs a phone 1.3 s of main-thread work and 1.2 MB 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.

  • Main-thread work: 8.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hcaptcha.com, YouTube and Google Tag Manager and others), adding 5.8 MB and 3.4 s of main-thread time.

  • Improve image delivery

    2.1 MB

    11 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page.

  • YouTube adds 942 ms

    942 ms

    YouTube costs a phone 942 ms of main-thread work and 1,022 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.

  • Mobile performance score: 60

    60/100

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

  • Shopify adds 344 ms

    344 ms

    Shopify costs a phone 344 ms of main-thread work and 3.0 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.

  • Google Tag Manager adds 583 ms

    583 ms

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

  • Render-blocking requests

    400 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    149 KiB

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

  • Reduce unused CSS

    142 KiB

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

  • Legacy JavaScript

    14 KiB

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

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix69
  • Time to Interactive: 37.4 s

    37.4 s

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

  • Speed Index: 13.7 s

    13.7 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

    Scripts block taps and scrolling for 1.7 s 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.

  • 17 images without width and height

    17 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
  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Aesthetics Health is an award-winning beauty center located…”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix43
  • Page weight: 7.3 MB in 416 requests

    7.3 MB

    Your homepage downloads 7.3 MB in 416 requests on a phone: scripts 3.2 MB (188), images 2.3 MB (22) and other files 926 KiB (158). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    1.8 MB

    6 images are downloaded at several times the size a phone draws them, for example 8E853823-32F8-4BC1-B9B1-683CC0BE4B75.jpg at 3,464 px wide, shown at 360 px. Resized copies would save about 1.8 MB.

  • 8 images below the first screen load straight away

    8 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.07 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 8390
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

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

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate 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.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

5 to fixGoogle 8584
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “UP TO 75% OFF”). One clear main headline is easier for people and search engines.

  • Meta description is long (273 characters)

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

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • 50 internal links, 25 external

    The homepage links to 50 pages on aesthetics-health.com and 25 external pages.

5 checks passed
  • Title: 64 characters

    Your title is a healthy 64 characters: “Aesthetics Health - Eyebrow near me | Skincare facial | pmu lips”.

  • Canonical URL set

    The canonical URL is https://www.aesthetics-health.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://www.aesthetics-health.com/sitemap.xml.

AI search readiness

100
4 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 (638 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.aesthetics-health.com/blogs/aesthetics-health has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.aesthetics-health.com/pages/how-to-book-your-appointment 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 18 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 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 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 534 words of copy

    The homepage carries about 534 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK AN APPOINTMENT” and “CALL / TEXT 703-625-6868”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “BOOK AN APPOINTMENT”, “CALL / TEXT 703-625-6868” and “CONTACT”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 aesthetics-health.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Forms · gtranslate.io · getsocialbar.com · chimpstatic.com

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Hiring

Hiring
2 open roles
Job board
careers page

Company

Headquarters
McLean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on aesthetics-health.com, including 16 speed issues, 5 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