Website review, no card needed
harobikes.de website review
Visit site (opens in a new tab)Reviewed 16 November 202620 issues · 74 checks
This review found 20 issues worth fixing on harobikes.de, 5 of them high impact, across 74 checks. The most urgent: 14 text elements with low contrast. 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
89B- #3,685 of 117,615 reviewed websitesbeats 95%
- #1,903 of 66,923 online storesbeats 95%
- #1,847 of 61,018 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 973 ms |
| Jun 6, 2026 | 957 ms |
| Jun 13, 2026 | 950 ms |
| Jun 20, 2026 | 989 ms |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 988 ms |
| Oct 10, 2026 | 959 ms |
| Oct 17, 2026 | 947 ms |
| Oct 24, 2026 | 947 ms |
| Oct 31, 2026 | 985 ms |
| Nov 7, 2026 | 1.0 s |
| Nov 14, 2026 | 970 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 92 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 94 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 98 ms |
| Sep 19, 2026 | 99 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 97 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 90 ms |
| Oct 31, 2026 | 92 ms |
| Nov 7, 2026 | 92 ms |
| Nov 14, 2026 | 91 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
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
470 ms · 81 KiBAbout 81 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.
1,597 HTML elements
The page has 1,597 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 215 KiB5 images could be 215 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Klaviyo, Shopify and JSDelivr CDN and others), adding 444 KiB and 263 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 23 KiB6 files are served with short cache lifetimes, so returning visitors download them again (23 KiB).
Render-blocking requests
150 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 451 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 8.7 s
8.7 sThe page becomes fully interactive after 8.7 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
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
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 94 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 91 ms
91 msReal visitors wait 91 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 424 ms
424 msReal visitors wait 424 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
1 image below the first screen load straight away
1 image further down the page (40 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 65.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.9 MB in 179 requests
1.9 MBYour homepage downloads 1.9 MB in 179 requests on a phone: other files 634 KiB (65), images 603 KiB (10) and scripts 545 KiB (69). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“”, “Black weeks” and “The Buzzard”). One clear main headline is easier for people and search engines.
Meta description is long (280 characters)
Your meta description is 280 characters; Google truncates after about 160, so the end of your pitch is cut.
152 internal links, 7 external
The homepage links to 152 pages on harobikes.de and 7 external pages.
6 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “HARO ALL BIKES – Haro Bikes Europe GmbH”.
Canonical URL set
The canonical URL is https://harobikes.de/en-us.
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://harobikes.de/sitemap.xml.
AI search readiness
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: 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 (775 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://harobikes.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share 2 titles
https://harobikes.de/en-us, https://harobikes.de/products/buzzard-alloy-2 and https://harobikes.de/products/buzzard-alloy-4 all use the title “HARO ALL BIKES – Haro Bikes Europe GmbH”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://harobikes.de/en-us/collections/black-week-emtb-2026, https://harobikes.de/en-us/collections/black-month-p-a-2026, https://harobikes.de/pages/partimos, https://harobikes.de/en-us/pages/e-mtb and https://harobikes.de/en-us/pages/full-suspension have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://harobikes.de/products/buzzard-alloy-2 and https://harobikes.de/products/buzzard-alloy-4 use the same meta description. A description written for each page earns more clicks.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://harobikes.de/pages/partimos, whose canonical is https://harobikes.de/en-us/pages/partimos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://harobikes.de/en-us/collections/black-week-emtb-2026, https://harobikes.de/en-us/collections/black-month-p-a-2026, https://harobikes.de/pages/partimos, https://harobikes.de/products/partimos-alloy, https://harobikes.de/collections/road-framesets and https://harobikes.de/collections/gravel-framesets and 6 others 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 89 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
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 269 words of copy
The homepage carries about 269 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “GET YOUR DEAL”.
8 calls to action
The homepage has 8 calls to action, for example “Shop by collection”, “get your deal” and “Shop the Buzzard”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Fathom.
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 Klaviyo (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.
21 other companies contacted
Loading the homepage contacts 21 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 harobikes.de, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Upsell Koala Discount · Pre Order
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
- E-commerce
- Shopify
- Analytics
- Fathom
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on harobikes.de, including 8 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.