ritueldefille.com website review

About 1.7 MB 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.

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

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

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

A phone's processor spends 7.4 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 (Shopify, rebuyengine.com and Google Tag Manager and others), adding 3.5 MB and 1.9 s of main-thread time.

rebuyengine.com costs a phone 375 ms of main-thread work and 946 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 378 ms of main-thread work and 496 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.

Google Tag Manager costs a phone 358 ms of main-thread work and 571 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 380 ms. During a long task the page ignores taps.

route.com costs a phone 320 ms of main-thread work and 542 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 images could be 316 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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

13 KiB could be saved by minifying CSS.

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 21.6 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 38.8 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 33.2 MB in 416 requests on a phone: media 26.1 MB (3), scripts 3.7 MB (151) and images 1.8 MB (43). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

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

The homepage links to 143 pages on ritueldefille.com and 10 external pages.

https://ritueldefille.com/collections/s-andromedae-x-rituel-de-fille, https://ritueldefille.com/collections/the-archive-2026, https://ritueldefille.com/collections/thorn-bite-peptide-plump-creme-lip-oil and https://ritueldefille.com/collections/multi-use-creme-color-for-eyes-lips-and-cheeks have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ritueldefille.com/pages/shipping-returns, whose canonical is https://ritueldefille.com/pages/help-center. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ritueldefille.com/pages/shipping-returns, https://ritueldefille.com/collections/s-andromedae-x-rituel-de-fille, https://ritueldefille.com/collections/the-archive-2026, https://ritueldefille.com/collections/bestsellers, https://ritueldefille.com/collections/thorn-bite-peptide-plump-creme-lip-oil and https://ritueldefille.com/collections/enchanted-lip-sheer and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

6 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

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

The homepage carries about 882 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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