Website review, no card needed

fittaste.com logo

fittaste.com website review

Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 79 checks

This review found 24 issues worth fixing on fittaste.com, 7 of them high impact, across 79 checks. The most urgent: images must have alternative text (1 element). 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
2.1 s1.7 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
271 ms184 msMay 16Oct 31202 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026222 ms
May 23, 2026222 ms
May 30, 2026221 ms
Jun 6, 2026227 ms
Jun 13, 2026236 ms
Jun 20, 2026245 ms
Jun 27, 2026257 ms
Jul 4, 2026261 ms
Jul 11, 2026257 ms
Jul 18, 2026253 ms
Jul 25, 2026244 ms
Aug 1, 2026250 ms
Aug 8, 2026256 ms
Aug 15, 2026260 ms
Aug 22, 2026261 ms
Aug 29, 2026239 ms
Sep 5, 2026216 ms
Sep 12, 2026204 ms
Sep 19, 2026194 ms
Sep 26, 2026195 ms
Oct 3, 2026200 ms
Oct 10, 2026199 ms
Oct 17, 2026198 ms
Oct 24, 2026203 ms
Oct 31, 2026202 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 fittaste.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix67
  • Reduce unused JavaScript

    920 ms · 185 KiB

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

  • Mobile performance score: 67

    67/100

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

  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    150 ms · 335 KiB

    8 images could be 335 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 500 KiB and 298 ms of main-thread time.

  • Reduce unused CSS

    170 ms · 52 KiB

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

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    39 KiB

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 613 ms of it running JavaScript. That is comfortably low.

  • Server response: 28 ms

    28 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Frau sitzt mit einer Schale Rindergulasch und Reis auf dem …”.

  • Time to Interactive: 9.7 s

    9.7 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    -9%

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

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

    1.3 s

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

  • Real-user INP: 133 ms

    133 ms

    Real visitors wait 133 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.1 s

    1.1 s

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

  • Real-user TTFB: 276 ms

    276 ms

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

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

    -12%

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

  • Total Blocking Time: 92 ms

    92 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 164 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 164 requests on a phone: scripts 737 KiB (64), other files 652 KiB (75) and images 442 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

6 to fixGoogle 8591
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 1 text element with low contrast

    1 text element doesn'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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

Google 92100
  • 48 internal links, 3 external

    The homepage links to 48 pages on fittaste.com and 3 external pages.

8 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Proteinreiche Mahlzeiten im Glas: in 3 Minuten warm, lecker und alltagstauglich. Entdecke 140+ gesunde Fertiggerichte f…”.

  • One H1 headline

    Your main headline reads: “Montag Gulasch,Donnerstag Curry.”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Proteinreiche Mahlzeiten im Glas | In 3 Minuten fertig | FITTASTE”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList.

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

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

Other pages

4 to fix78
  • 2 pages share a title

    https://fittaste.com/pages/box-zusammenstellen and https://fittaste.com/pages/box1 all use the title “Box zusammenstellen – FITTASTE”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://fittaste.com/pages/box-zusammenstellen, https://fittaste.com/pages/gerichte, https://fittaste.com/pages/erfahrungen, https://fittaste.com/pages/box1 and https://fittaste.com/pages/fittaste-ueber-uns-team have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://fittaste.com/pages/box1, whose canonical is https://fittaste.com/pages/box-zusammenstellen. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://fittaste.com/pages/fittaste-ueber-uns-team has 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 21 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 736 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.

  • 20 cookies set on arrival

    20

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 fittaste.com, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Venon · sealsubscriptions.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 Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Trier

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on fittaste.com, including 8 speed issues and 2 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