Website review, no card needed

backontrack.de logo

backontrack.de website review

Visit site (opens in a new tab)Reviewed 8 November 202623 issues · 95 checks

This review found 23 issues worth fixing on backontrack.de, 6 of them high impact, across 95 checks. The most urgent: page weight: 14.1 MB in 174 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
1.3 s599 msMay 16Oct 31681 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 2026918 ms
Oct 3, 2026789 ms
Oct 10, 2026717 ms
Oct 17, 2026702 ms
Oct 24, 2026694 ms
Oct 31, 2026681 ms
Real-visitor tap response (INP)75th percentile, phones
114 ms85 msMay 16Oct 31111 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202689 ms
May 23, 202688 ms
May 30, 202688 ms
Jun 6, 202688 ms
Jun 13, 202688 ms
Jun 20, 202692 ms
Jun 27, 202692 ms
Jul 4, 202691 ms
Jul 11, 202691 ms
Jul 18, 202690 ms
Jul 25, 202689 ms
Aug 1, 202690 ms
Aug 8, 202689 ms
Aug 15, 202689 ms
Aug 22, 202690 ms
Aug 29, 202688 ms
Sep 5, 202689 ms
Sep 12, 202692 ms
Sep 19, 202695 ms
Sep 26, 202697 ms
Oct 3, 2026103 ms
Oct 10, 2026105 ms
Oct 17, 2026105 ms
Oct 24, 2026106 ms
Oct 31, 2026111 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 backontrack.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

backontrack.de does not allow embedding, so this is Google's rendering of the page.

Speed

5 to fix91
  • 3,062 HTML elements

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (good-apps.co and Shopify), adding 12.6 MB and 42 ms of main-thread time.

  • Shopify adds 21 ms

    21 ms

    Shopify costs a phone 21 ms of main-thread work and 12.6 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.

  • Render-blocking requests

    450 ms

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

  • Improve image delivery

    350 ms · 77 KiB

    5 images could be 77 KiB 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.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    26 KiB

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

  • Use efficient cache lifetimes

    22 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (22 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.

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 38 ms

    38 ms

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

Core Web Vitals

2 to fix100
  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

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

12 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: 0.8 s

    0.8 s

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

  • Real-user INP: 139 ms

    139 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 338 ms

    338 ms

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

  • Largest content (LCP) got 44% faster for real visitors

    -44%

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

  • Time to Interactive: 3.5 s

    3.5 s

    The page is fully interactive after 3.5 s.

  • Speed Index: 2.8 s

    2.8 s

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.02

    0.02

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

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

1 to fix70
  • Page weight: 14.1 MB in 174 requests

    14.1 MB

    Your homepage downloads 14.1 MB in 174 requests on a phone: media 12.5 MB (2), images 629 KiB (37) and other files 616 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • About 4.0 g of CO₂ per visit

    4.00 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9696
  • 30 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Wohlbefinden durch Innovation.”). One clear main headline is easier for people and search engines.

  • 362 internal links, 8 external

    The homepage links to 362 pages on backontrack.de and 8 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Back on Track® wurde im Jahre 2000 mit der Vision gegründet, Produkte zu entwickeln, die Mensch und Tier im Alltag unte…”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Back on Track® – Back on Track Europe”.

  • Canonical URL set

    The canonical URL is https://backontrack.de/.

  • 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://backontrack.de/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    /collections/neu-und-demnaechst-erhaeltlich, /collections/bandagen-und-stuetzen, /collections/bandagen-und-stuetzen-strapz, /collections/cool-on-track%C2%AE-human, /collections/bandagen-und-stuetzen-nacken-und-schultern and /collections/bandagen-und-stuetzen-ellenbogen and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example /collections/cool-on-track%C2%AE-human, whose canonical is /collections/cool-on-track%c2%ae-human. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 169 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.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://facebook.com/backontrackofficial.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (backontrack.de).

  • Valid certificate (49 days left)

    The certificate from Let's Encrypt · YE1 verifies for backontrack.de and is valid for another 49 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://backontrack.de redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 45 links work

    All 45 links checked from your homepage (40 internal, 5 external) answered without errors.

Domain and trust

  • No CAA record

    backontrack.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

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

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

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

  • 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 710 words of copy

    The homepage carries about 710 words of visible text.

2 checks passed
  • 7 short forms

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

  • Direct contact links

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

Email authentication

2 to fix60
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be backontrack.de is still delivered. Add a report address, check the reports, then move to quarantine.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 60/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 +a +mx +ip4:91.201.63.139 ~all”.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 14 cookies set on arrival

    14

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

  • 8 other companies contacted

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

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

good-apps.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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

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 23 issues on backontrack.de, including 7 speed issues, 1 SEO issue and 6 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