rainbowsounds.us website review

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

8 third-party services load with your homepage (route.com, Google CDN and Clarity and others), adding 25.5 MB and 768 ms of main-thread time.

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

About 720 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

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

route.com costs a phone 195 ms of main-thread work and 542 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.

Google CDN costs a phone 134 ms of main-thread work and 296 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 231 ms. During a long task the page ignores taps.

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

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

6 KiB could be saved by minifying CSS.

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 8.1 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 18.0 s. Good is under 3.8 s.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 27.7 MB in 244 requests on a phone: media 24.2 MB (2), scripts 1.5 MB (71) and images 868 KiB (22). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example Auckland-training2_c04dbccc-182a-41cc-a5ad-f8033835fc4a.jpg at 900 px wide, shown at 129 px. Resized copies would save about 190 KiB.

4 images further down the page (313 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 7.85 g of CO₂e: 942.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 124 pages on rainbowsounds.us and 5 external pages.

Your homepage links to https://rainbowsounds.us/collections/crystal-singing-bowls-all, which answers with an error. Visitors hit a dead end and search engines drop it.

https://rainbowsounds.us/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://rainbowsounds.us/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://rainbowsounds.us/collections/online-training/app_extension and https://rainbowsounds.us/collections/online-training all use the title “Online training”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rainbowsounds.us/apps/my/courses/list, https://rainbowsounds.us/blogs/rainbow-sounds-blog, https://rainbowsounds.us/customer_authentication/redirect and https://rainbowsounds.us/collections/best-sellers have no meta description, so Google writes the search snippet from whatever text it finds.

https://rainbowsounds.us/collections/online-training/app_extension and https://rainbowsounds.us/collections/online-training use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://rainbowsounds.us/collections/online-training/app_extension, whose canonical is https://rainbowsounds.us/collections/online-training. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://rainbowsounds.us/apps/my/courses/list, https://rainbowsounds.us/pages/sound-demo, https://rainbowsounds.us/pages/faq, https://rainbowsounds.us/pages/care-guide, https://rainbowsounds.us/pages/contact and https://rainbowsounds.us/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

1 image is served at too low a resolution for sharp phone screens.

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

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 1 more (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 17 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.