sagaflor.de website review

7 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.8 s faster on a phone.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying CSS.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diese Website benutzt Cookies, die für den technischen Betr…”.

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

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

7 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' tap response (inp) went from 74 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.4 MB in 29 requests on a phone: images 3.2 MB (14), fonts 128 KiB (5) and stylesheets 47 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example logo_pool-dbia.png at 3,334 px wide, shown at 128 px. Resized copies would save about 191 KiB.

4 images (485 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.

3 images further down the page (241 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.96 g of CO₂e: 115.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Your title is 86 characters, so Google will cut it off around 60: “SAGAFLOR AG - Dienstleistungszentrale und Verbundgruppe für Garten- und Tierfachmärkte”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 37 pages on sagaflor.de and 11 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.sagaflor.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.sagaflor.de/unternehmen has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sagaflor.de/presse and https://www.sagaflor.de/kontakt 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.

https://www.sagaflor.de/presse/detail/vom-gewaechshaus-zur-theaterbuehne took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “$ is not defined”.

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.

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

Social proof on the homepage: 4 customer or partner logos. 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 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 321 words of visible text.

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.