Website review, no card needed
eunorau-ebike.com website review
Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 92 checks
This review found 38 issues worth fixing on eunorau-ebike.com, 15 of them high impact, across 92 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
80B- #45,494 of 114,894 reviewed websitesbeats 55%
- #30,678 of 66,334 online storesbeats 47%
- #29,555 of 60,680 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 113 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 114 ms |
| Nov 7, 2026 | 120 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.0 s
2.0 s
2.9 s
3.9 s
4.9 s
5.9 s
6.8 s
7.8 s
Speed
Improve image delivery
1.4 s · 530 KiB6 images could be 530 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.6 s
A phone's processor spends 9.6 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,640 HTML elements
The page has 5,640 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, xcottons.com and Clarity and others), adding 1.2 MB and 870 ms of main-thread time.
Render-blocking requests
950 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Shopify adds 411 ms
411 msShopify costs a phone 411 ms of main-thread work and 849 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 393 ms. During a long task the page ignores taps.
xcottons.com adds 209 ms
209 msxcottons.com costs a phone 209 ms of main-thread work and 343 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.
Reduce unused JavaScript
201 KiBAbout 201 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
150 ms · 39 KiBAbout 39 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.
Use efficient cache lifetimes
34 KiB10 files are served with short cache lifetimes, so returning visitors download them again (34 KiB).
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.2 s
14.2 sThe page becomes fully interactive after 14.2 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 131 ms
131 msReal visitors wait 131 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 668 ms
668 msReal visitors wait 668 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.017
0.017The layout barely moves while loading (CLS 0.017, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 315 requests
4.2 MBYour homepage downloads 4.2 MB in 315 requests on a phone: images 1.7 MB (47), other files 1.1 MB (146) and scripts 1.0 MB (89). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
bfcm_banner.png 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).
1 image far larger than shown
11 KiB1 image is downloaded at several times the size a phone draws it, for example popup.jpg at 1,080 px wide, shown at 342 px. Resized copies would save about 11 KiB.
About 1.2 g of CO₂ per visit
1.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 144.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
15 buttons without a name
15 buttons have no accessible name, so screen readers announce just “button”.
40 text elements with low contrast
40 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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
66 form fields without a label
66 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “All Ability-All Hyper-All AI || The World's Safest Ebike || EUNORAU US”.
Meta description is long (266 characters)
Your meta description is 266 characters; Google truncates after about 160, so the end of your pitch is cut.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
138 internal links, 9 external
The homepage links to 138 pages on eunorau-ebike.com and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://eunorau-ebike.com/.
Structured data in place
Structured data found: 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://eunorau-ebike.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://eunorau-ebike.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,797 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://eunorau-ebike.com/collections/all-eunorau-models, https://eunorau-ebike.com/pages/after-sales-service-support, https://eunorau-ebike.com/pages/store-locator, https://eunorau-ebike.com/pages/compare and https://eunorau-ebike.com/pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://eunorau-ebike.com/pages/become-a-dealer, whose canonical is https://eunorau-ebike.com/pages/become-eunorau-usa-dealer. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://eunorau-ebike.com/pages/after-sales-service-support, https://eunorau-ebike.com/pages/become-a-dealer and https://eunorau-ebike.com/products/meta-20-1 have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://eunorau-ebike.com/products/meta275-2 and https://eunorau-ebike.com/products/2x-fat-hs took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
4 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
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 11 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.
2 checks passed
Tap targets are thumb-sized
49 of 52 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.
Thin social proof
Social proof on the homepage: 43 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 1,047 words of copy
The homepage carries about 1,047 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP BOGO DEAL”.
10 calls to action
The homepage has 10 calls to action, for example “Register”, “SHOP BOGO DEAL” and “SHOP NOW”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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, Meta Pixel and Microsoft Ads 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.
34 other companies contacted
Loading the homepage contacts 34 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 eunorau-ebike.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Hulk Form Builder · Foxify Page Builder · Judge Me Reviews · Foxkit Upsell Bundles · Crisp Live Chat Chatbot · Globo Mega Menu · Triplewhale · Xcotton Guard · Microsoft Clarity · Easylocation · Tek Labs Gifts Upsell · Crisp Chatbox · Selleasy · Apphero Free Gift · goaffpro.com · closeby.co
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on eunorau-ebike.com, including 14 speed issues, 4 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.