turnitupdance.com website review

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 13.2 s faster on a phone.

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

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

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

7 third-party services load with your homepage (Vimeo, Google Tag Manager and JSDelivr CDN and others), adding 22.2 MB and 1.1 s of main-thread time.

Vimeo costs a phone 738 ms of main-thread work and 21.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.

Your mobile performance score is 53 (desktop: 65). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

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

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

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

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

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

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

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

Your homepage downloads 23.1 MB in 256 requests on a phone: other files 18.2 MB (59), scripts 3.7 MB (79) and images 473 KiB (28). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (108 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 60 pages on turnitupdance.com and 23 external pages.

https://turnitupdance.com/dance-tour-dates, https://turnitupdance.com/regional-competitions, https://turnitupdance.com/national-dance-competitions, https://turnitupdance.com/live-stream, https://turnitupdance.com/photosvideos and https://turnitupdance.com/rules-regulations and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://turnitupdance.com/regional-competitions, https://turnitupdance.com/national-dance-competitions, https://turnitupdance.com/dance-conventions, https://turnitupdance.com/about, https://turnitupdance.com/live-stream and https://turnitupdance.com/photosvideos and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://turnitupdance.com/national-dance-competitions, https://turnitupdance.com/photosvideos and https://turnitupdance.com/privacy-policy took over 3 s to send their HTML from our server.

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 ()”.

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

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

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.

The homepage has only about 131 words of visible text; thin pages give Google and first-time buyers little to go on.

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

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.