Website review, no card needed

die-lohners.de logo

die-lohners.de website review

Visit site (opens in a new tab)Reviewed 21 October 202630 issues · 77 checks

This review found 30 issues worth fixing on die-lohners.de, 9 of them high impact, across 77 checks. The most urgent: render-blocking 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.0 s1.6 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 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
Real-visitor tap response (INP)75th percentile, phones
99 ms92 msMay 2Oct 1795 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202697 ms
May 16, 202697 ms
May 23, 202697 ms
May 30, 202698 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202697 ms
Jun 27, 202696 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202694 ms
Jul 25, 202693 ms
Aug 1, 202693 ms
Aug 8, 202694 ms
Aug 15, 202695 ms
Aug 22, 202695 ms
Aug 29, 202695 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202695 ms
Oct 3, 202695 ms
Oct 10, 202695 ms
Oct 17, 202695 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 die-lohners.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. die-lohners.de at 0.8 s0.8 s
  2. die-lohners.de at 1.5 s1.5 s
  3. die-lohners.de at 2.3 s2.3 s
  4. die-lohners.de at 3.0 s3.0 s
  5. die-lohners.de at 3.8 s3.8 s
  6. die-lohners.de at 4.5 s4.5 s
  7. die-lohners.de at 5.3 s5.3 s
  8. die-lohners.de at 6.0 s6.0 s

Speed

7 to fix62
  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    500 ms · 299 KiB

    4 images could be 299 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Reduce unused JavaScript

    300 ms · 119 KiB

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

  • Reduce unused CSS

    300 ms · 75 KiB

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

  • iubenda adds 293 ms

    293 ms

    iubenda costs a phone 293 ms of main-thread work and 124 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.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 1.1 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 (iubenda, b-ite.com and Secomapp and others), adding 452 KiB and 413 ms of main-thread time.

  • Use efficient cache lifetimes

    200 ms · 52 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    25 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 95 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 57 ms

    57 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.2 s).

  • Speed Index: 8.8 s

    8.8 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Time to Interactive: 7.8 s

    7.8 s

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

  • 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

    -2%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

8 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: 2.2 s

    2.2 s

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

  • Real-user INP: 93 ms

    93 ms

    Real visitors wait 93 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.9 s

    0.9 s

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

  • Real-user TTFB: 348 ms

    348 ms

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

  • Total Blocking Time: 88 ms

    88 ms

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 164 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 164 requests on a phone: other files 760 KiB (91), images 574 KiB (12) and scripts 535 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    36 KiB

    1 image is downloaded at several times the size a phone draws it, for example RPR1.Zuckerschnecke_Ani_FINAL.00_00_00_00.Standbild002_x800. at 1,422 px wide, shown at 390 px. Resized copies would save about 36 KiB.

  • 1 image in older formats

    1 image (103 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.

  • 2 images below the first screen load straight away

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

  • About 0.6 g of CO₂ per visit

    0.59 g

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

Accessibility

5 to fixGoogle 8393
  • 3 text elements with low contrast

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

  • 4 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Meta description is long (296 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 87 internal links, 34 external

    The homepage links to 87 pages on die-lohners.de and 34 external pages.

6 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “Dein Lieblingsbäcker - Natürlich "Die Lohners"”.

  • Canonical URL set

    The canonical URL is https://die-lohners.de/.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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://die-lohners.de/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 (344 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 8 pages without a meta description

    https://die-lohners.de/pages/vision, https://die-lohners.de/pages/regionalitaet, https://die-lohners.de/pages/vereinsrabatt, https://die-lohners.de/pages/gin, https://die-lohners.de/pages/expansion and https://die-lohners.de/pages/lohners-fruhstucksbuffet and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://die-lohners.de/pages/vision, https://die-lohners.de/pages/nachhaltigkeit, https://die-lohners.de/collections/unserebrote, https://die-lohners.de/collections/broetchen, https://die-lohners.de/collections/teilchen and https://die-lohners.de/collections/kuchen and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 to fixGoogle 7785
  • 5 small tap targets

    5 of 23 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

1 checks passed
  • 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 social proof

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

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

    The homepage carries about 297 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Online-Shop” and “Online-ShopOnline-Shop”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 22 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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 die-lohners.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify

Company

Founded
1912
Headquarters
Polch

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on die-lohners.de, including 12 speed issues, 2 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