Website review, no card needed
justyol.com website review
Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 83 checks
This review found 31 issues worth fixing on justyol.com, 9 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
78C- #48,935 of 96,298 reviewed websitesbeats 44%
- #30,701 of 52,142 online storesbeats 36%
- #29,238 of 47,229 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 276 ms |
| May 23, 2026 | 291 ms |
| May 30, 2026 | 304 ms |
| Jun 6, 2026 | 311 ms |
| Jun 13, 2026 | 317 ms |
| Jun 20, 2026 | 323 ms |
| Jun 27, 2026 | 337 ms |
| Jul 4, 2026 | 331 ms |
| Jul 11, 2026 | 313 ms |
| Jul 18, 2026 | 290 ms |
| Jul 25, 2026 | 264 ms |
| Aug 1, 2026 | 257 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 274 ms |
| Aug 22, 2026 | 280 ms |
| Aug 29, 2026 | 281 ms |
| Sep 5, 2026 | 273 ms |
| Sep 12, 2026 | 272 ms |
| Sep 19, 2026 | 261 ms |
| Sep 26, 2026 | 256 ms |
| Oct 3, 2026 | 244 ms |
| Oct 10, 2026 | 231 ms |
| Oct 17, 2026 | 229 ms |
| Oct 24, 2026 | 236 ms |
| Oct 31, 2026 | 236 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
5,086 HTML elements
The page has 5,086 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 818 KiB28 images could be 818 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
800 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
5 third-party services on the page
5 third-party services load with your homepage (Clarity, Google Tag Manager and Shopify and others), adding 334 KiB and 286 ms of main-thread time.
Reduce unused CSS
280 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
Reduce unused JavaScript
174 KiBAbout 174 KiB of JavaScript is downloaded but never used on this page.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Duplicated JavaScript
23 KiB23 KiB JavaScript is shipped twice across bundles.
Use efficient cache lifetimes
18 KiB3 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “⚡ Ventes Flash jusqu'à −50%”.
Real-user INP: 236 ms
236 msReal visitors wait 236 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Time to Interactive: 7.2 s
7.2 sThe page becomes fully interactive after 7.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.19
0.19The layout shifts by 0.19 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
8 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 514 ms
514 msReal visitors wait 514 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 276 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 77 ms
77 msScripts block the page for only 77 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 257 requests
3.5 MBYour homepage downloads 3.5 MB in 257 requests on a phone: images 2.1 MB (88), other files 788 KiB (111) and scripts 491 KiB (46). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (50 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.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
29 tap targets too small
29 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (19 elements)
Alternative text of images should not be repeated as text: 19 elements on the page fail this check, rated minor by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (36 elements).
2 checks passed
Every image has alt text
All 372 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 1 more 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: “Justyol – Achat en Ligne au Maroc | Mode, Maison et plus à Bon Prix”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
572 internal links, 1 external
The homepage links to 572 pages on justyol.com and 1 external page.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Justyol est une marketplace marocaine qui privilégie la qualité. Nous sélectionnons des produits turcs fiables et tenda…”.
One H1 headline
Your main headline reads: “Le meilleur de la mode turque, livré chez vous.”.
Canonical URL set
The canonical URL is https://justyol.com/.
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://justyol.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://justyol.com/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (3,232 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://justyol.com/pages/wishlist and https://justyol.com/pages/mon-compte are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages share a meta description
https://justyol.com/pages/black-friday and https://justyol.com/pages/black-friday-game use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://justyol.com/pages/black-friday has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 181 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 8 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
112 of 113 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 875 words of copy
The homepage carries about 875 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 5 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
25 other companies contacted
Loading the homepage contacts 25 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 justyol.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
zoko.io
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
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on justyol.com, including 11 speed issues, 2 SEO issues and 3 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.