Website review, no card needed

adawliahshop.com logo

adawliahshop.com website review

Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 92 checks

This review found 43 issues worth fixing on adawliahshop.com, 20 of them high impact, across 92 checks. The most urgent: mobile performance score: 38. 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
6.1 s1.3 sMay 2Oct 175.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.3 s
Aug 22, 20262.6 s
Sep 12, 20263.5 s
Sep 19, 20264.4 s
Sep 26, 20265.0 s
Oct 3, 20265.2 s
Oct 10, 20265.4 s
Oct 17, 20265.5 s
Real-visitor tap response (INP)75th percentile, phones
329 ms182 msMay 2Oct 17296 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026230 ms
May 9, 2026231 ms
May 16, 2026230 ms
May 23, 2026204 ms
May 30, 2026201 ms
Jun 6, 2026202 ms
Jun 13, 2026201 ms
Jun 20, 2026199 ms
Jun 27, 2026201 ms
Jul 4, 2026202 ms
Jul 11, 2026203 ms
Jul 18, 2026209 ms
Jul 25, 2026210 ms
Aug 1, 2026216 ms
Aug 8, 2026230 ms
Aug 15, 2026245 ms
Aug 22, 2026263 ms
Sep 12, 2026289 ms
Sep 19, 2026312 ms
Sep 26, 2026312 ms
Oct 3, 2026304 ms
Oct 10, 2026303 ms
Oct 17, 2026296 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 adawliahshop.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adawliahshop.com at 1.2 s1.2 s
  2. adawliahshop.com at 2.5 s2.5 s
  3. adawliahshop.com at 3.7 s3.7 s
  4. adawliahshop.com at 4.9 s4.9 s
  5. adawliahshop.com at 6.1 s6.1 s
  6. adawliahshop.com at 7.4 s7.4 s
  7. adawliahshop.com at 8.6 s8.6 s
  8. adawliahshop.com at 9.8 s9.8 s

Speed

9 to fix38
  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.1 s

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

  • 3,772 HTML elements

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

  • Improve image delivery

    800 ms · 1.9 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and fynd.com and others), adding 6.0 MB and 589 ms of main-thread time.

  • Reduce unused JavaScript

    998 KiB

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

  • fynd.com adds 141 ms

    141 ms

    fynd.com costs a phone 141 ms of main-thread work and 5.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.

  • 18 long tasks on the main thread

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

  • Google Tag Manager adds 254 ms

    254 ms

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

  • Use efficient cache lifetimes

    223 KiB

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

  • Reduce unused CSS

    56 KiB

    About 56 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

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

    310 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.28

    0.28

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Time to Interactive: 20.4 s

    20.4 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • Total Blocking Time: 956 ms

    956 ms

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

  • First Contentful Paint: 3.3 s

    3.3 s

    The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user INP: 370 ms

    370 ms

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

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • Largest content (LCP) got 154% slower for real visitors

    +154%

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

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix50
  • Page weight: 6.8 MB in 206 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 206 requests on a phone: images 3.3 MB (81), other files 1.8 MB (86) and scripts 1.2 MB (28). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    630 KiB

    6 images are downloaded at several times the size a phone draws them, for example BOSE-HP-Mobile-EN01-2.png at 1,200 px wide, shown at 358 px. Resized copies would save about 630 KiB.

  • An image on the first screen is lazy-loaded

    BOSE-HP-Mobile-EN01-2.png 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).

  • 3 images below the first screen load straight away

    3 images further down the page (251 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (33 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.9 g of CO₂ per visit

    1.92 g

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

Accessibility

8 to fixGoogle 8289
  • 15 text elements with low contrast

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

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    6 elements hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (109 elements)

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

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (6 elements).

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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

3 to fixGoogle 10080
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “Musical Instruments & Pro Audio in Saudi Arabia | aDawliah - Official Online Store”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 133 internal links, 16 external

    The homepage links to 133 pages on adawliahshop.com and 16 external pages.

5 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Shop guitars, pianos, keyboards, drums, musical instruments, professional audio and AV equipment online at aDawliah wit…”.

  • Canonical URL set

    The canonical URL is https://adawliahshop.com/.

  • Structured data in place

    Structured data found: LocalBusiness, Organization and WebSite.

  • 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://adawliahshop.com/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    19%

    A phone browser shows 1,526 words, but the HTML your server sends has only 294. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

3 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • llms.txt published

    The site publishes https://adawliahshop.com/llms.txt (9 KiB, 34 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 11 pages without an H1

    https://adawliahshop.com/brands, https://adawliahshop.com/collection/special-offers, https://adawliahshop.com/collection/complete-solutions, https://adawliahshop.com/collection/headphones-av, https://adawliahshop.com/collection/guitar-and-bass and https://adawliahshop.com/collection/shop-av-gears and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://adawliahshop.com/collection/drums-and-percussion took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 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

2 to fixGoogle 9290
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 27 distorted images

    27 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    162 of 192 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • 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 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.

  • About 1,526 words of copy

    The homepage carries about 1,526 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Track your order”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Track your order”, “Talk to our experts” and “Shop AV Gears”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 adawliahshop.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
Tailwind CSS
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on adawliahshop.com, including 23 speed issues, 3 SEO issues and 1 conversion gap. 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