penoblo.de website review

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

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, gsitrix.com and Shopify and others), adding 2.0 MB and 669 ms of main-thread time.

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

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

Google Tag Manager costs a phone 357 ms of main-thread work and 774 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.

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

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

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

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

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

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pelikan, Füller, Souverän M800, 18Kt, Indian Ocean”.

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

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

Real visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Scripts block taps and scrolling for 213 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 6.0 MB in 572 requests on a phone: images 3.0 MB (240), scripts 1.4 MB (99) and other files 1,000 KiB (172). Under 2 MB keeps phones on slow connections fast.

pnb-campaign-montblanc-mobile.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).

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your <h1> is empty.

The homepage links to 613 pages on penoblo.de and 26 external pages.

https://www.penoblo.de/collections/all, https://www.penoblo.de/policies/shipping-policy, https://www.penoblo.de/collections/neuheiten, https://www.penoblo.de/collections/sets-und-geschenksets and https://www.penoblo.de/collections/kalligrafie have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.penoblo.de/pages/marken, whose canonical is https://www.penoblo.de/pages/marken-bei-penoblo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.penoblo.de/collections/all, https://www.penoblo.de/policies/shipping-policy, https://www.penoblo.de/collections/sale, https://www.penoblo.de/collections/edle-schreibgerate, https://www.penoblo.de/pages/marken and https://www.penoblo.de/collections/refills and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.penoblo.de/collections/montblanc-kugelschreiber took over 3 s to send its HTML from our server.

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

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 870 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 14 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.