ruffwear.fr website review

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

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

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

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

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

ContentSquare costs a phone 493 ms of main-thread work and 166 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.

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

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

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

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

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

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.

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 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “La saison des pulls, revisitée. La veste Timberline Fuse™ o…”.

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 262 requests on a phone: images 2.3 MB (58), scripts 1.0 MB (84) and other files 732 KiB (97). 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.22 g of CO₂e: 146.9 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 (“La saison des pulls, revisitée.” and “Une seule veste. Deux fois plus d'efficacité.”). 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)”.

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.fr and 10 external pages.

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

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/reviews-widget-plus/css/okendo-reviews-styles.ffe4027a.css' f…”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 1 more (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 13 cookies (measured from a US location before any click).

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