whiteriver.com website review

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

calconic.com costs a phone 1.3 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (calconic.com, Shopify and JSDelivr CDN and others), adding 5.1 MB and 2.8 s of main-thread time.

About 1.8 MB of JavaScript is downloaded but never used on this page.

20 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

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

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

Shopify costs a phone 371 ms of main-thread work and 2.5 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 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

JSDelivr CDN costs a phone 346 ms of main-thread work and 438 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.

Unpkg costs a phone 237 ms of main-thread work and 469 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.

roseperl.com costs a phone 208 ms of main-thread work and 314 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.

192 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

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 could be saved by minifying CSS.

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

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

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tambour panels and architectural detail — White River Hardw…”.

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

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

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

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

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

Your homepage downloads 8.3 MB in 335 requests on a phone: scripts 3.7 MB (160), media 1.5 MB (1) and images 1.5 MB (19). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Cassidy_New.jpg at 2,326 px wide, shown at 52 px. Resized copies would save about 108 KiB.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

1 image has no alt text, which hurts accessibility and image search.

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

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: “Hardwood Mouldings, Tambour Panels, Corbels & Woodcarvings — White River Hardwoods”.

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

The homepage links to 386 pages on whiteriver.com and 17 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://whiteriver.com/pages/store-locator and https://whiteriver.com/pages/visualizer have no meta description, so Google writes the search snippet from whatever text it finds.

https://whiteriver.com/collections/solid-wood-tambour-panel-collection, https://whiteriver.com/products/tambour-acoustic-wood-panels-display, https://whiteriver.com/collections/mdf-radius-corners-for-fixtures-cabinetry-furniture, https://whiteriver.com/collections/harmony-series-panels-balanced-acoustics-for-every-space and https://whiteriver.com/collections/premium-solid-wood-paneling have no <h1> headline, so visitors and search engines get no clear main topic.

https://whiteriver.com/pages/tambour-acoustic-stone-paneling, https://whiteriver.com/pages/tambour_panel_custom, https://whiteriver.com/products/tambour-acoustic-wood-panels-display, https://whiteriver.com/products/tambour-more-sample-box, https://whiteriver.com/pages/visualizer and https://whiteriver.com/collections/mdf-radius-corners-for-fixtures-cabinetry-furniture took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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