Website review, no card needed
mysadaka.it website review
Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 79 checks
This review found 35 issues worth fixing on mysadaka.it, 10 of them high impact, across 79 checks. The most urgent: avoid multiple page redirects. 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
One score from every part of this review. How it works
Speed
Avoid multiple page redirects
6.9 sThe page goes through 4 redirects before it starts loading, costing about 6.9 s. Link and advertise the final URL directly.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (mysadaka.com, Google Tag Manager and Google Fonts and others), adding 1.8 MB and 701 ms of main-thread time.
mysadaka.com adds 700 ms
700 msmysadaka.com costs a phone 700 ms of main-thread work and 1.4 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.
Document request latency
600 msThe HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused JavaScript
150 ms · 254 KiBAbout 254 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
400 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Use efficient cache lifetimes
384 KiB11 files are served with short cache lifetimes, so returning visitors download them again (384 KiB).
Legacy JavaScript
150 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 159 ms. During a long task the page ignores taps.
Duplicated JavaScript
51 KiB51 KiB JavaScript is shipped twice across bundles.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 872 ms of it running JavaScript. That is comfortably low.
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.3 s
12.3 sYour largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mysadaka”.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
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: 1.8 s
1.8 sReal visitors wait 1.8 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: 586 ms
586 msReal visitors wait 586 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 113 ms
113 msScripts block the page for only 113 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 111 requests
3.1 MBYour homepage downloads 3.1 MB in 111 requests on a phone: scripts 1.2 MB (58), images 1.1 MB (16) and fonts 511 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
5 tap targets too small
5 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
48 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: 48 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (8 characters)
Your title is only 8 characters: “Mysadaka”. Between 30 and 65 characters leaves room to say what you do and for whom.
Canonical points to another host
Your canonical URL points to mysadaka.com, not mysadaka.it, so Google may credit that host instead.
2 H1 headlines
There are 2 <h1> headlines (“Mysadaka” and “Construction d'une place d’ablution pour une mosq…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
35 internal links, 15 external
The homepage links to 35 pages on mysadaka.it and 15 external pages.
3 checks passed
Structured data in place
Structured data found: FAQPage.
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://mysadaka.it/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.
Some text only appears after JavaScript runs
50%The HTML your server sends has 788 of the 1,564 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://mysadaka.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://mysadaka.it/pages/concours-omra-ramadan-2025, which answers with an error. Visitors hit a dead end and search engines drop it.
14 linked pages hidden from search
https://mysadaka.it/products/mon-fauteuil-roulant-a-makkah, https://mysadaka.it/products/mon-coran-a-makkah, https://mysadaka.it/products/place-d-ablution-1-18-a-votre-nom, https://mysadaka.it/products/hajj-mysadaka, https://mysadaka.it/products/omra-badal and https://mysadaka.it/pages/elhudadaawa and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
10 pages without a meta description
https://mysadaka.it/products/place-d-ablution-1-18-a-votre-nom, https://mysadaka.it/pages/elhudadaawa, https://mysadaka.it/pages/faq, https://mysadaka.it/pages/contact, https://mysadaka.it/collections/all and https://mysadaka.it/policies/shipping-policy and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://mysadaka.it/products/place-d-ablution-1-18-a-votre-nom, https://mysadaka.it/pages/elhudadaawa, https://mysadaka.it/pages/faq, https://mysadaka.it/pages/contact, https://mysadaka.it/pages/avis and https://mysadaka.it/pages/qui-sommes-nous have 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 22 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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,564 words of copy
The homepage carries about 1,564 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 4 of them by other companies (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.
9 other companies contacted
Loading the homepage contacts 9 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 mysadaka.it, 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 21 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Whatsapp Ck · Vitals · Replaypro · Avada Seo Suite · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Thoughtmetric · Omnise Ai Builder · Ecomposer Builder · Addingwell · Judge Me Reviews · Whatsapp Abandoned Cart · Dondy Whatsapp Chat Widget · Locales Ai · Gdpr Backpack · cloudfront.net · snapchat.com · luckyorange.com · boxtal.com · loox.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on mysadaka.it, including 12 speed issues, 7 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.