Website review, no card needed

glercbikes.de logo

glercbikes.de website review

Visit site (opens in a new tab)Reviewed 8 November 202648 issues · 96 checks

This review found 48 issues worth fixing on glercbikes.de, 13 of them high impact, across 96 checks. The most urgent: page weight: 85.3 MB in 519 requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.7 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
426 ms251 msMay 16Oct 31271 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026319 ms
May 23, 2026335 ms
May 30, 2026359 ms
Jun 6, 2026384 ms
Jun 13, 2026393 ms
Jun 20, 2026395 ms
Jun 27, 2026403 ms
Jul 4, 2026394 ms
Jul 11, 2026406 ms
Jul 18, 2026373 ms
Jul 25, 2026331 ms
Aug 1, 2026303 ms
Aug 8, 2026283 ms
Aug 15, 2026282 ms
Aug 22, 2026286 ms
Aug 29, 2026283 ms
Sep 5, 2026285 ms
Sep 12, 2026278 ms
Sep 19, 2026278 ms
Sep 26, 2026278 ms
Oct 3, 2026271 ms
Oct 10, 2026272 ms
Oct 17, 2026275 ms
Oct 24, 2026274 ms
Oct 31, 2026271 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

Full-page screenshot of glercbikes.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. glercbikes.de at 0.6 s0.6 s
  2. glercbikes.de at 1.3 s1.3 s
  3. glercbikes.de at 1.9 s1.9 s
  4. glercbikes.de at 2.6 s2.6 s
  5. glercbikes.de at 3.2 s3.2 s
  6. glercbikes.de at 3.9 s3.9 s
  7. glercbikes.de at 4.5 s4.5 s
  8. glercbikes.de at 5.2 s5.2 s

Speed

13 to fix56
  • Render-blocking requests

    1.9 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

  • Main-thread work: 6.3 s

    A phone's processor spends 6.3 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,009 HTML elements

    The page has 3,009 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    350 ms · 2.5 MB

    27 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and freshworks.com and others), adding 3.2 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 1,023 KiB

    About 1,023 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    750 ms · 254 KiB

    About 254 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • Minify CSS

    600 ms · 114 KiB

    114 KiB could be saved by minifying CSS.

  • Shopify adds 376 ms

    376 ms

    Shopify costs a phone 376 ms of main-thread work and 1.5 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 301 ms

    301 ms

    Google Tag Manager costs a phone 301 ms of main-thread work and 554 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.

  • freshworks.com adds 281 ms

    281 ms

    freshworks.com costs a phone 281 ms of main-thread work and 358 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.

  • Klaviyo adds 170 ms

    170 ms

    Klaviyo costs a phone 170 ms of main-thread work and 517 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.

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    162 KiB

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

  • Legacy JavaScript

    38 KiB

    Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • 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: 89 ms

    89 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Time to Interactive: 37.0 s

    37.0 s

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

  • Speed Index: 12.9 s

    12.9 s

    Visually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 8.0 s

    8.0 s

    Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Real-user INP: 273 ms

    273 ms

    Real visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.15

    0.15

    For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

  • 39 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.133

    0.133

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

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 592 ms

    592 ms

    Real visitors wait 592 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 17% faster for real visitors

    -17%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 319 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 197 ms

    197 ms

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

Images and page weight

3 to fix53
  • Page weight: 85.3 MB in 519 requests

    85.3 MB

    Your homepage downloads 85.3 MB in 519 requests on a phone: media 76.3 MB (10), images 4.0 MB (71) and scripts 2.9 MB (213). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    272 KiB

    2 images are downloaded at several times the size a phone draws them, for example glerc-boys-bike-collection.jpg at 800 px wide, shown at 175 px. Resized copies would save about 272 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (394 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (105 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 24.2 g of CO₂ per visit

    24.17 g

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

Accessibility

9 to fixGoogle 7688
  • 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.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 17 text elements with low contrast

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

  • 5 tap targets too small

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

  • 8 images without alt text

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

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 34 links without text

    34 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8582
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “GlercBikes EU Official | Top Quality Bikes at Great Prices – GLERC BIKES EU”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (182 characters)

    Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 260 internal links, 37 external

    The homepage links to 260 pages on glercbikes.de and 37 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “GLERC BIKES EU”.

  • Canonical URL set

    The canonical URL is https://glercbikes-eu.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://glercbikes-eu.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://glercbikes-eu.com/pages/black-friday-sale, https://glercbikes-eu.com/pages/new-arrivals, https://glercbikes-eu.com/collections/all, https://glercbikes-eu.com/collections/all-bikes, https://glercbikes-eu.com/collections/adult-bikes and https://glercbikes-eu.com/collections/bestsell and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://glercbikes-eu.com/pages/black-friday-sale, https://glercbikes-eu.com/pages/new-arrivals, https://glercbikes-eu.com/collections/all, https://glercbikes-eu.com/collections/all-bikes, https://glercbikes-eu.com/collections/girls-bikes and https://glercbikes-eu.com/collections/boys-bikes and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://glercbikes-eu.com/collections/all and https://glercbikes-eu.com/collections/girls-bikes took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.

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

  • 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

4 to fixGoogle 5083
  • 42 small tap targets

    42 of 95 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://glercbikes-eu.com/cdn/shop/t/45/assets/logo-list.aio.min.css?v=82540' because its …”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,441 words of copy

    The homepage carries about 1,441 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Now”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop Bikes”, “Shop by Rider Height” and “Shop by Age/ Bike Size”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 156 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 2 of them by other companies (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.

  • 46 other companies contacted

    Loading the homepage contacts 46 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 glercbikes.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 29 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Cartsee Email Marketing Sms · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Simprosys Google Shopping Feed · Hulk Form Builder · Impact Com · Judge Me Reviews · Gsc Countdown Timer · Seowill Ai Seo · Omnisend · Selleasy · Pushowl · Tms Prod V 71ff83e · Social Widget · Gdpr Backpack · Captain Shipping Protection · Essential Pre Order Presale · Vizup · Grouptify Combined Listings · Essential Cart Drawer · Bestpush · Freegifts · Powr Popup · amazonaws.com · goaffpro.com · conversionbear.com · trustedshops.com · bogos.io

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
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on glercbikes.de, including 22 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

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