ric3.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, rebuyengine.com and Klaviyo and others), adding 2.0 MB and 1.2 s of main-thread time.

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

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

Google Tag Manager costs a phone 311 ms of main-thread work and 325 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.

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

rebuyengine.com costs a phone 233 ms of main-thread work and 656 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.

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

5 KiB could be saved by minifying CSS.

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

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

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 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

The layout shifts by 0.615 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

L1210324-2_1.jpg weighs 520 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 4.0 MB in 269 requests on a phone: scripts 2.1 MB (106), other files 844 KiB (132) and images 726 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example L1210324-2_1.jpg at 2,048 px wide, shown at 340 px. Resized copies would save about 391 KiB.

1 image (520 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (520 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

5 dropdowns have no label.

2 buttons have no accessible name, so screen readers announce just “button”.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 28 characters: “Enchanté by Daniel Ricciardo”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 29 characters: “The go-to F1 lifestyle brand.”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Enchanté” and “Enchanté x Ford Racing: Long Road to Austin”). One clear main headline is easier for people and search engines.

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

The homepage links to 72 pages on ric3.com and 10 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.

https://enchante.co/collections/long-road-to-austin, https://enchante.co/collections/new-arrivals, https://enchante.co/collections/shop-all, https://enchante.co/collections/tees, https://enchante.co/collections/crewnecks and https://enchante.co/collections/hoodies and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://enchante.co/collections has no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getAttribute')”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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