zikforyou.com website review

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

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

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

Shopify costs a phone 274 ms of main-thread work and 648 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, willdesk.com and Cloudflare CDN and others), adding 925 KiB and 349 ms of main-thread time.

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

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

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

Polyfills for old browsers add 17 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.

2 KiB could be saved by minifying CSS.

Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Chanson d’amour commandée pour exprimer vos sentiments”.

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

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

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

The first text or image appears after 1.8 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.

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.

Your homepage downloads 2.1 MB in 192 requests on a phone: scripts 1,000 KiB (58), other files 702 KiB (88) and images 168 KiB (5). Under 2 MB keeps phones on slow connections fast.

Chanson-d-amour-sur-commande.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).

1 image (67 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.59 g of CO₂e: 71.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Your title is 70 characters, so Google will cut it off around 60: “Chanson personnalisée unique – Le cadeau personnalisé idéal |ZikForYou”.

Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 25 pages on zikforyou.com and 7 external pages.

https://zikforyou.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://zikforyou.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://zikforyou.com/blogs/les-occasions-speciales, https://zikforyou.com/customer_authentication/redirect, https://zikforyou.com/a/faq and https://zikforyou.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://zikforyou.com/customer_authentication/redirect, https://zikforyou.com/a/faq and https://zikforyou.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://zikforyou.com/pages/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Soundbite: You must include an element for the widget to attach to. Check https://soundbite.so/help for…”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,065 words of visible text.

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