Website review, no card needed
heinz.com website review
Visit site (opens in a new tab)Reviewed 1 November 202636 issues · 86 checks
This review found 36 issues worth fixing on heinz.com, 13 of them high impact, across 86 checks. The most urgent: tiktokcdn-us.com adds 5.6 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 147 ms |
| May 16, 2026 | 149 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 157 ms |
| Jul 11, 2026 | 156 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 159 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 148 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 149 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
Speed
tiktokcdn-us.com adds 5.6 s
5.6 stiktokcdn-us.com costs a phone 5.6 s of main-thread work and 8.4 MB 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.
Use efficient cache lifetimes
2.5 s · 2.7 MB175 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).
Reduce unused JavaScript
1.4 s · 3.8 MBAbout 3.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 18.1 s
A phone's processor spends 18.1 s on main-thread work while loading, 13.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38. 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 (tiktokcdn-us.com, Google Tag Manager and Google CDN and others), adding 14.0 MB and 7.1 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 742 ms. During a long task the page ignores taps.
Google Tag Manager adds 537 ms
537 msGoogle Tag Manager costs a phone 537 ms of main-thread work and 517 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.
TikTok adds 171 ms
171 msTikTok costs a phone 171 ms of main-thread work and 3.6 MB 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.
Google CDN adds 360 ms
360 msGoogle CDN costs a phone 360 ms of main-thread work and 736 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
150 ms · 101 KiBAbout 101 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.
Render-blocking requests
250 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.
Legacy JavaScript
150 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 19.7 s
19.7 sVisually, the page fills in at 19.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 4.8 s
4.8 sScripts block taps and scrolling for 4.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 84.8 s
84.8 sThe page becomes fully interactive after 84.8 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 396 ms
396 msReal visitors wait 396 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.13
0.13For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 147 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, 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).
2 checks passed
Cumulative Layout Shift: 0.099
0.099The layout barely moves while loading (CLS 0.099, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 18.9 MB in 550 requests
18.9 MBYour homepage downloads 18.9 MB in 550 requests on a phone: scripts 9.6 MB (204), media 3.6 MB (12) and other files 2.4 MB (246). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (70 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 5.3 g of CO₂ per visit
5.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.35 g of CO₂e: 641.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
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
Every image has alt text
All 16 images in the HTML carry an alt attribute.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
26 internal links, 14 external
The homepage links to 26 pages on heinz.com and 14 external pages.
8 checks passed
Meta description: 86 characters
Your meta description is 86 characters: “Discover what’s new at Heinz®. New products, exciting flavors, great collabs and more.”.
One H1 headline
Your main headline reads: “HEINZ KETCHUP, MUSTARD, BEANZ & SAUCES”.
Title: 39 characters
Your title is a healthy 39 characters: “Heinz Official Site - Heinz® US | Heinz”.
Canonical URL set
The canonical URL is https://www.heinz.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://www.heinz.com/sitemap-index.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (359 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.heinz.com/llms.txt (76 KiB, 77 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://www.heinz.com/recipes/shepherd-s-pie-bowls, https://www.heinz.com/recipes/southwest-salad, https://www.heinz.com/recipes/turkey-tinga-tacos and https://www.heinz.com/recipes/sticky-thai-chili-air-fryer-wings use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://www.heinz.com/privacy-policy, https://www.heinz.com/sustainability, https://www.heinz.com/recipes and https://www.heinz.com/terms-of-use have 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 and read each the way a search engine does.
6 checks passed
Linked pages load
14 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.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
4 third-party cookies
4 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.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
18 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 297 words of copy
The homepage carries about 297 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Sign Up For Free”, “Join TasteVIP” and “Contact Us”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 3 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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
53 other companies contacted
Loading the homepage contacts 53 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 heinz.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
- Next.js
- Hosting
- Google Cloud
Company
- Founded
- 1869
- Headquarters
- Pittsburgh
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 heinz.com, including 20 speed issues, 1 SEO issue and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.