Website review, no card needed

almajed4oud.com logo

almajed4oud.com website review

Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 85 checks

This review found 34 issues worth fixing on almajed4oud.com, 15 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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.8 s1.8 sMay 9Oct 101.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.5 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
201 ms175 msMay 9Oct 10194 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026180 ms
May 16, 2026181 ms
May 23, 2026184 ms
May 30, 2026182 ms
Jun 6, 2026180 ms
Jun 13, 2026178 ms
Jun 20, 2026178 ms
Jun 27, 2026178 ms
Jul 4, 2026178 ms
Jul 11, 2026180 ms
Jul 18, 2026180 ms
Jul 25, 2026180 ms
Aug 1, 2026187 ms
Aug 8, 2026187 ms
Aug 15, 2026191 ms
Aug 22, 2026195 ms
Aug 29, 2026193 ms
Sep 5, 2026196 ms
Sep 12, 2026195 ms
Sep 19, 2026195 ms
Sep 26, 2026198 ms
Oct 3, 2026195 ms
Oct 10, 2026194 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 almajed4oud.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. almajed4oud.com at 0.9 s0.9 s
  2. almajed4oud.com at 1.9 s1.9 s
  3. almajed4oud.com at 2.8 s2.8 s
  4. almajed4oud.com at 3.8 s3.8 s
  5. almajed4oud.com at 4.7 s4.7 s
  6. almajed4oud.com at 5.7 s5.7 s
  7. almajed4oud.com at 6.6 s6.6 s
  8. almajed4oud.com at 7.6 s7.6 s

Speed

12 to fix10
  • Reduce unused JavaScript

    1.7 s · 892 KiB

    About 892 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Render-blocking requests

    1.7 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.

  • Mobile performance score: 10

    10/100

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

  • Main-thread work: 6.4 s

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

  • Use efficient cache lifetimes

    950 ms · 5.4 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, salla.network and Facebook and others), adding 19.4 MB and 2.2 s of main-thread time.

  • salla.network adds 617 ms

    617 ms

    salla.network costs a phone 617 ms of main-thread work and 18.1 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.

  • Improve image delivery

    350 ms · 1.3 MB

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

  • Google Tag Manager adds 895 ms

    895 ms

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

  • Reduce unused CSS

    460 ms · 61 KiB

    About 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • 2,595 HTML elements

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

  • Legacy JavaScript

    21 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 38 but mobile only 10. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

    3 ms

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

Core Web Vitals

9 to fix67
  • 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: 1.38

    1.38

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

  • Cumulative Layout Shift: 2.037

    2.037

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

  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Al Majed for Oud: Finest Oud & Perfume Products”.

  • Time to Interactive: 27.8 s

    27.8 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Total Blocking Time: 906 ms

    906 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    +8%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 197 ms

    197 ms

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

  • Real-user TTFB: 615 ms

    615 ms

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

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

    -15%

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

Images and page weight

3 to fix62
  • Page weight: 17.8 MB in 361 requests

    17.8 MB

    Your homepage downloads 17.8 MB in 361 requests on a phone: media 12.1 MB (4), images 2.7 MB (134) and scripts 2.4 MB (98). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    a2348e95-eeee-4b72-bbf3-a66a10d6e511-original.webp 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).

  • 5 images below the first screen load straight away

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

  • About 5.1 g of CO₂ per visit

    5.06 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9696
  • 17 text elements with low contrast

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

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

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

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

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

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

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

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

Google 100100
  • 32 internal links, 10 external

    The homepage links to 32 pages on almajed4oud.com and 10 external pages.

8 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Discover Almajed 4 Oud s collection of premium oud, perfumes, fragrances, incense, and Arabian scents. Shop authentic l…”.

  • One H1 headline

    Your main headline reads: “Al Majed for Oud: Finest Oud & Perfume Products”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Almajed 4 Oud | Luxury Oud Perfumes and Fragrances”.

  • Canonical URL set

    The canonical URL is https://global.almajed4oud.com/en.

  • Structured data in place

    Structured data found: Organization and WebPage.

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

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (274 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://global.almajed4oud.com/llms.txt (8 KiB, 37 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 14 pages share a meta description

    https://global.almajed4oud.com/en/-/c199032994, https://global.almajed4oud.com/en/-/c1550744276, https://global.almajed4oud.com/en/-/c1676347343, https://global.almajed4oud.com/en/-/c869286084, https://global.almajed4oud.com/en/-/c1809094171 and https://global.almajed4oud.com/en/-/c1753498508 and 8 others use the same meta description. A description written for each page earns more clicks.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://global.almajed4oud.com/en/-/c199032994, whose canonical is https://global.almajed4oud.com/en/autumn-fragrances/c199032994. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages with very little text

    https://global.almajed4oud.com/en/-/c199032994, https://global.almajed4oud.com/en/-/c1550744276, https://global.almajed4oud.com/en/-/c1676347343, https://global.almajed4oud.com/en/-/c869286084, https://global.almajed4oud.com/en/-/c1809094171 and https://global.almajed4oud.com/en/-/c1753498508 and 8 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.

  • 15 internal pages checked

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

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7397
  • 1 third-party cookie

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    21 of 25 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 249 words

    The homepage has only about 249 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
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager 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
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

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

  • 35 other companies contacted

    Loading the homepage contacts 35 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 almajed4oud.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 Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on almajed4oud.com, including 21 speed 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