Website review, no card needed

stempel.eu.com logo

stempel.eu.com website review

Visit site (opens in a new tab)Reviewed 5 November 202627 issues · 75 checks

This review found 27 issues worth fixing on stempel.eu.com, 4 of them high impact, across 75 checks. The most urgent: 1 linked page is broken. 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 stempel.eu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix90
  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    150 ms · 479 KiB

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

  • 1,986 HTML elements

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

  • Shopify adds 26 ms

    26 ms

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

  • vimando.com adds 0 ms

    0 ms

    vimando.com costs a phone 0 ms of main-thread work and 309 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.

  • Reduce unused JavaScript

    200 KiB

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

  • Reduce unused CSS

    150 ms · 42 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Clarity, Shopify and Judge.me and others), adding 658 KiB and 125 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    14 KiB

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

3 checks passed
  • Mobile performance score: 90

    90/100

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

  • Main-thread work: 1.5 s

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

  • Server response: 45 ms

    45 ms

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

Core Web Vitals

4 to fix89
  • Time to Interactive: 7.1 s

    7.1 s

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

  • 36 images without width and height

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

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

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 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.

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

    0

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

  • Total Blocking Time: 17 ms

    17 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.8 MB in 236 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 236 requests on a phone: other files 1.1 MB (140), images 985 KiB (44) and scripts 499 KiB (35). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    31 KiB

    2 images are downloaded at several times the size a phone draws them, for example search_related.png at 400 px wide, shown at 120 px. Resized copies would save about 31 KiB.

  • 5 images in older formats

    5 images (272 KiB) 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.

  • 5 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

4 to fixGoogle 9489
  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 3 images without alt text

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

  • 15 links without text

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

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h4, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 23 automated accessibility rules passed

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

SEO

5 to fixGoogle 9282
  • Canonical points to another host

    Your canonical URL points to topstempel.de, not stempel.eu.com, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Stempel bestellen” and “STEMPEL BESTELLEN BEI topstempel.de”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 278 internal links, 0 external

    The homepage links to 278 pages on stempel.eu.com and 0 external pages.

4 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Stempel online bestellen, einfach und günstig. & Online Text Editor & Grafik-Upload & Top Preise & Bis 14h bestellt, am…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Stempel bestellen (Trodat | Colop) im schnellsten Stempelshop”.

  • 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://stempel.eu.com/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 (1,729 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://stempel.eu.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://stempel.eu.com/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages share a title

    https://stempel.eu.com/pages/designer, https://stempel.eu.com/pages/designer/image and https://stempel.eu.com/pages/designer/text_image all use the title “Stempel mit eigenem Text individuell gestalten”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://stempel.eu.com/pages/designer, https://stempel.eu.com/pages/designer/image and https://stempel.eu.com/pages/designer/text_image use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=56030216&tm=gtm002&Ver=2&mid=f46780e4-7556-4c50-af97-6e96f6b9c3ba&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Stempel%20bestellen%20(Trodat%20%7C%20Colop)%.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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,391 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “zum Shop”.

  • 1 call to action

    The homepage has 1 call to action, for example “zum Shop”.

  • 6 short forms

    6 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 124 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 4 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 stempel.eu.com, 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

Microsoft Clarity · Judge Me Reviews

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

Framework
Tailwind CSS
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 27 issues on stempel.eu.com, including 9 speed issues and 5 SEO issues. 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