Website review, no card needed
homechef.com website review
Visit site (opens in a new tab)Reviewed 11 October 202636 issues · 84 checks
This review found 36 issues worth fixing on homechef.com, 12 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Home Chef
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.6 s |
| Apr 25, 2026 | 2.6 s |
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 188 ms |
| Apr 25, 2026 | 192 ms |
| May 2, 2026 | 192 ms |
| May 9, 2026 | 184 ms |
| May 16, 2026 | 178 ms |
| May 23, 2026 | 175 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 175 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 178 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 176 ms |
| Aug 29, 2026 | 173 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 178 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
5.2 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.
Use efficient cache lifetimes
4.5 s · 1.6 MB101 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Render-blocking requests
4.5 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Optimizely and Yottaa and others), adding 1.0 MB and 595 ms of main-thread time.
Improve image delivery
300 ms · 389 KiB13 images could be 389 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
350 ms · 94 KiBPolyfills for old browsers add 94 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 234 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 13 KiB13 KiB could be saved by minifying JavaScript.
Font display
50 msWeb 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 62 but mobile only 28. 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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 10.4 s
10.4 sThe first text or image appears after 10.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.2 s
25.2 sYour largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Meet Home Chef Let’s cook together See Pricing & Meals Take…”.
Time to Interactive: 29.0 s
29.0 sThe page becomes fully interactive after 29.0 s. Good is under 3.8 s.
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 795 ms
795 msScripts block taps and scrolling for 795 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.193
0.193The layout shifts by 0.193 while loading, so content jumps under the reader's thumb. Good is under 0.1.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 188 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 452 ms
452 msReal visitors wait 452 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.5 MB in 203 requests
4.5 MBYour homepage downloads 4.5 MB in 203 requests on a phone: scripts 2.9 MB (67), images 1.1 MB (56) and fonts 342 KiB (5). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
86 KiB3 images are downloaded at several times the size a phone draws them, for example cook_and_enjoy-3971583bb4cf2ae218ccba3e83192fc824b61afa941cc at 1,084 px wide, shown at 250 px. Resized copies would save about 86 KiB.
10 images below the first screen load straight away
10 images further down the page (373 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.3 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
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Meal Delivery Service - Fresh Weekly Meal Kit Delivery - Home Chef”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
7 H1 headlines
There are 7 <h1> headlines (“Meet Home Chef”, “Explore The Menu” and “How It Works”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://www.homechef.com/sitemap.xml.gz, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
41 internal links, 13 external
The homepage links to 41 pages on homechef.com and 13 external pages.
4 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Our weekly deliveries of fresh, perfectly-portioned ingredients have everything you need to prepare home-cooked meals i…”.
Canonical URL set
The canonical URL is https://www.homechef.com/.
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.
AI search readiness
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.
No llms.txt
There is no https://www.homechef.com/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.
2 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,659 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.homechef.com/customize-it declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
7 pages share 3 titles
/ and https://www.homechef.com/customize-it all use the title “Meal Delivery Service - Fresh Weekly Meal Kit Delivery - Home Chef”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.homechef.com/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://www.homechef.com/accessibility, https://www.homechef.com/our-menu, https://www.homechef.com/our-menus/19-oct-2026/standard, https://www.homechef.com/customize-it, https://www.homechef.com/heroes and https://www.homechef.com/recipes and 1 other use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
4 broken images
4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=4010699&Ver=2&mid=5d528e43-520c-4db6-a758-2a07d383e05e&bo=1&sid=4895c310c5b811f1b7925fbbd6f5bfb1&vid=4895f610c5b811f192aea1d0a7529f73&vids=1&msclkid=N&pi=918639831&lg=.
5 small tap targets
5 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 1,501 words of copy
The homepage carries about 1,501 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Started” and “See Pricing & Meals”.
14 calls to action
The homepage has 14 calls to action, for example “Get Started”, “See Pricing & Meals” and “Start the Quiz”.
5 short forms
5 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Amplitude and Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Amplitude, Criteo, Google Ads, Google Tag Manager and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
40 cookies set on arrival
40Opening the homepage sets 40 cookies (measured from a US location before any click).
55 other companies contacted
Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 homechef.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager | Amplitude
Hiring
- Hiring
- 29 open roles
- Teams
- Warehouse (5), Production (4), Tempo Production (3), Field HR (2)
- Job board
- greenhouse
- Careers page
- www.homechef.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on homechef.com, including 15 speed issues, 5 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.