3pagen.de website review

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

15 images could be 365 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

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

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

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

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

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

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

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

2 third-party services load with your homepage (Trusted Shops and goodays.co), adding 152 KiB and 22 ms of main-thread time.

20 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “3PAGEN setzt Cookies mit unterschiedlichen Funktionen ein. …”.

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

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

The layout shifts by 0.13 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 2.2 MB in 80 requests on a phone: images 1.6 MB (51), scripts 291 KiB (9) and stylesheets 149 KiB (2). Under 2 MB keeps phones on slow connections fast.

14 images (1.3 MB) 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.

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

1 image is downloaded at several times the size a phone draws it, for example Mini_Winterschuhe_DE-37480-0.jpg at 1,475 px wide, shown at 390 px. Resized copies would save about 39 KiB.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

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

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

The homepage links to 530 pages on 3pagen.de and 6 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/direct-order and /weihnachten/weihnachtsdeko/schneemaenner are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/direct-order and /weihnachten have no meta description, so Google writes the search snippet from whatever text it finds.

/direct-order and /weihnachten have no <h1> headline, so visitors and search engines get no clear main topic.

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

20 of 88 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Trustbadge: Missing container for custom mobile trustbadge div#MyCustomTrustbadge”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

1 link go through two or more redirects, for example https://www.3pagen.de/account/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

3pagen.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 584 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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.

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