Website review, no card needed

yfood.com logo

yfood.com website review

Visit site (opens in a new tab)Reviewed 28 October 202644 issues · 90 checks

This review found 44 issues worth fixing on yfood.com, 17 of them high impact, across 90 checks. The most urgent: main-thread work: 28.8 s. 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
1.8 s1.5 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
262 ms199 msMay 9Oct 24242 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026206 ms
May 16, 2026209 ms
May 23, 2026210 ms
May 30, 2026213 ms
Jun 6, 2026216 ms
Jun 13, 2026219 ms
Jun 20, 2026221 ms
Jun 27, 2026222 ms
Jul 4, 2026226 ms
Jul 11, 2026228 ms
Jul 18, 2026228 ms
Jul 25, 2026230 ms
Aug 1, 2026236 ms
Aug 8, 2026244 ms
Aug 15, 2026253 ms
Aug 22, 2026246 ms
Aug 29, 2026244 ms
Sep 5, 2026250 ms
Sep 12, 2026254 ms
Sep 19, 2026255 ms
Sep 26, 2026255 ms
Oct 3, 2026246 ms
Oct 10, 2026237 ms
Oct 17, 2026242 ms
Oct 24, 2026242 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 yfood.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yfood.com at 2.6 s2.6 s
  2. yfood.com at 5.2 s5.2 s
  3. yfood.com at 7.8 s7.8 s
  4. yfood.com at 10.4 s10.4 s
  5. yfood.com at 13.0 s13.0 s
  6. yfood.com at 15.6 s15.6 s
  7. yfood.com at 18.2 s18.2 s
  8. yfood.com at 20.8 s20.8 s

Speed

14 to fix30
  • Main-thread work: 28.8 s

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

  • Improve image delivery

    1.1 s · 228 KiB

    8 images could be 228 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 182 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 30

    30/100

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

  • 5,875 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Talkable and Shopify and others), adding 1.0 MB and 2.9 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

  • Render-blocking requests

    550 ms

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

  • Talkable adds 526 ms

    526 ms

    Talkable costs a phone 526 ms of main-thread work and 205 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.

  • Reduce unused CSS

    450 ms · 80 KiB

    About 80 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 364 ms

    364 ms

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

  • rechargecdn.com adds 348 ms

    348 ms

    rechargecdn.com costs a phone 348 ms of main-thread work and 127 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.

  • Trust Pilot adds 250 ms

    250 ms

    Trust Pilot costs a phone 250 ms of main-thread work and 72 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.

  • Use efficient cache lifetimes

    252 KiB

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

  • Reduce unused JavaScript

    236 KiB

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

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 30. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 11.6 s

    11.6 s

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

  • Total Blocking Time: 7.1 s

    7.1 s

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

  • Time to Interactive: 26.6 s

    26.6 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • Real-user INP: 302 ms

    302 ms

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

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

  • 13 images without width and height

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

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

    +17%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • 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.4 s

    1.4 s

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

  • Real-user TTFB: 478 ms

    478 ms

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

  • Cumulative Layout Shift: 0.071

    0.071

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

Images and page weight

3 to fix53
  • Page weight: 4.9 MB in 355 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 355 requests on a phone: images 2.3 MB (51), scripts 1.2 MB (168) and other files 626 KiB (97). Under 2 MB keeps phones on slow connections fast.

  • 16 images below the first screen load straight away

    16 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 16 images far larger than shown

    73 KiB

    16 images are downloaded at several times the size a phone draws them, for example PRODUCT_RTD_classic_Batman_Raspberry_highlight_shadow-on_dro at 720 px wide, shown at 234 px. Resized copies would save about 73 KiB.

  • About 1.4 g of CO₂ per visit

    1.39 g

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

4 to fixGoogle 9395
  • 3 text elements with low contrast

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

  • 31 form fields without a label

    31 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 29 links without text

    29 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 55 automated accessibility rules passed

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

SEO

4 to fixGoogle 9281
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “yfood - Bewusste Ernährung. Immer und überall mit yfood. – yfood Labs”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“yfood Labs” and “Das Ende ist nah. Für deinen Hunger.”). One clear main headline is easier for people and search engines.

  • Structured data has 2 problems

    Structured data found ((untyped) and Organization) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

  • No social preview image

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

  • 156 internal links, 5 external

    The homepage links to 156 pages on yfood.com and 5 external pages.

4 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Keine Zeit zum Essen? yfood hilft. Trinkmahlzeiten, Riegel & Pulver, die satt machen. ✓essentielle Vitamine & Nährstoff…”.

  • Canonical URL set

    The canonical URL is https://yfood.com/.

  • 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://yfood.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://yfood.com/collections/all, https://yfood.com/collections/trinkmahlzeit-pulver, https://yfood.com/collections/riegel, https://yfood.com/collections/subscription-products, https://yfood.com/collections/halloween-edition and https://yfood.com/products/drink-classic-choco-de and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5480
  • 2 broken images

    2 images failed to load on a phone, for example https://yfood.com/.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    58 of 60 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 507 words of visible text.

1 checks passed
  • 35 short forms

    35 short forms (2 fields at most) are right on the homepage.

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 TikTok Pixel (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.

  • 12 cookies set on arrival

    12

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 yfood.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Company

Employees
480
Headquarters
Munich

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on yfood.com, including 22 speed issues, 4 SEO issues and 5 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