Website review, no card needed

onlinestempel.ch logo

onlinestempel.ch website review

Visit site (opens in a new tab)Reviewed 11 November 202637 issues · 84 checks

This review found 37 issues worth fixing on onlinestempel.ch, 8 of them high impact, across 84 checks. The most urgent: 5 buttons without a name. 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 onlinestempel.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix87
  • Mobile performance score: 87

    87/100

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

  • Font display

    800 ms

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

  • Render-blocking requests

    800 ms

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

  • Improve image delivery

    200 ms · 432 KiB

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

  • Main-thread work: 2.1 s

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

  • 1,942 HTML elements

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

  • Shopify adds 39 ms

    39 ms

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

  • 4 third-party services on the page

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

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

  • 3 long tasks on the main thread

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

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

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

    48 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 7.1 s

    7.1 s

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

  • Speed Index: 5.0 s

    5.0 s

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

9 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.0 s

    1.0 s

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

  • Real-user INP: 72 ms

    72 ms

    Real visitors wait 72 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: 421 ms

    421 ms

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

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

    44 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.9 MB in 233 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 233 requests on a phone: other files 1.2 MB (140), images 923 KiB (42) and scripts 501 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    30 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 30 KiB.

  • 4 images in older formats

    4 images (233 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.81 g

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

Accessibility

9 to fixGoogle 7788
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

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

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

  • All page content should be contained by landmarks (8 elements)

    All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

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

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

  • 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
  • 51 automated accessibility rules passed

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

SEO

6 to fixGoogle 8579
  • 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 ONLINESTEMPEL.CH”). 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.

  • No XML sitemap

    No XML sitemap at https://onlinestempel.ch/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at onlinestempel.ch/robots.txt, the first file search crawlers ask for.

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

  • 276 internal links, 0 external

    The homepage links to 276 pages on onlinestempel.ch and 0 external pages.

3 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Stempel einfach online bestellen auf onlinestempel.ch. ✓ Stempel online gestalten ✓ Schweizer Produktion ✓ Versand ► Bi…”.

  • Title: 64 characters

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

  • Canonical URL set

    The canonical URL is https://onlinestempel.ch/.

AI search readiness

1 to fix81
  • 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.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (1,788 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix67
  • 1 linked page is broken

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

  • 3 pages share a title

    https://onlinestempel.ch/pages/designer, https://onlinestempel.ch/pages/designer/image and https://onlinestempel.ch/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://onlinestempel.ch/pages/designer, https://onlinestempel.ch/pages/designer/image and https://onlinestempel.ch/pages/designer/text_image use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://onlinestempel.ch/pages/delivery, https://onlinestempel.ch/pages/new-store and https://onlinestempel.ch/pages/designer took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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: 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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,446 words of copy

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

4 checks passed
  • 5 short forms

    5 short forms (1 field 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.

  • 8 cookies set on arrival

    8

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 onlinestempel.ch, 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

Judge Me Reviews · Microsoft Clarity

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 37 issues on onlinestempel.ch, including 12 speed issues, 6 SEO issues and 2 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