Website review, no card needed

alkhateeb.ae logo

alkhateeb.ae website review

Visit site (opens in a new tab)Reviewed 19 October 202625 issues · 103 checks

This review found 25 issues worth fixing on alkhateeb.ae, 7 of them high impact, across 103 checks. The most urgent: fails Core Web Vitals for real visitors. 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.0 s797 msApr 25Oct 10945 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026822 ms
May 2, 2026826 ms
May 9, 2026827 ms
May 16, 2026828 ms
May 23, 2026848 ms
May 30, 2026839 ms
Jun 6, 2026840 ms
Jun 13, 2026830 ms
Jun 20, 2026875 ms
Jun 27, 2026936 ms
Jul 4, 2026961 ms
Jul 11, 2026979 ms
Jul 18, 2026955 ms
Jul 25, 2026937 ms
Aug 1, 2026928 ms
Aug 8, 2026927 ms
Aug 15, 2026941 ms
Aug 22, 2026963 ms
Aug 29, 2026988 ms
Sep 5, 2026990 ms
Sep 12, 2026990 ms
Sep 19, 2026970 ms
Sep 26, 2026959 ms
Oct 3, 2026953 ms
Oct 10, 2026945 ms
Real-visitor tap response (INP)75th percentile, phones
127 ms98 msApr 25Oct 10121 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026124 ms
May 2, 2026105 ms
May 9, 2026105 ms
May 16, 2026101 ms
May 23, 2026103 ms
May 30, 2026105 ms
Jun 6, 2026108 ms
Jun 13, 2026112 ms
Jun 20, 2026109 ms
Jun 27, 2026112 ms
Jul 4, 2026112 ms
Jul 11, 2026107 ms
Jul 18, 2026109 ms
Jul 25, 2026106 ms
Aug 1, 2026104 ms
Aug 8, 2026105 ms
Aug 15, 2026109 ms
Aug 22, 2026112 ms
Aug 29, 2026114 ms
Sep 5, 2026114 ms
Sep 12, 2026115 ms
Sep 19, 2026114 ms
Sep 26, 2026119 ms
Oct 3, 2026124 ms
Oct 10, 2026121 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 alkhateeb.ae (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

alkhateeb.ae does not allow embedding, so this is Google's rendering of the page.

Speed

1 to fix97
  • 2,866 HTML elements

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

  • Reduce unused CSS

    187 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    40 KiB

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

  • Improve image delivery

    14 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Fonts, Shopify and expertvillagemedia.com), adding 138 KiB and 0 ms of main-thread time.

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

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97 (desktop: 100). That is in Google's “good” band (90 and up).

  • Main-thread work: 1.4 s

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

  • Server response: 13 ms

    13 ms

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

Core Web Vitals

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

    0.60

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

  • Real-user INP: 210 ms

    210 ms

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

  • 21 images without width and height

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

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

    +15%

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

8 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 743 ms

    743 ms

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 2.5 s

    2.5 s

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

  • Time to Interactive: 2.1 s

    2.1 s

    The page is fully interactive after 2.1 s.

  • 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

2 to fix60
  • Page weight: 5.3 MB in 104 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 104 requests on a phone: scripts 3.3 MB (26), images 1.6 MB (62) and stylesheets 216 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 20 images in older formats

    20 images (1.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.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

9 to fixGoogle 7587
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 2 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 13 images without alt text

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

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

    All page content should be contained by landmarks: 10 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.

  • 21 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

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

1 to fixGoogle 9298
  • 18 links crawlers can't follow

    18 links have no real href, so search engines can't follow them.

  • 351 internal links, 25 external

    The homepage links to 351 pages on alkhateeb.ae and 25 external pages.

8 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Get the best car accessories and body kits from Al Khateeb, a leading UAE supplier. Fast shipping across UAE, Middle Ea…”.

  • One H1 headline

    Your main headline reads: “Leading Manufacturer & Distributor of Car Accessories & Parts”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Car Accessories & Body Kits Supplier UAE | Al Khateeb”.

  • Canonical URL set

    The canonical URL is https://alkhateeb.ae/.

  • Structured data in place

    Structured data found: AutoPartsStore, BreadcrumbList, Organization and WebSite.

  • 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://alkhateeb.ae/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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    /collections/car-door-handle and /collections/car-logo-emblem have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    /collections/automotive-accessories and /collections/car-logo-emblem have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 9286
  • Scrolls sideways on phones

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Unexpected end of attribute. Expected length, "".”.

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (alkhateeb.ae).

  • Valid certificate (79 days left)

    The certificate from Let's Encrypt · YE2 verifies for alkhateeb.ae and is valid for another 79 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://alkhateeb.ae redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 50 links work

    All 50 links checked from your homepage (40 internal, 10 external) answered without errors.

Domain and trust

  • No CAA record

    alkhateeb.ae has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 58 testimonial or review blocks. 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 471 words of copy

    The homepage carries about 471 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call” and “Contact”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Call”, “Contact” and “Subscribe”.

  • 18 short forms

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

  • Direct contact links

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

  • Phone number on the homepage

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

Email authentication

95
  • Email authentication score: 95/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 +mx +a +ip4:108.167.161.12 +ip4:108.167.189.12 +include:spf.smtp2go.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “default”), so receivers can verify mail really came from you.

Privacy and tracking

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

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
jQuery
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This free review found 25 issues on alkhateeb.ae, including 6 speed issues, 1 SEO issue 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