Website review, no card needed

lopalmed.de logo

lopalmed.de website review

Visit site (opens in a new tab)Reviewed 10 November 202623 issues · 78 checks

This review found 23 issues worth fixing on lopalmed.de, 7 of them high impact, across 78 checks. The most urgent: main-thread work: 9.2 s. 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.8 s1.0 sMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
149 ms131 msMay 23Nov 7136 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026139 ms
May 30, 2026137 ms
Jun 6, 2026138 ms
Jun 13, 2026137 ms
Jun 20, 2026138 ms
Jun 27, 2026143 ms
Jul 4, 2026146 ms
Jul 11, 2026147 ms
Jul 18, 2026145 ms
Jul 25, 2026138 ms
Aug 1, 2026135 ms
Aug 8, 2026135 ms
Aug 15, 2026134 ms
Aug 22, 2026136 ms
Aug 29, 2026136 ms
Sep 5, 2026135 ms
Sep 12, 2026136 ms
Sep 19, 2026136 ms
Sep 26, 2026137 ms
Oct 3, 2026138 ms
Oct 10, 2026137 ms
Oct 17, 2026136 ms
Oct 24, 2026133 ms
Oct 31, 2026137 ms
Nov 7, 2026136 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 lopalmed.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lopalmed.de at 1.9 s1.9 s
  2. lopalmed.de at 3.8 s3.8 s
  3. lopalmed.de at 5.7 s5.7 s
  4. lopalmed.de at 7.5 s7.5 s
  5. lopalmed.de at 9.4 s9.4 s
  6. lopalmed.de at 11.3 s11.3 s
  7. lopalmed.de at 13.2 s13.2 s
  8. lopalmed.de at 15.1 s15.1 s

Speed

7 to fix87
  • Main-thread work: 9.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and omnisnippet1.com and others), adding 969 KiB and 1.0 s of main-thread time.

  • Mobile performance score: 87

    87/100

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

  • Shopify adds 430 ms

    430 ms

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

  • Render-blocking requests

    450 ms

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

  • Clarity adds 305 ms

    305 ms

    Clarity costs a phone 305 ms of main-thread work and 29 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.

  • 1,853 HTML elements

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

  • Reduce unused JavaScript

    225 KiB

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    111 KiB

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

  • Improve image delivery

    50 KiB

    5 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    27 KiB

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

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

    14 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 7.5 s

    7.5 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Herbst-Aktionsbanner: Lopalmed-Flasche und Füße auf blauer …”.

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

11 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.2 s

    1.2 s

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

  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 399 ms

    399 ms

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

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

    -34%

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

  • Total Blocking Time: 166 ms

    166 ms

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

  • Speed Index: 2.5 s

    2.5 s

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 394 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 394 requests on a phone: other files 1.5 MB (262), scripts 743 KiB (60) and images 725 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.89 g

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

2 checks passed
  • 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

2 to fixGoogle 9796
  • 6 text elements with low contrast

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

  • Scrollable region must have keyboard access (6 elements)

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

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 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
  • Meta description is long (165 characters)

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

  • 44 internal links, 5 external

    The homepage links to 44 pages on lopalmed.de and 5 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Gepflegte Füße ohne lästige Hornhaut in wenigen Minuten”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Lopalmed - Der sanfte Weg zu schönen Händen und gesunden Füßen”.

  • Canonical URL set

    The canonical URL is https://lopalmed.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://lopalmed.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,403 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://lopalmed.de/discount/SOFT10 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://lopalmed.de/discount/SOFT10 all use the title “Lopalmed - Der sanfte Weg zu schönen Händen und gesunden Füßen”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://lopalmed.de/policies/shipping-policy and https://lopalmed.de/policies/legal-notice have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://lopalmed.de/pages/haendler has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://lopalmed.de/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.

  • 2 pages slow to respond

    https://lopalmed.de/pages/hornhaut-entfernen and https://lopalmed.de/blogs/gepflegte-fuesse-und-haende/wie-hornhaut-an-den-handen-entfernen-eine-umfassende-anleitung took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.plyr.io/3.7.8/plyr.css' from origin 'https://lopalmed.de' has been blocked by …”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 98 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 23 cookies set on arrival

    23

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

  • 36 other companies contacted

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

Apps your storefront loads

Geo Pro Geolocation · Sami Wholesale · T Lab Ai Translate · Microsoft Clarity · Judge Me Reviews · Easylocation · Omnisend

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
Google Tag Manager | Microsoft Clarity
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 lopalmed.de, including 10 speed issues, 1 SEO issue 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