prepmymeal.ch website review

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

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

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

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

Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Shopify, Bold Commerce and weglot.com and others), adding 2.7 MB and 1.7 s of main-thread time.

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

Shopify costs a phone 334 ms of main-thread work and 292 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.

Bold Commerce costs a phone 254 ms of main-thread work and 484 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.

ablyft.com costs a phone 200 ms of main-thread work and 772 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.

Reviews.io costs a phone 174 ms of main-thread work and 296 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.

Klaviyo costs a phone 154 ms of main-thread work and 331 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.

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

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Your largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hast du den richtigen Standort ausgewählt?”.

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

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

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

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

Your homepage downloads 12.5 MB in 539 requests on a phone: media 4.4 MB (1), images 3.5 MB (82) and scripts 2.5 MB (111). Under 2 MB keeps phones on slow connections fast.

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

5 images are downloaded at several times the size a phone draws them, for example gemusebowl600x.webp at 365 px wide, shown at 100 px. Resized copies would save about 122 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 3.53 g of CO₂e: 423.5 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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your <h1> is empty.

The homepage links to 44 pages on prepmymeal.ch and 19 external pages.

Your homepage links to https://prepmymeal.ch/products/12er-meal-box-individuell and https://prepmymeal.ch/null, which answer with an error. Visitors hit a dead end and search engines drop them.

https://prepmymeal.ch/pages/blog-1, https://prepmymeal.ch/products/ch-meal-box, https://prepmymeal.ch/policies/terms-of-service, https://prepmymeal.ch/policies/refund-policy and https://prepmymeal.ch/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://prepmymeal.ch/products/12er-meal-box-ch, https://prepmymeal.ch/products/6er-meal-box-ch, https://prepmymeal.ch/products/18er-meal-box-ch and https://prepmymeal.ch/products/24er-meal-box-ch use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://prepmymeal.ch/products/gift-card, whose canonical is https://prepmymeal.ch/products/prepmymeal-gutschein-ch. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://prepmymeal.ch/products/6er-meal-box-1-produkt, https://prepmymeal.ch/pages/bc-13-09, https://prepmymeal.ch/pages/blog-1, https://prepmymeal.ch/products/12er-meal-box-ch, https://prepmymeal.ch/products/ch-meal-box and https://prepmymeal.ch/products/6er-meal-box-ch and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Identifier 'doRatingSnippetReq' has already been declared”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 26 cookies, 3 of them by other companies (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 56 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.