Website review, no card needed

aadancecostumes.com logo

aadancecostumes.com website review

Visit site (opens in a new tab)Reviewed 21 October 202636 issues · 83 checks

This review found 36 issues worth fixing on aadancecostumes.com, 10 of them high impact, across 83 checks. The most urgent: page weight: 5.1 MB in 386 requests. 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

Real-visitor load time (LCP)75th percentile, phones
1.1 s756 msMay 9Oct 17828 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026916 ms
May 16, 2026858 ms
May 23, 2026826 ms
May 30, 2026798 ms
Jun 6, 2026796 ms
Jun 13, 2026884 ms
Jun 20, 2026900 ms
Jun 27, 2026960 ms
Jul 4, 20261.1 s
Jul 11, 2026972 ms
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 2026915 ms
Aug 8, 2026910 ms
Aug 15, 2026863 ms
Aug 22, 2026902 ms
Aug 29, 2026968 ms
Sep 5, 2026977 ms
Sep 12, 2026962 ms
Sep 19, 2026940 ms
Sep 26, 2026909 ms
Oct 3, 2026862 ms
Oct 10, 2026827 ms
Oct 17, 2026828 ms
Real-visitor tap response (INP)75th percentile, phones
172 ms86 msMay 9Oct 17129 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026103 ms
May 16, 202696 ms
May 23, 2026103 ms
May 30, 2026103 ms
Jun 6, 2026104 ms
Jun 13, 2026112 ms
Jun 20, 2026121 ms
Jun 27, 2026128 ms
Jul 4, 2026137 ms
Jul 11, 2026135 ms
Jul 18, 2026162 ms
Jul 25, 2026150 ms
Aug 1, 2026138 ms
Aug 8, 2026144 ms
Aug 15, 2026121 ms
Aug 22, 2026125 ms
Aug 29, 2026121 ms
Sep 5, 2026121 ms
Sep 12, 2026120 ms
Sep 19, 2026121 ms
Sep 26, 2026121 ms
Oct 3, 2026122 ms
Oct 10, 2026128 ms
Oct 17, 2026129 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 aadancecostumes.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix63
  • Main-thread work: 4.7 s

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

  • 3,270 HTML elements

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

  • Improve image delivery

    1,014 KiB

    11 images could be 1,014 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 86). 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 (Shopify, Yotpo and Klaviyo and others), adding 3.3 MB and 604 ms of main-thread time.

  • Shopify adds 241 ms

    241 ms

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

  • Reduce unused JavaScript

    170 ms · 301 KiB

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

  • Reduce unused CSS

    300 ms · 78 KiB

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

  • Use efficient cache lifetimes

    266 KiB

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

  • 4 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 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 fix100
  • Largest Contentful Paint: 10.5 s

    10.5 s

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

  • Time to Interactive: 22.7 s

    22.7 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Tap response (INP) got 29% slower for real visitors

    +29%

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 104 ms

    104 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 470 ms

    470 ms

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

  • Total Blocking Time: 135 ms

    135 ms

    Scripts block the page for only 135 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

3 to fix53
  • Page weight: 5.1 MB in 386 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 386 requests on a phone: images 2.5 MB (20), scripts 1.2 MB (187) and other files 843 KiB (145). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    AA_Dance_Costumes_Copyright_2026_11_ef224222-c0d5-45fb-b842- is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    134 KiB

    2 images are downloaded at several times the size a phone draws them, for example AADanceCostumesCopyright2026_151.jpg at 2,000 px wide, shown at 310 px. Resized copies would save about 134 KiB.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

7 to fixGoogle 8792
  • 8 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Zoom is disabled

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

  • 6 links without text

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

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (1 element)

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 82 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 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
  • Meta description is long (161 characters)

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

  • 173 internal links, 9 external

    The homepage links to 173 pages on aadancecostumes.com and 9 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “AA DANCE COSTUMES”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “AA Dance Costumes - A Dancewear Company.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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://aadancecostumes.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix83
  • 1 page without a meta description

    https://aadancecostumes.com/pages/rewards has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://aadancecostumes.com/collections/leotards, https://aadancecostumes.com/collections/unitards, https://aadancecostumes.com/collections/sets, https://aadancecostumes.com/collections/tops, https://aadancecostumes.com/collections/bottoms and https://aadancecostumes.com/collections/studio-essentials use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://aadancecostumes.com/collections/dresses/Dress-or-Dresses, whose canonical is https://aadancecostumes.com/collections/dresses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://aadancecostumes.com/pages/rewards 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 61 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 7785
  • 7 small tap targets

    7 of 12 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 “Access to XMLHttpRequest at 'https://shopify-extension.getredo.com/7036-a115bc9f.css' from origin 'https://aadancecostu…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 963 words of visible text.

2 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop All”, “Shop the Seville” and “Shop the Regatta”.

  • 4 short forms

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

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 17 cookies set on arrival

    17

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

  • 35 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on aadancecostumes.com, including 14 speed issues, 1 SEO issue 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