pergolux.de website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, SpeedCurve RUM and Affiliate Window and others), adding 661 KiB and 207 ms of main-thread time.

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

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

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

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

About 14 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.

For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.

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

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

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

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

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

2 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' largest content (lcp) went from 2.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.4 MB in 217 requests on a phone: images 1.0 MB (34), other files 806 KiB (97) and scripts 533 KiB (78). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 2408_PERGOLUX_Pergola_S2_4x6_White_Wall-Mounted_Fabian_Germa at 1,800 px wide, shown at 350 px. Resized copies would save about 137 KiB.

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

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

ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

The homepage links to 128 pages on pergolux.de and 12 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://pergolux.de/products/pergola-pro and https://pergolux.de/products/pergola-pro-max use the same meta description. A description written for each page earns more clicks.

https://pergolux.de/products/pergola, https://pergolux.de/products/pergola-pro, https://pergolux.de/products/pergola-pro-max, https://pergolux.de/products/pergola-custom-design-plus and https://pergolux.de/products/markise have no <h1> headline, so visitors and search engines get no clear main topic.

https://pergolux.de/products/pergola and https://pergolux.de/products/pergola-pro have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,475 words of visible text.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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 16 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.