Website review, no card needed
ehabcenter.com website review
Visit site (opens in a new tab)Reviewed 21 October 202646 issues · 87 checks
This review found 46 issues worth fixing on ehabcenter.com, 21 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
63D- #114,926 of 120,970 reviewed websitesbeats 4%
- #66,953 of 68,463 online storesbeats 2%
- #2,646 of 2,803 WooCommerce storesbeats 4%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 220 ms |
| May 9, 2026 | 223 ms |
| May 16, 2026 | 228 ms |
| May 23, 2026 | 231 ms |
| May 30, 2026 | 236 ms |
| Jun 6, 2026 | 238 ms |
| Jun 13, 2026 | 241 ms |
| Jun 20, 2026 | 243 ms |
| Jun 27, 2026 | 246 ms |
| Jul 4, 2026 | 247 ms |
| Jul 11, 2026 | 239 ms |
| Jul 18, 2026 | 238 ms |
| Jul 25, 2026 | 238 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 250 ms |
| Aug 15, 2026 | 269 ms |
| Aug 22, 2026 | 285 ms |
| Aug 29, 2026 | 314 ms |
| Sep 5, 2026 | 318 ms |
| Sep 12, 2026 | 306 ms |
| Sep 19, 2026 | 312 ms |
| Sep 26, 2026 | 318 ms |
| Oct 3, 2026 | 321 ms |
| Oct 10, 2026 | 306 ms |
| Oct 17, 2026 | 279 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
Speed
Improve image delivery
1.6 s · 242 KiB6 images could be 242 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
1.2 s · 642 KiBAbout 642 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 165 KiB12 files are served with short cache lifetimes, so returning visitors download them again (165 KiB).
10,903 HTML elements
The page has 10,903 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 15
15/100Your mobile performance score is 15 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 2.3 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, tactful.ai and Facebook and others), adding 1.2 MB and 833 ms of main-thread time.
Reduce initial server response time
703 msReduce initial server response time. Google estimates savings of 703 ms on a phone.
Document request latency
700 msThe HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Google Tag Manager adds 485 ms
485 msGoogle Tag Manager costs a phone 485 ms of main-thread work and 348 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 373 ms. During a long task the page ignores taps.
tactful.ai adds 270 ms
270 mstactful.ai costs a phone 270 ms of main-thread work and 581 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.
Server response: 803 ms
803 msYour server takes 803 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Reduce unused CSS
150 ms · 87 KiBAbout 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 59 but mobile only 15. 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.
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: 9.2 s
9.2 sReal visitors wait 9.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 8.7 s
8.7 sReal visitors see the first content after 8.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 8.3 s
8.3 sReal visitors wait 8.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.0 s
13.0 sYour largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 1.002
1.002The layout shifts by 1.002 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 889 ms
889 msScripts block taps and scrolling for 889 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 470 ms
470 msReal visitors wait 470 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 220 ms to 279 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 2.8 MB in 134 requests
2.8 MBYour homepage downloads 2.8 MB in 134 requests on a phone: scripts 1.6 MB (88), fonts 572 KiB (13) and images 407 KiB (13). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
7 KiB2 images are downloaded at several times the size a phone draws them, for example 37-2.png at 300 px wide, shown at 97 px. Resized copies would save about 7 KiB.
4 images in older formats
4 images (211 KiB) 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 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 94.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
67 tap targets too small
67 tap targets are too small or too close together to hit reliably with a finger.
44 text elements with low contrast
44 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.
89 links without text
89 visible links have no text or label, so screen readers cannot say where they go.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (14 elements).
2 checks passed
Every image has alt text
All 249 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (Article, ElectronicsStore, ImageObject and Organization) but with 1 problem, for example “Person: missing name”.
600 internal links, 21 external
The homepage links to 600 pages on ehabcenter.com and 21 external pages.
6 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Buy From EHAB Center all Home Appliances and Mobile any Enjoy Cash offers and Discounts and free Delivery”.
Title: 34 characters
Your title is a healthy 34 characters: “Home | EHAB Center Home Appliances”.
Canonical URL set
The canonical URL is https://ehabcenter.com/.
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://ehabcenter.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://ehabcenter.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.
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: 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 (4,754 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://ehabcenter.com/iPhone-18 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://ehabcenter.com/product-category/small-appliances/water-filter and https://ehabcenter.com/iPhone-18 have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://ehabcenter.com/ar has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://ehabcenter.com/ar, https://ehabcenter.com/installment-offers, https://ehabcenter.com/product-category/small-appliances, https://ehabcenter.com/product-category/small-appliances/water-filter, https://ehabcenter.com/product-category/kitchenware and https://ehabcenter.com/product-category/refrigerators-freezers and 2 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.
6 pages slow to respond
https://ehabcenter.com/our-branches, https://ehabcenter.com/about-us, https://ehabcenter.com/product-category/small-appliances/water-filter, https://ehabcenter.com/iPhone-18, https://ehabcenter.com/product-category/refrigerators-freezers and https://ehabcenter.com/product-category/sound-system took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
4 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 a title
All 15 pages that loaded have a <title>.
Best practices
127 small tap targets
127 of 410 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'innerHTML')”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 7,370 words of copy
The homepage carries about 7,370 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Join Our Team”, “Contact Us” and “Order Tracking”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
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 Meta 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
11 other companies contacted
Loading the homepage contacts 11 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 ehabcenter.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on ehabcenter.com, including 26 speed issues, 2 SEO issues 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.