dancingdeer.com website review

About 605 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Clarity and Accessibe Accessibility Overlay and others), adding 5.9 MB and 534 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

33 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

14 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, 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).

Your homepage downloads 8.5 MB in 243 requests on a phone: other files 5.2 MB (114), scripts 1.5 MB (72) and images 1.4 MB (39). Under 2 MB keeps phones on slow connections fast.

9 images further down the page (721 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example DD_MiddleBanner.jpg at 2,440 px wide, shown at 390 px. Resized copies would save about 189 KiB.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your <h1> is empty.

The homepage links to 232 pages on dancingdeer.com and 15 external pages.

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.

Your homepage links to https://www.dancingdeer.com/collections/gift-boxes, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.dancingdeer.com/collections/new-creations-1, https://www.dancingdeer.com/collections/cookie-collection, https://www.dancingdeer.com/collections/brownie-collection, https://www.dancingdeer.com/collections/gluten-free-collection, https://www.dancingdeer.com/collections/chocolate and https://www.dancingdeer.com/collections/caramel and 8 others have no <title>, so Google invents the link text in results.

https://www.dancingdeer.com/collections/new-creations-1, https://www.dancingdeer.com/collections/cookie-collection, https://www.dancingdeer.com/collections/brownie-collection, https://www.dancingdeer.com/collections/gluten-free-collection, https://www.dancingdeer.com/collections/chocolate and https://www.dancingdeer.com/collections/caramel and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.dancingdeer.com/collections/new-creations-1, https://www.dancingdeer.com/collections/cookie-collection, https://www.dancingdeer.com/collections/brownie-collection, https://www.dancingdeer.com/collections/gluten-free-collection, https://www.dancingdeer.com/collections/chocolate and https://www.dancingdeer.com/collections/caramel and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 839 words of visible text.

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

Opening the homepage sets 22 cookies, 4 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.