Website review, no card needed

allett.de logo

allett.de website review

Visit site (opens in a new tab)Reviewed 9 November 202621 issues · 65 checks

This review found 21 issues worth fixing on allett.de, 4 of them high impact, across 65 checks. The most urgent: no call to action on the first screen. 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.0 s867 msMay 16Sep 5998 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026916 ms
May 23, 2026956 ms
May 30, 2026915 ms
Jun 6, 2026893 ms
Jun 13, 2026909 ms
Jun 20, 2026884 ms
Jun 27, 2026912 ms
Jul 4, 2026949 ms
Jul 11, 2026953 ms
Jul 18, 2026962 ms
Jul 25, 2026986 ms
Aug 1, 2026999 ms
Aug 8, 2026987 ms
Aug 15, 2026964 ms
Aug 22, 2026953 ms
Aug 29, 2026972 ms
Sep 5, 2026998 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms71 msMay 16Aug 2973 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202672 ms
May 23, 202676 ms
May 30, 202672 ms
Jun 6, 202673 ms
Jun 13, 202674 ms
Jun 20, 202674 ms
Jun 27, 202678 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202680 ms
Aug 29, 202673 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 allett.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix72
  • Improve image delivery

    650 ms · 451 KiB

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

  • Mobile performance score: 72

    72/100

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

  • Render-blocking requests

    400 ms

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

  • Legacy JavaScript

    200 ms · 80 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 233 KiB and 68 ms of main-thread time.

  • Reduce unused CSS

    23 KiB

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

  • Use efficient cache lifetimes

    5 KiB

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 9.2 s

    9.2 s

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

  • Time to Interactive: 9.2 s

    9.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Speed Index: 3.9 s

    3.9 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

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

2 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix81
  • Page weight: 2.2 MB in 220 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 220 requests on a phone: other files 897 KiB (132), images 786 KiB (7) and scripts 464 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    ALLETT-Int-Hero-Homeowner-3_750x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.4 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

1 to fixGoogle 10099
  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor 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 19 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10080
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “ALLETT Mäher - Spindelmaher für Privatkunden und Profikunden – ALLETT Deutschland”.

  • Meta description is long (314 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 110 internal links, 14 external

    The homepage links to 110 pages on allett.de and 14 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://allett.de/collections/maeher-fuer-privatkunden, https://allett.de/pages/stirling, https://allett.de/pages/liberty, https://allett.de/pages/kensington, https://allett.de/pages/classic and https://allett.de/pages/sandringham and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://allett.de/pages/stirling, https://allett.de/pages/cambridge, https://allett.de/pages/liberty, https://allett.de/pages/kensington, https://allett.de/pages/classic and https://allett.de/pages/sandringham and 8 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 58 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 10 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 social proof

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

  • No analytics detected

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

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

    The homepage carries about 380 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “SHOP BESUCHEN”.

  • 4 short forms

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 9 cookies set on arrival

    9

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

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 allett.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

T Lab Ai Translate · Frontend

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on allett.de, including 7 speed issues, 4 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