Website review, no card needed

dancewearcorner.com logo

dancewearcorner.com website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 85 checks

This review found 32 issues worth fixing on dancewearcorner.com, 10 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.2 s1.7 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
135 ms109 msMay 16Oct 31122 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026112 ms
May 30, 2026117 ms
Jun 6, 2026121 ms
Jun 13, 2026128 ms
Jun 20, 2026129 ms
Jun 27, 2026129 ms
Jul 4, 2026132 ms
Jul 11, 2026128 ms
Jul 18, 2026122 ms
Jul 25, 2026125 ms
Aug 1, 2026126 ms
Aug 8, 2026125 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026128 ms
Sep 19, 2026129 ms
Sep 26, 2026129 ms
Oct 3, 2026129 ms
Oct 10, 2026131 ms
Oct 17, 2026131 ms
Oct 24, 2026128 ms
Oct 31, 2026122 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 dancewearcorner.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dancewearcorner.com at 1.4 s1.4 s
  2. dancewearcorner.com at 2.9 s2.9 s
  3. dancewearcorner.com at 4.3 s4.3 s
  4. dancewearcorner.com at 5.8 s5.8 s
  5. dancewearcorner.com at 7.2 s7.2 s
  6. dancewearcorner.com at 8.7 s8.7 s
  7. dancewearcorner.com at 10.1 s10.1 s
  8. dancewearcorner.com at 11.6 s11.6 s

Speed

12 to fix50
  • Main-thread work: 8.9 s

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

  • 4,889 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and Bold Commerce and others), adding 3.9 MB and 1.5 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Render-blocking requests

    950 ms

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

  • Reduce unused JavaScript

    676 KiB

    About 676 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 346 ms

    346 ms

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

  • Use efficient cache lifetimes

    100 ms · 401 KiB

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

  • Klaviyo adds 324 ms

    324 ms

    Klaviyo costs a phone 324 ms of main-thread work and 614 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.

  • 18 long tasks on the main thread

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

  • Bold Commerce adds 265 ms

    265 ms

    Bold Commerce costs a phone 265 ms of main-thread work and 484 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.

  • smile.io adds 107 ms

    107 ms

    smile.io costs a phone 107 ms of main-thread work and 457 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.

  • Reduce unused CSS

    150 ms · 133 KiB

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

  • Improve image delivery

    135 KiB

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

  • Legacy JavaScript

    90 KiB

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

  • Minify CSS

    6 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

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

  • Time to Interactive: 28.4 s

    28.4 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • Total Blocking Time: 795 ms

    795 ms

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

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

    +12%

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

6 checks passed
  • Real-user INP: 155 ms

    155 ms

    Real visitors wait 155 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 TTFB: 784 ms

    784 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

3 to fix53
  • Page weight: 6.5 MB in 586 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 586 requests on a phone: scripts 2.4 MB (290), other files 1.1 MB (185) and images 1.1 MB (53). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    holidayguidefordancers.jpg 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).

  • 1 image far larger than shown

    22 KiB

    1 image is downloaded at several times the size a phone draws it, for example holidayguidefordancers.jpg at 1,376 px wide, shown at 390 px. Resized copies would save about 22 KiB.

  • About 1.8 g of CO₂ per visit

    1.84 g

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

2 to fixGoogle 9797
  • 2 text elements with low contrast

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

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

  • 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 186 images in the HTML carry an alt attribute.

  • 53 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: 53 passed and 2 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Pointe Shoes & Premium Dancewear | Dancewear Corner – DanceWear Corner”.

  • Structured data has 1 problem

    Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("dancewearcorner.com")”.

  • No social preview image

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

  • 422 internal links, 13 external

    The homepage links to 422 pages on dancewearcorner.com and 13 external pages.

5 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Shop pointe shoes, ballet shoes, leotards & dancewear from top brands. Expert fit guidance & fast shipping — only at Da…”.

  • One H1 headline

    Your main headline reads: “DanceWear Corner”.

  • Canonical URL set

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

  • 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://dancewearcorner.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 (3,695 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix75
  • 1 page without a title

    https://dancewearcorner.com/products/dancegiftcard has no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://dancewearcorner.com/pages/contact-us and https://dancewearcorner.com/products/dancegiftcard have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://dancewearcorner.com/pages/contact-us, https://dancewearcorner.com/products/dancegiftcard, https://dancewearcorner.com/collections/whats-new, https://dancewearcorner.com/collections/pointe-shoes, https://dancewearcorner.com/collections/suffolk-pointe-shoes and https://dancewearcorner.com/collections/r-class-pointe-shoes and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://dancewearcorner.com/collections/pointe-shoes took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 194 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.

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

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No opening hours

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

  • 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 2,689 words of copy

    The homepage carries about 2,689 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: “SHOP GIFTS”.

  • 40 calls to action

    The homepage has 40 calls to action, for example “Contact Us”, “Shop All Pointe Shoes” and “Shop All Tights”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 8 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

  • 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
  • 3 trackers load before any consent

    3

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

  • 12 cookies set on arrival

    12

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

  • 41 other companies contacted

    Loading the homepage contacts 41 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 dancewearcorner.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Redo · Bold Subscriptions · Judge Me Reviews · Gift Card Pro · Seo Manager Venntov · Klaviyo Email Marketing Sms · Fondue Cashback Promotions · Smart Wishlist · Microsoft Clarity · Pushowl · amazonaws.com · gorgias.chat · getredo.com · 9gtb.com · hubapi.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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Orlando

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on dancewearcorner.com, including 19 speed issues and 3 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