SEO report for www.hellofresh.com
https://www.hellofresh.com/ · checked Wed, 11 Nov 2026 07:09 GMT
Fix these first
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- Title tagcritical
“HelloFresh® Meal Kits | Free Breakfast for Life + 10 Free Meals”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- H1 headingcritical
3 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- HTML sizemedium
565 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- Scripts & third partiesmedium
87 script tag(s); files loaded from 0 other domain(s).
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
32 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to hellofresh.com…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap index found at https://www.hellofresh.com/sitemap_index.xml listing 5 sitemaps.
Declared in robots.txt.
No lastmod dates – add accurate ones so search engines know what changed.
- ✓
Canonical URLhigh
Canonical: https://www.hellofresh.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://hellofresh.com/ → https://www.hellofresh.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
hellofresh.com redirects to www.hellofresh.com.
- ✓
hreflangmedium
22 hreflang link(s).
All language codes are valid.
Search snippet & sharing 79%
How the page looks in Google results and when shared.
- !
Title tagcritical
“HelloFresh® Meal Kits | Free Breakfast for Life + 10 Free Meals”
About 560px of Google's ~580px desktop width.
Repeated words: free.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✓
Meta descriptionhigh
153 characters, ~934px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-US"
Content quality 73%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,149 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- i
Readabilitymedium
Not enough paragraph text to score readability.
- ✓
Topic focushigh
5 of 6 title keywords appear in the main content (missing: breakfast).
- !
H1 headingcritical
3 H1 headings – one clear H1 is best practice.
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- ✓
Heading structuremedium
21 headings for 1149 words.
Levels are in order.
- ✗
Text-to-code ratiolow
2% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 56%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- !
Question-led contentmedium
1 heading(s) phrased as questions, e.g. “Not hungry yet?”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✓
Trust pages (E-E-A-T)medium
Links found to all three: about, contact and privacy.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): FAQPage, Question, Answer.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
83 internal and 7 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 54%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
45 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
565 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 0 stylesheet(s) in <head>.
- ✗
Scripts & third partiesmedium
87 script tag(s); files loaded from 0 other domain(s).
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
32 image(s).
5 without width/height – can cause layout shift (CLS).
1 image(s) after the first three aren't lazy-loaded.
20 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: public, max-age=14400
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 83%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=63072000
- ✗
Security headerslow
Present: nosniff.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✗
Server fingerprintlow
X-Powered-By reveals “Next.js”.
Fix: Remove X-Powered-By so attackers can't see your software versions.
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width
- ✓
Image alt textmedium
All 32 images have alt text.
- ✓
Form labelsmedium
All 1 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.