Website review, no card needed

danube.sa logo

danube.sa website review

Visit site (opens in a new tab)Reviewed 31 October 202646 issues · 88 checks

This review found 46 issues worth fixing on danube.sa, 12 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
2.9 s2.4 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
180 ms110 msMay 9Oct 24118 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026167 ms
May 16, 2026172 ms
May 23, 2026171 ms
May 30, 2026163 ms
Jun 6, 2026160 ms
Jun 13, 2026161 ms
Jun 20, 2026156 ms
Jun 27, 2026158 ms
Jul 4, 2026155 ms
Jul 11, 2026146 ms
Jul 18, 2026149 ms
Jul 25, 2026146 ms
Aug 1, 2026148 ms
Aug 8, 2026149 ms
Aug 15, 2026137 ms
Aug 22, 2026126 ms
Aug 29, 2026126 ms
Sep 5, 2026125 ms
Sep 12, 2026126 ms
Sep 19, 2026124 ms
Sep 26, 2026120 ms
Oct 3, 2026119 ms
Oct 10, 2026118 ms
Oct 17, 2026119 ms
Oct 24, 2026118 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 danube.sa (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. danube.sa at 0.4 s0.4 s
  2. danube.sa at 0.8 s0.8 s
  3. danube.sa at 1.1 s1.1 s
  4. danube.sa at 1.5 s1.5 s
  5. danube.sa at 1.9 s1.9 s
  6. danube.sa at 2.3 s2.3 s
  7. danube.sa at 2.6 s2.6 s
  8. danube.sa at 3.0 s3.0 s

Speed

11 to fix55
  • Use efficient cache lifetimes

    3.8 s · 1.2 MB

    27 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Reduce unused JavaScript

    750 ms · 604 KiB

    About 604 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • Render-blocking requests

    850 ms

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

  • Avoid multiple page redirects

    755 ms

    The page goes through 1 redirect before it starts loading, costing about 755 ms. Link and advertise the final URL directly.

  • Improve image delivery

    300 ms · 113 KiB

    5 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 53 KiB

    About 53 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.

  • Document request latency

    350 ms

    The HTML itself could arrive about 350 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Google Maps adds 139 ms

    139 ms

    Google Maps costs a phone 139 ms of main-thread work and 393 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.

  • Google CDN adds 80 ms

    80 ms

    Google CDN costs a phone 80 ms of main-thread work and 352 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Google CDN and Criteo and others), adding 899 KiB and 319 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 373 ms of it running JavaScript. That is comfortably low.

  • Server response: 79 ms

    79 ms

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

Core Web Vitals

8 to fix100
  • 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: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “English الدانوب أونلاين يعمل بشكل أفضل عبر تطبيقنا. احصل عل…”.

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Cumulative Layout Shift: 0.33

    0.33

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 207 ms

    207 ms

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

  • 7 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 62 ms

    62 ms

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

  • Real-user CLS: 0.01

    0.01

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

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

    -30%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 49 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 49 requests on a phone: scripts 1.2 MB (20), images 533 KiB (8) and fonts 260 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (385 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 0.6 g of CO₂ per visit

    0.58 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.8 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

8 to fixGoogle 6687
  • 1 button without a name

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

  • 4 text elements with low contrast

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

  • 23 images without alt text

    23 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 3 elements on the page fail 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.

  • Zoom is disabled

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

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

6 to fixGoogle 9267
  • No H1 headline

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

  • Title is short (17 characters)

    Your title is only 17 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 short (7 characters)

    Your meta description is only 7 characters: “الدانوب”. 70 to 160 characters is enough to sell the click.

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

  • No XML sitemap

    No XML sitemap at https://danube.sa/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 55 internal links, 4 external

    The homepage links to 55 pages on danube.sa and 4 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://danube.sa/.

  • robots.txt in place

    robots.txt is in place.

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://danube.sa/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

4 to fix62
  • 2 linked pages are broken

    Your homepage links to https://danube.sa/en/how-to-shop and https://danube.sa/en/terms-and-conditions, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    / and https://danube.sa/departments all use the title “الدانوب - الدانوب”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages share a meta description

    https://danube.sa/departments, https://danube.sa/ar/departments/online-deals-2024, https://danube.sa/departments/online-deals-2024/5sar-deals, https://danube.sa/departments/promotions, https://danube.sa/departments/online-deals-2024/snacks/chocolate and https://danube.sa/departments/promotions/mobiles-&-tablets and 6 others use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://danube.sa/en, https://danube.sa/departments, https://danube.sa/brochures/351, https://danube.sa/brochures/145, https://danube.sa/brochures/2 and https://danube.sa/brochures/6 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages with very little text

    https://danube.sa/departments, https://danube.sa/ar/departments/online-deals-2024, https://danube.sa/departments/online-deals-2024/5sar-deals, https://danube.sa/departments/promotions, https://danube.sa/departments/online-deals-2024/snacks/chocolate and https://danube.sa/departments/promotions/mobiles-&-tablets 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.

  • 1 page slow to respond

    https://danube.sa/departments took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 20 small tap targets

    20 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

  • Only about 8 words

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

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

4 checks passed
  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Criteo (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.

  • 4 cookies set on arrival

    4

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

  • 16 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Heroku

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on danube.sa, including 19 speed issues, 6 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

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