peter-park.de website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

3 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

28 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

8 third-party services load with your homepage (website-files.com, Hubspot and cookiehub.eu and others), adding 7.6 MB and 376 ms of main-thread time.

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

website-files.com costs a phone 162 ms of main-thread work and 6.0 MB 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.2 s on main-thread work while loading, 825 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Amazon Web Services costs a phone 0 ms of main-thread work and 1.2 MB 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.

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

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

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

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 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden auf unserer Webseite Cookies und ähnliche Tec…”.

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

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

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

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

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

Your homepage downloads 7.7 MB in 87 requests on a phone: images 5.3 MB (31), media 1.2 MB (5) and scripts 541 KiB (37). Under 2 MB keeps phones on slow connections fast.

69ba0d2d4df8ab8f2de4acee_06b734cc4956c2f21be5353e8970a404_Fr weighs 653 KiB. On a phone connection a single image that size takes seconds.

69ba0d2d4df8ab8f2de4acee_06b734cc4956c2f21be5353e8970a404_Fr 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 (132 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 2.18 g of CO₂e: 261.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

1 image has no alt text, which hurts accessibility and image search.

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

The homepage links to 105 pages on peter-park.de and 10 external pages.

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.

There is no https://www.peter-park.de/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.

https://www.peter-park.de/branche/badeseen-und-kustenregion and https://www.peter-park.de/branche/bahnhoefe-und-flughafen have no <title>, so Google invents the link text in results.

/, https://www.peter-park.de/ch, https://www.peter-park.de/de-at and https://www.peter-park.de/de-it all use the title “Peter Park | Digitales Parkraummanagement mit KI-Technologie”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.peter-park.de/branche/badeseen-und-kustenregion and https://www.peter-park.de/branche/bahnhoefe-und-flughafen have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.peter-park.de/ch, https://www.peter-park.de/de-at and https://www.peter-park.de/de-it use the same meta description. A description written for each page earns more clicks.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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