donnerdeal.com website review

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

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

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and loox.io and others), adding 2.2 MB and 895 ms of main-thread time.

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

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

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

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

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

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

cloudfront.net costs a phone 155 ms of main-thread work and 418 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.

Shopify costs a phone 68 ms of main-thread work and 875 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 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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.

Your largest element takes 28.5 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 29.1 s. Good is under 3.8 s.

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

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

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

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

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

The layout shifts by 0.102 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 5.6 MB in 316 requests on a phone: images 2.2 MB (48), scripts 2.1 MB (77) and other files 944 KiB (178). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

There are 2 <h1> headlines (“Electronic & Digital Music Instruments | Donner® …” and “Discount Code FAQ”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 262 pages on donnerdeal.com and 38 external pages.

https://us.donnermusic.com/policies/refund-policy and https://us.donnermusic.com/collections/donner-all-music-instruments have no meta description, so Google writes the search snippet from whatever text it finds.

https://us.donnermusic.com/pages/sales has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

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.

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

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

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 799 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 5 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 39 cookies (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 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.