Website review, no card needed

aljedaie.com logo

aljedaie.com website review

Visit site (opens in a new tab)Reviewed 23 October 202627 issues · 79 checks

This review found 27 issues worth fixing on aljedaie.com, 6 of them high impact, across 79 checks. The most urgent: 1 linked page is broken. 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
1.8 s1.3 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
107 ms94 msMay 2Oct 17103 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202695 ms
May 9, 202697 ms
May 16, 202697 ms
May 23, 202698 ms
May 30, 2026101 ms
Jun 6, 2026102 ms
Jun 13, 2026101 ms
Jun 20, 2026101 ms
Jun 27, 2026100 ms
Jul 4, 2026100 ms
Jul 11, 2026100 ms
Jul 18, 2026101 ms
Jul 25, 2026105 ms
Aug 1, 2026103 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026100 ms
Aug 29, 2026100 ms
Sep 5, 202699 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 202699 ms
Oct 17, 2026103 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 aljedaie.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aljedaie.com at 0.7 s0.7 s
  2. aljedaie.com at 1.4 s1.4 s
  3. aljedaie.com at 2.0 s2.0 s
  4. aljedaie.com at 2.7 s2.7 s
  5. aljedaie.com at 3.4 s3.4 s
  6. aljedaie.com at 4.1 s4.1 s
  7. aljedaie.com at 4.7 s4.7 s
  8. aljedaie.com at 5.4 s5.4 s

Speed

5 to fix68
  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68 (desktop: 72). 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 (salla.network, Google Tag Manager and Snapchat and others), adding 1.6 MB and 773 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 68 KiB

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

  • salla.network adds 245 ms

    245 ms

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

  • Main-thread work: 2.8 s

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

  • Reduce unused JavaScript

    221 KiB

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

  • Render-blocking requests

    150 ms

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

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    37 KiB

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

  • Improve image delivery

    17 KiB

    1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    9 KiB

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

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

6 to fix100
  • Time to Interactive: 12.4 s

    12.4 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “الجديعي للأقمشة الرجالية”.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Total Blocking Time: 201 ms

    201 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 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: 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: 112 ms

    112 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 630 ms

    630 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.53 g

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

4 checks passed
  • Page weight: 1.9 MB in 138 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 138 requests on a phone: scripts 1,013 KiB (70), images 449 KiB (20) and fonts 298 KiB (3). That is a lean page.

  • 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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails 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. (4 elements).

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 38 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: 38 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10089
  • 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 XML sitemap

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

  • 39 internal links, 0 external

    The homepage links to 39 pages on aljedaie.com and 0 external pages.

6 checks passed
  • Meta description: 70 characters

    Your meta description is 70 characters: “روّاد الفخامة في عالم الأقمشة الرجالية عالية الجودة على مستوى المملكة.”.

  • One H1 headline

    Your main headline reads: “الجديعي للأقمشة الرجالية”.

  • Canonical URL set

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

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

AI search readiness

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

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

  • llms.txt published

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

Other pages

3 to fix69
  • 1 linked page is broken

    Your homepage links to https://aljedaie.com/-/c25113843, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://aljedaie.com/%D9%85%D8%B9%D9%84%D9%88%D9%85%D8%A7%D8%AA-%D8%B9%D9%86%D8%A7/page-1155052398, https://aljedaie.com/%D8%A7%D9%84%D8%AA%D9%88%D8%B5%D9%8A%D9%84-%D9%88%D8%A7%D9%84%D8%B4%D8%AD%D9%86/page-738098548, https://aljedaie.com/%D8%B3%D9%8A%D8%A7%D8%B3%D8%A9-%D8%A7%D9%84%D8%A5%D8%B1%D8%AC%D8%A7%D8%B9/page-96771189, https://aljedaie.com/%D8%A7%D9%84%D8%B4%D8%B1%D9%88%D8%B7-%D9%88%D8%A7%D9%84%D8%A3%D8%AD%D9%83%D8%A7%D9%85/page-563010167, https://aljedaie.com/%D8%B3%D9%8A%D8%A7%D8%B3%D8%A9-%D8%A7%D9%84%D8%AE%D8%B5%D9%88%D8%B5%D9%8A%D8%A9/page-1761232499 and https://aljedaie.com/%D8%A7%D9%84%D8%A3%D8%B3%D8%A6%D9%84%D8%A9-%D8%A7%D9%84%D8%B4%D8%A7%D8%A6%D8%B9%D8%A9/page-1720361854 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B5%D9%8A%D9%81%D9%8A%D8%A9/c25113843, https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%A8%D9%86%D8%AA%D9%84%D9%8A/c479771326, https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B1%D8%B3%D9%85%D9%8A%D8%A9/c1852168639, https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B9%D9%85%D9%84%D9%8A%D8%A9/c1744053946, https://aljedaie.com/%D8%A3%D9%82%D8%B7%D8%A7%D9%86-%D8%B7%D8%A8%D9%8A%D8%B9%D9%8A%D8%A9/c2035204487 and https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B4%D8%AA%D9%88%D9%8A%D8%A9/c757166845 and 2 others use the same meta description. A description written for each page earns more clicks.

  • 14 pages with very little text

    https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B5%D9%8A%D9%81%D9%8A%D8%A9/c25113843, https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%A8%D9%86%D8%AA%D9%84%D9%8A/c479771326, https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B1%D8%B3%D9%85%D9%8A%D8%A9/c1852168639, https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B9%D9%85%D9%84%D9%8A%D8%A9/c1744053946, https://aljedaie.com/%D8%A3%D9%82%D8%B7%D8%A7%D9%86-%D8%B7%D8%A8%D9%8A%D8%B9%D9%8A%D8%A9/c2035204487 and https://aljedaie.com/%D8%A3%D9%82%D9%85%D8%B4%D8%A9-%D8%B4%D8%AA%D9%88%D9%8A%D8%A9/c757166845 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 16 found) and read each the way a search engine does.

5 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 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    33 of 37 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Only about 24 words

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

  • No form on the homepage

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 16 cookies set on arrival

    16

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 aljedaie.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 27 issues on aljedaie.com, including 11 speed issues, 2 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