primeros.de website review

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

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

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Erste-Hilfe-Kurse in deiner Nähe Für den Führerschein, den …”.

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

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

2 images (83 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.

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

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

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

8 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: 10 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.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 68 characters, so Google will cut it off around 60: “PRIMEROS | Erste-Hilfe-Kurse in deiner Nähe – Führerschein & Betrieb”.

No Open Graph image, 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 111 pages on primeros.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://www.primeros.de/ersthelferausbildung, https://www.primeros.de/brandschutzhelferausbildung and https://www.primeros.de/jobs have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.primeros.de/ersthelferausbildung and https://www.primeros.de/jobs have no <h1> headline, so visitors and search engines get no clear main topic.

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

19 of 37 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 677 words of visible text.

Opening the homepage sets 1 cookie (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.