Website review, no card needed

Aescape logo

aescape.com website review

Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 81 checks

This review found 31 issues worth fixing on aescape.com, 9 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Aescape

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.1 s602 msMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.5 s
Aug 22, 20261.3 s
Aug 29, 2026956 ms
Sep 5, 2026778 ms
Sep 12, 2026770 ms
Sep 19, 2026774 ms
Sep 26, 2026794 ms
Oct 3, 2026802 ms
Oct 10, 2026821 ms
Oct 17, 20261.1 s
Oct 24, 20261.4 s
Oct 31, 20261.6 s
Nov 7, 20261.7 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
152 ms61 msMay 30Nov 1481 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026141 ms
Jun 6, 2026137 ms
Jun 13, 2026125 ms
Jun 20, 2026120 ms
Jun 27, 2026109 ms
Jul 4, 2026107 ms
Jul 11, 2026110 ms
Jul 18, 2026110 ms
Jul 25, 2026109 ms
Aug 1, 2026109 ms
Aug 8, 2026104 ms
Aug 15, 202696 ms
Aug 22, 202687 ms
Aug 29, 202675 ms
Sep 5, 202671 ms
Sep 12, 202672 ms
Sep 19, 202674 ms
Sep 26, 202674 ms
Oct 3, 202674 ms
Oct 10, 202674 ms
Oct 17, 202678 ms
Oct 24, 202679 ms
Oct 31, 202679 ms
Nov 7, 202680 ms
Nov 14, 202681 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

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

Speed

7 to fix74
  • Use efficient cache lifetimes

    2.5 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Framer CDN, Google Tag Manager and Facebook and others), adding 3.3 MB and 813 ms of main-thread time.

  • Reduce unused JavaScript

    600 ms · 488 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Framer CDN adds 446 ms

    446 ms

    Framer CDN costs a phone 446 ms of main-thread work and 2.6 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.

  • Improve image delivery

    641 KiB

    3 images could be 641 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1,885 HTML elements

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    44 KiB

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

  • Minify JavaScript

    34 KiB

    34 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

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

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

  • Server response: 74 ms

    74 ms

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

Core Web Vitals

5 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.38

    0.38

    For real visitors the layout shifts by 0.38 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 9.8 s

    9.8 s

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 81 ms

    81 ms

    Real visitors wait 81 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 0.7 s

    0.7 s

    Real visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 397 ms

    397 ms

    Real visitors wait 397 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 42% faster for real visitors

    -42%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 141 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 56 ms

    56 ms

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

Images and page weight

1 to fix70
  • Page weight: 5.6 MB in 101 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 101 requests on a phone: media 2.0 MB (1), scripts 1.4 MB (54) and fonts 1.2 MB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 190.9 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

8 to fixGoogle 8987
  • Interactive controls must not be nested (12 elements)

    Interactive controls must not be nested: 12 elements on the page fail this check, rated serious by axe-core.

  • 9 text elements with low contrast

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

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

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

    All page content should be contained by landmarks: 41 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.

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 8 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 62 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 17 H1 headlines

    There are 17 <h1> headlines (“Listen. Release. Repeat.”, “Listen. Release. Repeat.” and “Listen. Release. Repeat.”). One clear main headline is easier for people and search engines.

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

  • 104 internal links, 50 external

    The homepage links to 104 pages on aescape.com and 50 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Aescape maps your body, releases the tension it holds, and adapts every session to you. Find Adaptive Body Therapy near…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Aescape | Adaptive Body Therapy, Where the Body Is Heard”.

  • Canonical URL set

    The canonical URL is https://www.aescape.com/.

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 2 pages without an H1

    https://www.aescape.com/privacy-policy and https://www.aescape.com/terms-of-use have 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 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.

  • 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 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

3 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 12-field form

    Your longest form asks for 12 fields (1 required). Every extra field lowers completion.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 572 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book now”.

  • 58 calls to action

    The homepage has 58 calls to action, for example “Book now”, “Book a session” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 aescape.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
Framer
E-commerce
Shopify
Analytics
Google Analytics | Segment
Hosting
Framer

Hiring

Hiring
7 open roles
Teams
Hardware Engineering (3), Software Engineering (2), Finance (1), Sales (1)
Job board
ashby

Company

Employees
80
Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on aescape.com, including 12 speed issues, 3 SEO issues and 3 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