Website review, no card needed

amanstores.com logo

amanstores.com website review

Visit site (opens in a new tab)Reviewed 1 November 202640 issues · 82 checks

This review found 40 issues worth fixing on amanstores.com, 10 of them high impact, across 82 checks. The most urgent: page weight: 9.0 MB in 207 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.3 s2.1 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.7 s
May 16, 20266.7 s
May 23, 20266.5 s
May 30, 20266.4 s
Jun 6, 20266.3 s
Jun 13, 20266.2 s
Jun 20, 20266.3 s
Jun 27, 20266.3 s
Jul 4, 20266.4 s
Jul 11, 20266.4 s
Jul 18, 20266.4 s
Jul 25, 20266.5 s
Aug 1, 20266.0 s
Aug 8, 20264.9 s
Aug 15, 20263.9 s
Aug 22, 20263.1 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
397 ms312 msMay 9Oct 24322 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026369 ms
May 16, 2026368 ms
May 23, 2026367 ms
May 30, 2026361 ms
Jun 6, 2026375 ms
Jun 13, 2026373 ms
Jun 20, 2026380 ms
Jun 27, 2026387 ms
Jul 4, 2026384 ms
Jul 11, 2026377 ms
Jul 18, 2026364 ms
Jul 25, 2026358 ms
Aug 1, 2026352 ms
Aug 8, 2026362 ms
Aug 15, 2026376 ms
Aug 22, 2026377 ms
Aug 29, 2026378 ms
Sep 5, 2026374 ms
Sep 12, 2026364 ms
Sep 19, 2026360 ms
Sep 26, 2026356 ms
Oct 3, 2026353 ms
Oct 10, 2026341 ms
Oct 17, 2026327 ms
Oct 24, 2026322 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

Full-page screenshot of amanstores.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amanstores.com at 1.0 s1.0 s
  2. amanstores.com at 2.0 s2.0 s
  3. amanstores.com at 2.9 s2.9 s
  4. amanstores.com at 3.9 s3.9 s
  5. amanstores.com at 4.9 s4.9 s
  6. amanstores.com at 5.9 s5.9 s
  7. amanstores.com at 6.9 s6.9 s
  8. amanstores.com at 7.8 s7.8 s

Speed

8 to fix53
  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    600 ms · 5.5 MB

    62 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 53

    53/100

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

  • Reduce unused JavaScript

    915 KiB

    About 915 KiB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and Facebook and others), adding 1.3 MB and 764 ms of main-thread time.

  • Google Tag Manager adds 355 ms

    355 ms

    Google Tag Manager costs a phone 355 ms of main-thread work and 769 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.

  • Render-blocking requests

    400 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

  • 2,481 HTML elements

    The page has 2,481 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    241 KiB

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

  • 19 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 61 KiB

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

  • 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: 189 ms

    189 ms

    Your server sent the HTML in 189 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix0
  • 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.

  • Time to Interactive: 21.6 s

    21.6 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 446 ms

    446 ms

    Real visitors wait 446 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.20

    0.20

    For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

  • Real-user FCP: 2.4 s

    2.4 s

    Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.213

    0.213

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

  • Total Blocking Time: 423 ms

    423 ms

    Scripts block taps and scrolling for 423 ms in total while the page loads. Good is under 200 ms.

3 checks passed
  • Tap response (INP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 369 ms to 322 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 59% faster for real visitors

    -59%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.7 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix33
  • Page weight: 9.0 MB in 207 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 207 requests on a phone: images 6.6 MB (88), scripts 1.9 MB (42) and other files 212 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • About 2.5 g of CO₂ per visit

    2.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.54 g of CO₂e: 304.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 9088
  • 1 button without a name

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 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.

  • 22 text elements with low contrast

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 174 images in the HTML carry an alt attribute.

  • 19 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 22 WCAG 2.2 A/AA and best-practice rules on the phone render: 19 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9279
  • Title is short (24 characters)

    Your title is only 24 characters: “اشتري وقسط مع أمان ستورز”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (197 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 16 links crawlers can't follow

    16 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 92 internal links, 0 external

    The homepage links to 92 pages on amanstores.com and 0 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “موبايل”.

  • Canonical URL set

    The canonical URL is https://www.amanstores.com/ar/.

  • 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://www.amanstores.com/en/sitemap.xml.

AI search readiness

1 to fix83
  • 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://www.amanstores.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.

1 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.

Other pages

2 to fix80
  • 2 pages without a title

    https://www.amanstores.com/ar/best-deal and https://www.amanstores.com/ar/buy-get-offer have no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://www.amanstores.com/ar/best-deal and https://www.amanstores.com/ar/buy-get-offer have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages with very little text

    https://www.amanstores.com/ar/hot-deal, https://www.amanstores.com/ar/victoria-s-secret-bombshell-eau-de-parfum-box-100-ml-for-women-e38-gls, https://www.amanstores.com/ar/women-s-cotton-lycra-pajama-set-imported-premium-fabric-beige-one-size-z105-gls, https://www.amanstores.com/ar/baggy-fit-jeans-ice-marble, https://www.amanstores.com/ar/u-s-polo-assn-laced-sportsman-uomo-navy-45 and https://www.amanstores.com/ar/sokany-glass-electric-water-kettle-2-5-liters-1350-watt-black-sk-09077-7777031021623-ebs-1 and 6 others have 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.

  • 2 pages slow to respond

    https://www.amanstores.com/ar/sokany-glass-electric-water-kettle-2-5-liters-1350-watt-black-sk-09077-7777031021623-ebs-1 and https://www.amanstores.com/ar/braun-texstyle-steam-iron-2000-watt-green-si1040gr-1 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'getRegistrations')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 14 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 amanstores.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on amanstores.com, including 19 speed issues, 5 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25