helpling.de website review

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

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

Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.

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

4 third-party services load with your homepage (Braze, VWO and FontAwesome CDN and others), adding 366 KiB and 179 ms of main-thread time.

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

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

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

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

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 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “De Message Autumn”. Most of its time is element render delay (1.8 s).

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 image further down the page (39 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Structured data found (ImageObject, ItemPage, LocalBusiness and Organization) but with 1 problem, for example “Product: no offers (price) block”.

No XML sitemap at https://www.helpling.de/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at helpling.de/robots.txt, the first file search crawlers ask for.

The homepage links to 85 pages on helpling.de and 32 external pages.

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.

Your homepage links to /putzfrau/hamburg, which answers with an error. Visitors hit a dead end and search engines drop it.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /de_en, whose canonical is /de_en/de_en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/blog has no <h1> headline, so visitors and search engines get no clear main topic.

/de_en, /haftpflichtversicherung, /faq, /putzfrau/berlin, /putzfrau/muenchen and /putzfrau/frankfurt-main took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.helpling.de/wp-content/uploads/2023/08/Helpling_Map_DE-720x461.webp.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 502 ()”.

2 links from your homepage to your own site are broken, for example https://www.helpling.de/vergleich/ (502).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

helpling.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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 474 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 11 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.