balmyworld.com website review

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

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

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

8 third-party services load with your homepage (Clarity, Klaviyo and Google Tag Manager and others), adding 1.1 MB and 443 ms of main-thread time.

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

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

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

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

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

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

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

About 35 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB JavaScript is shipped twice across bundles.

Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A calming instrument anyone can play in minutes.”.

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

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

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

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

balmy-world-steel-tongue-drums-hero-1mobile.webp weighs 658 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.0 MB in 225 requests on a phone: scripts 1.0 MB (79), images 970 KiB (40) and other files 699 KiB (70). Under 2 MB keeps phones on slow connections fast.

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

2 images (892 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image is downloaded at several times the size a phone draws it, for example Image-Aryakiddingme-1.webp at 1,200 px wide, shown at 360 px. Resized copies would save about 45 KiB.

1 image further down the page (234 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 0.84 g of CO₂e: 101.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 82 characters, so Google will cut it off around 60: “Steel Tongue Drum – Easy to Play, Relaxing & Fun for All Ages | Balmy – Balmy Drum”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“A calming instrument anyone can play in minutes.” and “Balmy World - For Children”). One clear main headline is easier for people and search engines.

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

The homepage links to 46 pages on balmyworld.com and 2 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.

https://www.balmyworld.com/policies/shipping-policy and https://www.balmyworld.com/pages/shipping-policy all use the title “Shipping policy – Balmy Drum”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.balmyworld.com/collections/all, https://www.balmyworld.com/collections/best-collection, https://www.balmyworld.com/policies/shipping-policy, https://www.balmyworld.com/pages/how-to-play, https://www.balmyworld.com/pages/blog and https://www.balmyworld.com/collections/accessories and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.balmyworld.com/apps/tracktor, whose canonical is https://www.balmyworld.com/apps/tracktor/track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.balmyworld.com/collections/best-collection, https://www.balmyworld.com/collections/accessories, https://www.balmyworld.com/collections/books and https://www.balmyworld.com/apps/tracktor have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.balmyworld.com/apps/tracktor has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.balmyworld.com/pages/how-to-play took over 3 s to send its HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

The homepage carries about 1,887 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 20 cookies, 3 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.