Website review, no card needed

prepmymeal.at logo

prepmymeal.at website review

Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 81 checks

This review found 38 issues worth fixing on prepmymeal.at, 16 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.1 s1.7 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.8 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.5 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Jul 4, 20263.1 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.5 s
Aug 22, 20262.3 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
277 ms147 msMay 16Oct 31165 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026217 ms
May 23, 2026220 ms
May 30, 2026220 ms
Jun 6, 2026222 ms
Jun 13, 2026220 ms
Jun 20, 2026221 ms
Jun 27, 2026225 ms
Jul 4, 2026243 ms
Jul 11, 2026258 ms
Jul 18, 2026262 ms
Jul 25, 2026256 ms
Aug 1, 2026242 ms
Aug 8, 2026236 ms
Aug 15, 2026216 ms
Aug 22, 2026197 ms
Aug 29, 2026185 ms
Sep 5, 2026175 ms
Sep 12, 2026170 ms
Sep 19, 2026170 ms
Sep 26, 2026165 ms
Oct 3, 2026162 ms
Oct 10, 2026162 ms
Oct 17, 2026163 ms
Oct 24, 2026168 ms
Oct 31, 2026165 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of prepmymeal.at (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prepmymeal.at at 1.0 s1.0 s
  2. prepmymeal.at at 2.1 s2.1 s
  3. prepmymeal.at at 3.1 s3.1 s
  4. prepmymeal.at at 4.1 s4.1 s
  5. prepmymeal.at at 5.1 s5.1 s
  6. prepmymeal.at at 6.2 s6.2 s
  7. prepmymeal.at at 7.2 s7.2 s
  8. prepmymeal.at at 8.2 s8.2 s

Speed

16 to fix45
  • Reduce unused JavaScript

    5.6 s · 1.0 MB

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

  • Use efficient cache lifetimes

    5.2 s · 1.1 MB

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

  • Render-blocking requests

    2.3 s

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

  • Main-thread work: 15.9 s

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

  • Mobile performance score: 45

    45/100

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

  • 3,334 HTML elements

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

  • Improve image delivery

    2.4 MB

    34 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

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

  • Legacy JavaScript

    450 ms · 80 KiB

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

  • Reduce unused CSS

    450 ms · 26 KiB

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

  • Shopify adds 295 ms

    295 ms

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

  • 11 long tasks on the main thread

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

  • Bold Commerce adds 251 ms

    251 ms

    Bold Commerce costs a phone 251 ms of main-thread work and 485 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 adds 148 ms

    148 ms

    ablyft.com costs a phone 148 ms of main-thread work and 771 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 adds 140 ms

    140 ms

    Reviews.io costs a phone 140 ms of main-thread work and 295 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 adds 134 ms

    134 ms

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

  • Font display

    150 ms

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 30.8 s

    30.8 s

    Your largest element takes 30.8 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?”.

  • Time to Interactive: 31.5 s

    31.5 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 453 ms

    453 ms

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 120 ms

    120 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 643 ms

    643 ms

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

  • Tap response (INP) got 24% faster for real visitors

    -24%

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

  • Largest content (LCP) got 47% faster for real visitors

    -47%

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

  • Cumulative Layout Shift: 0.055

    0.055

    The layout barely moves while loading (CLS 0.055, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 8.4 MB in 535 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 535 requests on a phone: images 3.9 MB (82), scripts 2.5 MB (111) and other files 1.4 MB (269). Under 2 MB keeps phones on slow connections fast.

  • 11 images below the first screen load straight away

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

  • 4 images far larger than shown

    99 KiB

    4 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 99 KiB.

  • About 2.4 g of CO₂ per visit

    2.39 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9096
  • 11 text elements with low contrast

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

  • 1 image without alt text

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

  • All page content should be contained by landmarks (1 element)

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

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Meta description is long (255 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 44 internal links, 20 external

    The homepage links to 44 pages on prepmymeal.at and 20 external pages.

6 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Leckere High Protein Gerichte - Geliefert zu dir! – prepmymeal”.

  • Canonical URL set

    The canonical URL is https://prepmymeal.at/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://prepmymeal.at/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,816 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://prepmymeal.at/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix64
  • 1 linked page is broken

    Your homepage links to https://prepmymeal.at/null, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

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

  • 3 pages share a meta description

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

  • 8 pages without an H1

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

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    17 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,152 words of copy

    The homepage carries about 1,152 words of visible text.

3 checks passed
  • 15 short forms

    15 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks, 5 customer or partner logos, a star rating and 23 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    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.

  • 24 cookies set on arrival

    24

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

  • No consent tool detected

    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.

  • 59 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at prepmymeal.at, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Mable · Weglot Translate Your Store · Delivery Pickup · Instant Ai Page Builder · Pixoo Taboola Pixel · Klaviyo Email Marketing · Orbe Geolocation · Reviews Co Uk Product And Merchant Review Collection · Sovendus App Prepmymeal · goaffpro.com · rechargecdn.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on prepmymeal.at, including 21 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25