ruffwear.eu website review

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

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

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

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

8 third-party services load with your homepage (ContentSquare, Osano CMP and Klaviyo and others), adding 679 KiB and 584 ms of main-thread time.

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

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

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

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

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

Polyfills for old browsers add 25 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.

Your largest element takes 12.7 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 12.8 s. Good is under 3.8 s.

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

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

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

Your homepage downloads 4.4 MB in 286 requests on a phone: images 2.3 MB (58), scripts 964 KiB (81) and other files 832 KiB (126). Under 2 MB keeps phones on slow connections fast.

Web_JPG-0568_Sun-Shower-Coverall_Midnight-Blue_Oakridge-21.j 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).

1 image is downloaded at several times the size a phone draws it, for example Web_JPG-0568_Sun-Shower-Coverall_Midnight-Blue_Oakridge-21.j at 1,300 px wide, shown at 390 px. Resized copies would save about 17 KiB.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 2 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 2 problems, for example “Organization: url points at a different host (http://www.ruffwear.com)”.

There is no robots.txt at ruffwear.eu/robots.txt, the first file search crawlers ask for.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 132 pages on ruffwear.eu and 10 external pages.

https://ruffwear.eu/pages/partners-in-grime, https://ruffwear.eu/collections/dog-boots and https://ruffwear.eu/collections/dog-collars took over 3 s to send their HTML from our server.

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

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

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

The homepage carries about 515 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and TikTok Pixel (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 8 cookies (measured from a US location before any click).

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