Website review, no card needed

rexbikes.eu logo

rexbikes.eu website review

Visit site (opens in a new tab)Reviewed 13 November 202632 issues · 75 checks

This review found 32 issues worth fixing on rexbikes.eu, 13 of them high impact, across 75 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of rexbikes.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rexbikes.eu at 0.4 s0.4 s
  2. rexbikes.eu at 0.8 s0.8 s
  3. rexbikes.eu at 1.1 s1.1 s
  4. rexbikes.eu at 1.5 s1.5 s
  5. rexbikes.eu at 1.9 s1.9 s
  6. rexbikes.eu at 2.3 s2.3 s
  7. rexbikes.eu at 2.6 s2.6 s
  8. rexbikes.eu at 3.0 s3.0 s

Speed

4 to fix72
  • Improve image delivery

    2.3 s · 717 KiB

    13 images could be 717 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    900 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Shopify adds 75 ms

    75 ms

    Shopify costs a phone 75 ms of main-thread work and 374 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 CSS

    150 ms · 29 KiB

    About 29 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 381 KiB and 75 ms of main-thread time.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    20 KiB

    About 20 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    6 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).

  • 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.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 525 ms of it running JavaScript. That is comfortably low.

  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix64
  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 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.3 s

    8.3 s

    The page becomes fully interactive after 8.3 s. Good is under 3.8 s.

  • Cumulative Layout Shift: 0.124

    0.124

    The layout shifts by 0.124 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 36 ms

    36 ms

    Scripts block the page for only 36 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix76
  • Page weight: 2.6 MB in 224 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 224 requests on a phone: images 1.2 MB (16), other files 774 KiB (92) and scripts 395 KiB (106). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    DIMG_5266.jpg 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).

  • 6 images below the first screen load straight away

    6 images further down the page (327 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (112 KiB) is 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.7 g of CO₂ per visit

    0.73 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 7487
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 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: 48 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8570
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (11 characters)

    Your title is only 11 characters: “Rex E-Bikes”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 30 internal links, 0 external

    The homepage links to 30 pages on rexbikes.eu and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://rexbikes.eu/.

  • Structured data in place

    Structured data found: Organization.

  • 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://rexbikes.eu/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (334 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://rexbikes.eu/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://rexbikes.eu/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://rexbikes.eu/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://rexbikes.eu/collections/rex, https://rexbikes.eu/pages/contact, https://rexbikes.eu/customer_authentication/redirect and https://rexbikes.eu/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://rexbikes.eu/collections/rex, https://rexbikes.eu/pages/contact, https://rexbikes.eu/customer_authentication/redirect, https://rexbikes.eu/collections/all, https://rexbikes.eu/products/commuter-plus and https://rexbikes.eu/products/carbon and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://rexbikes.eu/pages/contact 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.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 8 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.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    21 of 24 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 240 words

    The homepage has only about 240 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop now”.

  • 8 short forms

    8 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 rexbikes.eu, 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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews

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
jQuery
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on rexbikes.eu, including 8 speed issues, 4 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25