manuelritz.com website review

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

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

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

64 KiB could be saved by minifying JavaScript.

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

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

Shopify costs a phone 87 ms of main-thread work and 311 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.

8 third-party services load with your homepage (Shopify, Key CDN and pushowl.com and others), adding 841 KiB and 293 ms of main-thread time.

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

6 KiB could be saved by minifying CSS.

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

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

1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 10 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 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Visually, the page fills in at 4.2 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 110 ms to 125 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 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 285 requests on a phone: other files 946 KiB (169), scripts 910 KiB (65) and images 436 KiB (26). Under 2 MB keeps phones on slow connections fast.

FW26_mobile_bimbo_1.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).

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

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

2 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("files/MR_Shopify_logo_2.jpg")”.

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

The homepage links to 98 pages on manuelritz.com and 6 external pages.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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