Website review, no card needed
uniikon.com website review
Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 84 checks
This review found 33 issues worth fixing on uniikon.com, 12 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #22,712 of 97,925 reviewed websitesbeats 72%
- #14,467 of 53,390 online storesbeats 66%
- #14,010 of 48,418 Shopify storesbeats 64%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 158 ms |
| May 23, 2026 | 164 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 174 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 176 ms |
| Jul 11, 2026 | 176 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 174 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 188 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 175 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 172 ms |
| Oct 24, 2026 | 169 ms |
| Oct 31, 2026 | 168 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
5.0 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 361 KiB25 files are served with short cache lifetimes, so returning visitors download them again (361 KiB).
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, loox.io and Klaviyo and others), adding 11.0 MB and 980 ms of main-thread time.
Shopify adds 57 ms
57 msShopify costs a phone 57 ms of main-thread work and 9.7 MB 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.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Minify JavaScript
350 ms · 80 KiB80 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 366 ms
366 msGoogle Tag Manager costs a phone 366 ms of main-thread work and 479 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.
Reduce unused CSS
300 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,864 HTML elements
The page has 2,864 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 211 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 20.8 s
20.8 sYour largest element takes 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 21.2 s
21.2 sThe page becomes fully interactive after 21.2 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
34 images without width and height
34 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 306 ms
306 msScripts block taps and scrolling for 306 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 158 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 465 ms
465 msReal visitors wait 465 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 14.7 MB in 288 requests
14.7 MBYour homepage downloads 14.7 MB in 288 requests on a phone: media 9.5 MB (5), images 2.1 MB (73) and scripts 2.0 MB (105). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
589 KiB8 images are downloaded at several times the size a phone draws them, for example lissage_indiana_700x.webp at 700 px wide, shown at 69 px. Resized copies would save about 589 KiB.
10 images below the first screen load straight away
10 images further down the page (651 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (460 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.
About 4.2 g of CO₂ per visit
4.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.17 g of CO₂e: 500.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
[role="img"] and [role="image"] elements must have alternative text (4 elements)
[role="img"] and [role="image"] elements must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
53 links without text
53 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (24 elements).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Big hair Big dream by Uniikon, des cheveux plus forts et plus sains”.
Meta description is long (298 characters)
Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.
236 internal links, 25 external
The homepage links to 236 pages on uniikon.com and 25 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Résultats Réels”.
Canonical URL set
The canonical URL is https://uniikon.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://uniikon.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,730 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://uniikon.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://uniikon.com/collections/shop-all, https://uniikon.com/collections/nouveautes, https://uniikon.com/collections/les-gammes, https://uniikon.com/collections/gamme-rosemary-1, https://uniikon.com/collections/gamme-maxlift and https://uniikon.com/collections/brume-capillaire and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://uniikon.com/collections/gamme-maxlift, https://uniikon.com/collections/brume-capillaire, https://uniikon.com/collections/gamme-afro-curl, https://uniikon.com/collections/gamme-the-one, https://uniikon.com/collections/gamme-resistance and https://uniikon.com/collections/gamme-detox-metal and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
30 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,689 words of copy
The homepage carries about 1,689 words of visible text.
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact” and “Contact Pro & B2B”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 16 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
No consent tool detected
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.
53 other companies contacted
Loading the homepage contacts 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at uniikon.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Uplinkly Sticky Cart · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Scalapay On Site Messaging · Weglot Translate Your Store · Icart Cart Upsell · Instafeed · Avada Seo Ai Blog · Selleasy · Sales Shield · Scalapay Widget Installer Prod · Bitbybit Loyalty · machinads.io · cloudfront.net · snapchat.com · loox.io · widebundle.com · trustpilot.com · identixweb.com · useamp.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
- The footer still says © 2024.
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on uniikon.com, including 17 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.