Website review, no card needed

al-jammaz.com logo

al-jammaz.com website review

Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 73 checks

This review found 34 issues worth fixing on al-jammaz.com, 10 of them high impact, across 73 checks. The most urgent: page weight: 9.2 MB in 54 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
5.3 s2.3 sMay 2Oct 174.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.7 s
May 9, 20264.5 s
May 16, 20264.4 s
May 23, 20264.4 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20263.5 s
Jun 20, 20262.9 s
Jun 27, 20262.7 s
Jul 4, 20263.2 s
Jul 11, 20264.7 s
Jul 18, 20264.9 s
Jul 25, 20264.9 s
Aug 1, 20265.0 s
Aug 8, 20264.8 s
Aug 15, 20264.6 s
Aug 22, 20264.3 s
Aug 29, 20264.2 s
Sep 5, 20263.9 s
Sep 12, 20263.5 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20263.5 s
Oct 10, 20263.9 s
Oct 17, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
497 ms253 msMay 2Oct 17281 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026409 ms
May 9, 2026403 ms
May 16, 2026405 ms
May 23, 2026413 ms
May 30, 2026447 ms
Jun 6, 2026469 ms
Jun 20, 2026378 ms
Jun 27, 2026351 ms
Jul 4, 2026350 ms
Jul 11, 2026429 ms
Jul 18, 2026436 ms
Jul 25, 2026440 ms
Aug 1, 2026449 ms
Aug 8, 2026439 ms
Aug 15, 2026443 ms
Aug 22, 2026428 ms
Aug 29, 2026428 ms
Sep 5, 2026422 ms
Sep 12, 2026408 ms
Sep 19, 2026384 ms
Sep 26, 2026372 ms
Oct 3, 2026415 ms
Oct 10, 2026347 ms
Oct 17, 2026281 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 al-jammaz.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. al-jammaz.com at 0.4 s0.4 s
  2. al-jammaz.com at 0.8 s0.8 s
  3. al-jammaz.com at 1.2 s1.2 s
  4. al-jammaz.com at 1.6 s1.6 s
  5. al-jammaz.com at 2.0 s2.0 s
  6. al-jammaz.com at 2.4 s2.4 s
  7. al-jammaz.com at 2.8 s2.8 s
  8. al-jammaz.com at 3.2 s3.2 s

Speed

5 to fix69
  • Improve image delivery

    150 ms · 7.6 MB

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

  • Use efficient cache lifetimes

    3.3 MB

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

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 104 KiB

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Reduce unused CSS

    13 KiB

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

  • Phones get a much slower page than desktops

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

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

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix50
  • 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 FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 25.1 s

    25.1 s

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

  • Time to Interactive: 27.2 s

    27.2 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • 3 images without width and height

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

5 checks passed
  • Real-user CLS: 0.02

    0.02

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

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

    -23%

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

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

    -13%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix14
  • Page weight: 9.2 MB in 54 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 54 requests on a phone: images 8.3 MB (26), other files 564 KiB (17) and scripts 289 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 7.9 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    4.2 MB

    4 images are downloaded at several times the size a phone draws them, for example solution-datacenter-v2.png at 1,536 px wide, shown at 348 px. Resized copies would save about 4.2 MB.

  • 4 images in older formats

    4 images (7.9 MB) 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.

  • An image on the first screen is lazy-loaded

    hero-it-compute-v1-mobile.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).

  • About 2.6 g of CO₂ per visit

    2.62 g

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

Accessibility

3 to fixGoogle 9696
  • 21 text elements with low contrast

    21 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 20 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9180
  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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://www.al-jammaz.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at al-jammaz.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 164 internal links, 4 external

    The homepage links to 164 pages on al-jammaz.com and 4 external pages.

3 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Technology distribution, enterprise solutions and partner services across Saudi Arabia, the GCC and the Middle East.”.

  • One H1 headline

    Your main headline reads: “The technology ecosystem for the AI era.”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “AlJammaz Technologies | Technology. Partnership. Possibility.”.

AI search readiness

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.al-jammaz.com/solutions has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • 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 10093
  • 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 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    29 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • About 648 words of copy

    The homepage carries about 648 words of visible text.

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Find a reseller / How to buy”, “Join us” and “Contact us”.

  • Direct contact links

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

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 al-jammaz.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
Hosting
Vercel

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 al-jammaz.com, including 14 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