Website review, no card needed

germanxia.com logo

germanxia.com website review

Visit site (opens in a new tab)Reviewed 11 November 202649 issues · 88 checks

This review found 49 issues worth fixing on germanxia.com, 17 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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 germanxia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. germanxia.com at 0.6 s0.6 s
  2. germanxia.com at 1.1 s1.1 s
  3. germanxia.com at 1.7 s1.7 s
  4. germanxia.com at 2.2 s2.2 s
  5. germanxia.com at 2.8 s2.8 s
  6. germanxia.com at 3.3 s3.3 s
  7. germanxia.com at 3.9 s3.9 s
  8. germanxia.com at 4.4 s4.4 s

Speed

13 to fix47
  • Reduce unused JavaScript

    2.0 s · 942 KiB

    About 942 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

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

  • Improve image delivery

    7.0 MB

    12 images could be 7.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, PayPal and plentyone.com and others), adding 16.2 MB and 1.4 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 2.2 MB

    65 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • plentyone.com adds 188 ms

    188 ms

    plentyone.com costs a phone 188 ms of main-thread work and 14.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 660 ms

    660 ms

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

  • 14 long tasks on the main thread

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

  • PayPal adds 224 ms

    224 ms

    PayPal costs a phone 224 ms of main-thread work and 331 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.

  • 2,251 HTML elements

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

  • Other Google APIs/SDKs adds 39 ms

    39 ms

    Other Google APIs/SDKs costs a phone 39 ms of main-thread work and 511 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.

  • Legacy JavaScript

    150 ms · 45 KiB

    Polyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Reduce unused CSS

    42 KiB

    About 42 KiB of CSS is downloaded but never applied on this page.

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 239 ms

    239 ms

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

Core Web Vitals

6 to fix48
  • Largest Contentful Paint: 26.0 s

    26.0 s

    Your largest element takes 26.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Das erste TÜV-zertifizierte Falt-S-Pedelec mit 45 km/h in D…”.

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 40.2 s

    40.2 s

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

  • Total Blocking Time: 698 ms

    698 ms

    Scripts block taps and scrolling for 698 ms in total while the page loads. Good is under 200 ms.

  • 20 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 17.7 MB in 156 requests

    17.7 MB

    Your homepage downloads 17.7 MB in 156 requests on a phone: images 15.3 MB (48), scripts 1.7 MB (41) and other files 461 KiB (54). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    5.4 MB

    8 images are downloaded at several times the size a phone draws them, for example Mobilemaster_Rohloff_E-14_PT_CX.jpg at 6,000 px wide, shown at 174 px. Resized copies would save about 5.4 MB.

  • 3 images over 500 KB

    3 images weigh 4.5 MB together. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (4.5 MB) are 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.

  • 7 images below the first screen load straight away

    7 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.0 g of CO₂ per visit

    5.02 g

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

Accessibility

10 to fixGoogle 7987
  • Certain ARIA roles must contain particular children (7 elements)

    Certain ARIA roles must contain particular children: 7 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (7 elements)

    Certain ARIA roles must be contained by particular parents: 7 elements on the page fail this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • ARIA toggle fields must have an accessible name (7 elements)

    ARIA toggle fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 12 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (7 elements)

    ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

  • 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, h1 → h3 and 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. (3 elements).

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8573
  • Title is long (112 characters)

    Your title is 112 characters, so Google will cut it off around 60: “Premium Elektro-Klapprad in Köln kaufen | Hergestellt in Köln | GermanXia - Ihr Kölner Sp…”.

  • 8 H1 headlines

    There are 8 <h1> headlines (“Das erste TÜV-zertifizierte Falt-S-Pedelec mit 45…”, “So flexibel wie Ihr Alltag - das Light E8 SX55!” and “Minimalismus trifft auf Klapp-Innovation: das Roh…”). One clear main headline is easier for people and search engines.

  • Meta description is long (208 characters)

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

    No XML sitemap at https://www.germanxia.de/sitemap.xmll, so Google discovers your pages only by following links.

  • 15 links crawlers can't follow

    15 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 161 internal links, 22 external

    The homepage links to 161 pages on germanxia.com and 22 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.germanxia.de/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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.

  • No llms.txt

    There is no https://www.germanxia.de/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
  • 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 (1,730 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.germanxia.de/blog and https://www.germanxia.de/wish-list have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages slow to respond

    https://www.germanxia.de/e-klapprad/mobilemaster-cx, https://www.germanxia.de/e-klapprad/offroad-gt-bosch, https://www.germanxia.de/e-klapprad/offroad-gt-bosch/e-14, https://www.germanxia.de/e-klapprad/offroad-gt-bosch/n380, https://www.germanxia.de/e-klapprad/offroad-gt-bosch/shimano-e5-e8-e11 and https://www.germanxia.de/e-klapprad/offroad-gt-bosch/touren and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5291
  • 1 third-party cookie

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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 827 words of copy

    The homepage carries about 827 words of visible text.

2 checks passed
  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 5 cookies set on arrival

    5

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

  • 27 other companies contacted

    Loading the homepage contacts 27 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 germanxia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
plentymarkets
Framework
Vue.js
E-commerce
10 Shopify Products;Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
Analytics
Google Analytics | Google Tag Manager
Hosting
dogado GmbH

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on germanxia.com, including 19 speed issues, 6 SEO issues and 4 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