windriverchimes.com website review

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

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

8 third-party services load with your homepage (FontAwesome CDN, Shopify and Google Tag Manager and others), adding 1.7 MB and 1.6 s of main-thread time.

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

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

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

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

FontAwesome CDN costs a phone 786 ms of main-thread work and 27 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 205 ms of main-thread work and 930 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.

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

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

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

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

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

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

Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Enjoy 10% Off All Wind River Chimes!”.

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

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

11 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' tap response (inp) went from 121 ms to 132 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 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.8 MB in 355 requests on a phone: scripts 2.1 MB (141), other files 1.2 MB (140) and images 1.1 MB (29). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 10_Mobile_Banner_Sale_-_Mobile.png at 1,890 px wide, shown at 390 px. Resized copies would save about 105 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

All page content should be contained by landmarks: 10 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 (h1 → h3), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“Enjoy 10% Off All Wind River Chimes!” and “Frequently Asked Questions”). One clear main headline is easier for people and search engines.

23 links have no real href, so search engines can't follow them.

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

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

The homepage links to 385 pages on windriverchimes.com and 14 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://windriverchimes.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

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

https://windriverchimes.com/customer_authentication/redirect and https://windriverchimes.com/collections/featured-chimes have no meta description, so Google writes the search snippet from whatever text it finds.

https://windriverchimes.com/pages/giveaway, https://windriverchimes.com/customer_authentication/redirect, https://windriverchimes.com/collections/all-wind-chimes and https://windriverchimes.com/collections/featured-chimes have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: dataLayer is not defined”.

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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 1,907 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 15 cookies (measured from a US location before any click).

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