simplyketo.de website review

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

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

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

8 third-party services load with your homepage (Cookiebot, Shopify and JSDelivr CDN and others), adding 1.7 MB and 991 ms of main-thread time.

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

Shopify costs a phone 350 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.

Cookiebot costs a phone 437 ms of main-thread work and 162 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.

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

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

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

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

90 KiB could be saved by minifying JavaScript.

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

4 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 110 ms to 157 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.3 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Scripts block taps and scrolling for 384 ms in total while the page loads. Good is under 200 ms.

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

Your homepage downloads 4.3 MB in 410 requests on a phone: scripts 1.4 MB (155), other files 1.3 MB (171) and images 853 KiB (43). Under 2 MB keeps phones on slow connections fast.

Traumschaum_Erdbeere_Web_02.jpg 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).

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

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Elements with visible text labels do not have matching accessible names. (1 element).

Your meta description is 278 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//simplyketo.de/cdn/shop/files/sk-logo-new.png?crop=cen…”.

The homepage links to 319 pages on simplyketo.de and 5 external pages.

https://simplyketo.de/collections/bestseller, https://simplyketo.de/collections/neuheiten-1, https://simplyketo.de/collections/susse-backmischungen, https://simplyketo.de/collections/mehl-alternativen, https://simplyketo.de/collections/sussungsmittel and https://simplyketo.de/collections/herzhafte-backmischungen and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://simplyketo.de/collections/bestseller, https://simplyketo.de/collections/neuheiten-1, https://simplyketo.de/collections/susse-backmischungen, https://simplyketo.de/collections/mehl-alternativen, https://simplyketo.de/collections/sussungsmittel and https://simplyketo.de/collections/herzhafte-backmischungen and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 138 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: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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: 62 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

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