ruffwear.ca website review

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

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

ContentSquare costs a phone 1.1 s of main-thread work and 166 KiB 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.

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

8 third-party services load with your homepage (ContentSquare, Klaviyo and Osano CMP and others), adding 1.4 MB and 3.0 s of main-thread time.

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

Klaviyo costs a phone 630 ms of main-thread work and 529 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.

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

Osano CMP costs a phone 490 ms of main-thread work and 84 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.

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

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

reamaze.com costs a phone 313 ms of main-thread work and 216 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 232 ms of main-thread work and 323 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

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 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sweater weather, upgraded. The Timberline Fuse™ Vest delive…”.

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

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

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

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

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

Your homepage downloads 5.4 MB in 413 requests on a phone: images 2.5 MB (67), scripts 1.7 MB (167) and other files 850 KiB (151). Under 2 MB keeps phones on slow connections fast.

ruffworn_950d612d-6847-45e7-a2e5-977f689b24cd.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 are downloaded at several times the size a phone draws them, for example ruffworn_950d612d-6847-45e7-a2e5-977f689b24cd.jpg at 1,300 px wide, shown at 390 px. Resized copies would save about 47 KiB.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 2 <h1> headlines (“Sweater weather, upgraded.” and “One vest. Double the duty.”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 171 pages on ruffwear.ca and 12 external pages.

https://ruffwear.com/collections/ruffworn, https://ruffwear.com/products/front-range-everyday-dog-harness, https://ruffwear.com/products/web-master-harness, https://ruffwear.com/products/dog-harness-flagline, https://ruffwear.com/products/float-coat-dog-life-jacket and https://ruffwear.com/collections/dog-harnesses and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://ruffwear.com/collections/ruffworn 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://ruffwear.com/pages/avalanche-dogs took over 3 s to send its HTML from our server.

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 598 words of visible text.

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

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

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