rafinity.co.ma website review

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

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

About 198 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 56 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

About 104 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

8 images could be 319 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

10 KiB could be saved by minifying JavaScript.

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

2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 195 KiB and 8 ms of main-thread time.

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

15 KiB could be saved by minifying CSS.

Desktop scores 83 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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 image. Most of its time is resource load delay (7.9 s).

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

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

3 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-17, real Chrome visitors' tap response (inp) went from 87 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

4 images are downloaded at several times the size a phone draws them, for example 6_v3.jpg at 1,920 px wide, shown at 185 px. Resized copies would save about 192 KiB.

5 images (324 KiB) are 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.

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

6 tap targets are too small or too close together to hit reliably with a finger.

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: 4 elements on the page fail this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 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 meta description is only 22 characters: “Créateurs de tendances”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Bijoux pour homme” and “Les montres Bovet”). One clear main headline is easier for people and search engines.

No XML sitemap at https://rafinity.co.ma/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at rafinity.co.ma/robots.txt, the first file search crawlers ask for.

The homepage links to 50 pages on rafinity.co.ma and 10 external pages.

There is no https://rafinity.co.ma/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.

/ and https://rafinity.co.ma/en all use the title “Rafinity.co.ma - Joaillerie luxe et fashion - Diamants et or 18k”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rafinity.co.ma/en took over 3 s to send its HTML from our server.

We fetched 1 page linked from your homepage and read each the way a search engine does.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 1 cookie (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.