Programmable

Website review, no card needed

prepmymeal.it logo

prepmymeal.it website review

Visit site (opens in a new tab)Reviewed 7 November 202627 issues · 72 checks

This review found 27 issues worth fixing on prepmymeal.it, 7 of them high impact, across 72 checks. The most urgent: 13 text elements with low contrast. 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

Site score

78C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.6 s2.4 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
175 ms123 msMay 16Oct 31162 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026129 ms
May 30, 2026129 ms
Jun 6, 2026135 ms
Jun 13, 2026136 ms
Jun 20, 2026134 ms
Jun 27, 2026131 ms
Jul 4, 2026131 ms
Jul 11, 2026131 ms
Jul 18, 2026134 ms
Jul 25, 2026136 ms
Aug 1, 2026135 ms
Aug 8, 2026136 ms
Aug 15, 2026137 ms
Aug 22, 2026140 ms
Aug 29, 2026146 ms
Sep 5, 2026155 ms
Sep 12, 2026165 ms
Sep 19, 2026169 ms
Sep 26, 2026168 ms
Oct 3, 2026167 ms
Oct 10, 2026166 ms
Oct 17, 2026163 ms
Oct 24, 2026162 ms
Oct 31, 2026162 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

prepmymeal.it (opens in a new tab)
Full-page screenshot of prepmymeal.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prepmymeal.it at 0.4 s0.4 s
  2. prepmymeal.it at 0.8 s0.8 s
  3. prepmymeal.it at 1.1 s1.1 s
  4. prepmymeal.it at 1.5 s1.5 s
  5. prepmymeal.it at 1.9 s1.9 s
  6. prepmymeal.it at 2.3 s2.3 s
  7. prepmymeal.it at 2.6 s2.6 s
  8. prepmymeal.it at 3.0 s3.0 s

Speed

5 to fix53

  • Improve image delivery

    150 ms · 915 KiB

    13 images could be 915 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 53

    53/100

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

  • Render-blocking requests

    950 ms

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

  • Use efficient cache lifetimes

    450 ms · 182 KiB

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

  • Main-thread work: 2.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (ablyft.com, Klaviyo and Shopify and others), adding 533 KiB and 362 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 47 KiB

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • 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: 7 ms

    7 ms

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

Core Web Vitals

7 to fix100

  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Oltre 300.000 clienti soddisfatti SEGUI UN'ALIMENTAZIONE SA…”.

  • Cumulative Layout Shift: 0.354

    0.354

    The layout shifts by 0.354 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 8.2 s

    8.2 s

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

  • Tap response (INP) got 26% slower for real visitors

    +26%

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Speed Index: 3.4 s

    3.4 s

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

  • 5 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

7 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: 1.7 s

    1.7 s

    Real visitors wait 1.7 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.2 s

    1.2 s

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

  • Real-user TTFB: 597 ms

    597 ms

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85

  • Page weight: 3.1 MB in 275 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 275 requests on a phone: images 1.3 MB (20), other files 939 KiB (146) and scripts 679 KiB (76). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9796

  • 13 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

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

2 checks passed

  • Every image has alt text

    All 70 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

5 to fixGoogle 9271

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (26 characters)

    Your title is only 26 characters: “Prepmymeal – prepmymeal-it”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “SEGUI UN'ALIMENTAZIONE SANA IN TUTTA SEMPLICITÀ”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://prepmymeal.it/sitemap.xml, so Google discovers your pages only by following links.

  • 48 internal links, 10 external

    The homepage links to 48 pages on prepmymeal.it and 10 external pages.

3 checks passed

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

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

AI search readiness

100

  • No llms.txt

    There is no https://prepmymeal.it/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.

3 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 (883 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90

  • 6 pages without a meta description

    https://prepmymeal.it/products/box-da-6-pasti-low-carb-cheto, https://prepmymeal.it/products/box-da-6-pasti-veggie-vegan, https://prepmymeal.it/products/box-da-6-pasti-senza-glutine, https://prepmymeal.it/products/box-da-6-pasti-paleo, https://prepmymeal.it/pages/b2b-homepage and https://prepmymeal.it/pages/come-funziona have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://prepmymeal.it/products/box-da-6-pasti-low-carb-cheto, https://prepmymeal.it/products/box-da-6-pasti-veggie-vegan, https://prepmymeal.it/products/box-da-6-pasti-senza-glutine, https://prepmymeal.it/products/box-da-6-pasti-paleo, https://prepmymeal.it/pages/b2b-homepage and https://prepmymeal.it/pages/come-funziona have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://prepmymeal.it/products/box-da-6-pasti-low-carb-cheto, https://prepmymeal.it/products/box-da-6-pasti-veggie-vegan, https://prepmymeal.it/products/box-da-6-pasti-senza-glutine, https://prepmymeal.it/products/box-da-6-pasti-paleo, https://prepmymeal.it/products/body-challenge and https://prepmymeal.it/pages/b2b-homepage and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed

  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 7 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 “Refused to apply style from 'https://prepmymeal.it/cdn/shop/t/30/assets/component-loading-overlay.css?v=3618' because i…”.

2 checks passed

  • Tap targets are thumb-sized

    11 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67

  • 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 analytics detected

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

  • 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 572 words of copy

    The homepage carries about 572 words of visible text.

3 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop” and “Shop now”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 94 testimonial or review blocks, a star rating and 6 trust badges.

Privacy and tracking

1 to fix

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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.it, 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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Mable · Essential A B Testing · Judge Me Reviews · Delivery Pickup · Orbe Geolocation · goaffpro.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on prepmymeal.it, including 12 speed issues, 5 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