ritterwools.com website review

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

19 images could be 725 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (posthog.com, Shopify and Clarity and others), adding 3.3 MB and 1.4 s of main-thread time.

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

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

posthog.com costs a phone 723 ms of main-thread work and 247 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 366 ms of main-thread work and 2.6 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.

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

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

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

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

17 KiB JavaScript is shipped twice across bundles.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Six people laughing together in Ritter alpaca vests”.

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

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

Real visitors wait 204 ms for the page to respond to a tap (75th percentile). 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 207 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The first text or image appears after 3.0 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 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 478 requests on a phone: scripts 1.9 MB (211), other files 1.0 MB (204) and media 939 KiB (2). Under 2 MB keeps phones on slow connections fast.

10 images further down the page (440 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example RTW_PDP_AlpacaRittervest_Glacier_2.png at 600 px wide, shown at 147 px. Resized copies would save about 75 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.50 g of CO₂e: 180.1 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: 35 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

There are 3 <h1> headlines (“Ritter”, “Search” and “The Rittervest”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 75 pages on ritterwools.com and 4 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.

There is no https://www.ritterwools.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.

Your homepage links to https://www.ritterwools.com/collections/mens-collection, https://www.ritterwools.com/collections/womens-collection and https://www.ritterwools.com/collections/exclusive, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.ritterwools.com/products/alpaca-vest has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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

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