Website review, no card needed
habtoormotors.com website review
Visit site (opens in a new tab)Reviewed 27 October 202645 issues · 83 checks
This review found 45 issues worth fixing on habtoormotors.com, 22 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 137 ms |
| May 16, 2026 | 137 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 168 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 174 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 192 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
How it loaded on a phone
1.1 s
2.1 s
3.2 s
4.3 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Use efficient cache lifetimes
6.8 s · 2.1 MB52 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).
Improve image delivery
3.1 s · 879 KiB11 images could be 879 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.
Google Tag Manager adds 1.6 s
1.6 sGoogle Tag Manager costs a phone 1.6 s of main-thread work and 642 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google CDN adds 1.1 s
1.1 sGoogle CDN costs a phone 1.1 s of main-thread work and 741 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 21
21/100Your mobile performance score is 21 (desktop: 71). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.5 s
A phone's processor spends 8.5 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 1.6 MB and 2.9 s of main-thread time.
Reduce unused JavaScript
615 KiBAbout 615 KiB of JavaScript is downloaded but never used on this page.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 599 ms. During a long task the page ignores taps.
Reduce unused CSS
460 ms · 86 KiBAbout 86 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.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Phones get a much slower page than desktops
Desktop scores 71 but mobile only 21. 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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 4.7 s
4.7 sReal visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.34
0.34For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 23.0 s
23.0 sThe page becomes fully interactive after 23.0 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.334
0.334The layout shifts by 0.334 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 137 ms to 192 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
1 checks passed
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 85 requests
4.1 MBYour homepage downloads 4.1 MB in 85 requests on a phone: images 1.8 MB (31), scripts 1.4 MB (22) and fonts 407 KiB (5). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.0 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.
2 images far larger than shown
397 KiB2 images are downloaded at several times the size a phone draws them, for example home-full-3.jpg at 1,964 px wide, shown at 390 px. Resized copies would save about 397 KiB.
5 images below the first screen load straight away
5 images further down the page (504 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
30 images without alt text
30 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“Vacancies”, “Submit Your CV” and “About Al Habtoor Motors”). One clear main headline is easier for people and search engines.
24 internal links, 23 external
The homepage links to 24 pages on habtoormotors.com and 23 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Al Habtoor Motors: The Leading Automobile Distributor in UAE. Sole Distributor of Bentley, Bugatti, Pagani, Rimac, Mits…”.
Title: 61 characters
Your title is a healthy 61 characters: “Your Luxury & Premium vehicle distributor | Al Habtoor Motors”.
Canonical URL set
The canonical URL is https://habtoormotors.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage 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://habtoormotors.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,855 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://habtoormotors.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://habtoormotors.com/jbm-buses declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
7 pages without a meta description
https://habtoormotors.com/certified-pre-owned, https://habtoormotors.com/celebrating-excellence-on-a-global-scale, https://habtoormotors.com/al-habtoor-motors-recognised-3rd-time-as-eliteclass-mena-fuso-general-distributor-of-the-year-2025, https://habtoormotors.com/al-habtoor-motors-redefines-urban-logistics-in-the-uae-with-the-landmark-launch-of-the-all-electric-fuso-new-ecanter, https://habtoormotors.com/al-habtoor-news and https://habtoormotors.com/Terms-of-Use and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://habtoormotors.com/mitsubishi, https://habtoormotors.com/certified-pre-owned and https://habtoormotors.com/TBL have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://habtoormotors.com/TBL has 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.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
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 12 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 1,481 words of copy
The homepage carries about 1,481 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 10 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
13 other companies contacted
Loading the homepage contacts 13 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 habtoormotors.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- IONOS
Company
- Founded
- 1983
- Headquarters
- Dubai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on habtoormotors.com, including 26 speed issues, 1 SEO issue and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.