valyana.com website review

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

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

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

6 images could be 115 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

7 third-party services load with your homepage (helixo.co, Google CDN and Cloudflare CDN and others), adding 235 KiB and 152 ms of main-thread time.

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

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

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

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image (58 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.

By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.7 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 names: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 19 characters: “Sac Maroc – VALYANA”. 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 9 characters: “Sac Maroc”. 70 to 160 characters is enough to sell the click.

The homepage links to 28 pages on valyana.com and 1 external page.

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.

Your homepage links to https://www.valyana.com/www.pinterest.com/valyana.com and https://www.valyana.com/www.instagram.com/valyanamaroc, which answer with an error. Visitors hit a dead end and search engines drop them.

/, https://www.valyana.com/collections/sac-en-bandouliere/products/sac-bandouliere-texture-croco-maroc-sb6023, https://www.valyana.com/collections/sac-en-bandouliere/products/sac-bandouliere-cuir-maroc-sb0072 and https://www.valyana.com/collections/sac-en-bandouliere/products/sac-bandouliere-cuir-maroc-sb1413 all use the title “Sac Maroc – VALYANA”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.valyana.com/collections/sac-en-bandouliere, https://www.valyana.com/collections/sac-a-main, https://www.valyana.com/collections/sac-a-dos and https://www.valyana.com/collections/porte-feuille have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.valyana.com/collections/sac-en-bandouliere/products/sac-bandouliere-texture-croco-maroc-sb6023, whose canonical is https://www.valyana.com/products/sac-bandouliere-texture-croco-maroc-sb6023. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

10 of 39 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: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads 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 6 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.