Website review, no card needed
eros.ae website review
Visit site (opens in a new tab)Reviewed 30 October 202650 issues · 96 checks
This review found 50 issues worth fixing on eros.ae, 25 of them high impact, across 96 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
58F- #119,233 of 121,390 reviewed websitesbeats 1%
- #68,319 of 68,681 online storesbeats 0%
- #676 of 718 Magento storesbeats 4%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 5.0 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 4.9 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 195 ms |
| May 16, 2026 | 194 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 190 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 199 ms |
| Jul 4, 2026 | 203 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 201 ms |
| Jul 25, 2026 | 202 ms |
| Aug 1, 2026 | 199 ms |
| Aug 8, 2026 | 202 ms |
| Aug 15, 2026 | 210 ms |
| Aug 22, 2026 | 213 ms |
| Aug 29, 2026 | 222 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 227 ms |
| Sep 19, 2026 | 228 ms |
| Sep 26, 2026 | 229 ms |
| Oct 3, 2026 | 225 ms |
| Oct 10, 2026 | 227 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 221 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
3.6 s · 1.0 MB38 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
4.5 s51 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Use efficient cache lifetimes
2.3 s · 805 KiB364 files are served with short cache lifetimes, so returning visitors download them again (805 KiB).
Reduce unused CSS
1.1 s · 183 KiBAbout 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 21
21/100Your mobile performance score is 21. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,719 HTML elements
The page has 6,719 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
900 ms · 1,015 KiBAbout 1,015 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and TikTok and others), adding 1.9 MB and 993 ms of main-thread time.
Minify JavaScript
750 ms · 225 KiB225 KiB could be saved by minifying JavaScript.
Google CDN adds 368 ms
368 msGoogle CDN costs a phone 368 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.
Google Tag Manager adds 361 ms
361 msGoogle Tag Manager costs a phone 361 ms of main-thread work and 531 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 380 ms
380 msYour server sent the HTML in 380 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: 6.6 s
6.6 sReal visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 1.3 s
1.3 sReal visitors wait 1.3 s for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.41
0.41For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.7 s
4.7 sReal visitors wait 4.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 14.2 s
14.2 sYour largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.1 s
28.1 sThe page becomes fully interactive after 28.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.052
1.052The layout shifts by 1.052 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 472 ms
472 msScripts block taps and scrolling for 472 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 221 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.9 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.5 MB in 447 requests
5.5 MBYour homepage downloads 5.5 MB in 447 requests on a phone: scripts 2.8 MB (249), images 1.5 MB (95) and other files 378 KiB (43). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
redmi_note_17_m.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).
3 images far larger than shown
50 KiB3 images are downloaded at several times the size a phone draws them, for example SamsungAITV_m.webp at 1,200 px wide, shown at 390 px. Resized copies would save about 50 KiB.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
86 images without alt text
86 images have no alt text, which hurts accessibility and image search.
11 buttons without a name
11 buttons have no accessible name, so screen readers announce just “button”.
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.
47 links without text
47 visible links have no text or label, so screen readers cannot say where they go.
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
55 links crawlers can't follow
55 links have no real href, so search engines can't follow them.
Title is long (99 characters)
Your title is 99 characters, so Google will cut it off around 60: “Online Shopping Store for Electronics, Appliances, Computers & More in Dubai, Abu Dhabi, …”.
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.eros.ae/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at eros.ae/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
500 internal links, 7 external
The homepage links to 500 pages on eros.ae and 7 external pages.
4 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Shop premium electronics, home appliances and accessories online from top global brands at Eros, with trusted service, …”.
One H1 headline
Your main headline reads: “Buy Premium Electronics & Home Appliances Online In UAE”.
Canonical URL set
The canonical URL is https://www.eros.ae/.
Structured data in place
Structured data found: ElectronicsStore, Organization and WebSite.
AI search readiness
No llms.txt
There is no https://www.eros.ae/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
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,653 words), so crawlers that don't run JavaScript still read it.
Other pages
12 linked pages are broken
Your homepage links to https://www.eros.ae/catalogsearch/advanced, https://www.eros.ae/amlocator, https://www.eros.ae/smart-phones/harmonyos.html, https://www.eros.ae/computers-tablets/tablets.html, https://www.eros.ae/computers-tablets/tablets/ipad.html and https://www.eros.ae/computers-tablets/tablets/android.html and 6 others, which answer with an error. Visitors hit a dead end and search engines drop them.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 191 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 3 pages that loaded have a meta description.
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 3 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17557157&tm=gtm002&Ver=2&mid=73529fdc-be16-4ae0-bd75-0f12936f6ab9&bo=1&sid=38447c20d45a11f1a5b87bbeb71908ab&vid=38449c60d45a11f1afb985297fdd98ce&vids=1&msclkid=N&pi=91.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 491 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
105 of 114 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,184 words of copy
The homepage carries about 1,184 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Register”.
13 calls to action
The homepage has 13 calls to action, for example “Register”, “Shop by Brands” and “JOIN”.
74 short forms
74 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 70 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Snap Pixel and 1 more (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
24 other companies contacted
Loading the homepage contacts 24 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 eros.ae, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Magento
- Analytics
- Google Tag Manager
- Hosting
- Link11 GmbH
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on eros.ae, including 25 speed issues, 5 SEO issues and 1 conversion gap. 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.