Website review, no card needed
olddutchfoods.com website review
Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 78 checks
This review found 33 issues worth fixing on olddutchfoods.com, 15 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 86 ms |
| May 9, 2026 | 81 ms |
| May 16, 2026 | 77 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 76 ms |
| Jun 6, 2026 | 74 ms |
| Jun 13, 2026 | 75 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 72 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 75 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 74 ms |
| Aug 8, 2026 | 75 ms |
| Aug 15, 2026 | 74 ms |
| Aug 22, 2026 | 74 ms |
| Aug 29, 2026 | 75 ms |
| Sep 5, 2026 | 76 ms |
| Sep 12, 2026 | 77 ms |
| Sep 19, 2026 | 75 ms |
| Sep 26, 2026 | 77 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 78 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
1.6 s
3.3 s
4.9 s
6.5 s
8.1 s
9.8 s
11.4 s
13.0 s
Speed
Reduce unused JavaScript
3.3 s · 325 KiBAbout 325 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
1.5 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
250 ms · 3.4 MB8 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 895 KiB and 690 ms of main-thread time.
Google CDN adds 616 ms
616 msGoogle CDN costs a phone 616 ms of main-thread work and 734 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
280 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
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.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 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.
First Contentful Paint: 7.7 s
7.7 sThe first text or image appears after 7.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.4 s
17.4 sYour largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Old Dutch has come a long way since its humble beginnings a…”.
Time to Interactive: 18.2 s
18.2 sThe page becomes fully interactive after 18.2 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.229
0.229The layout shifts by 0.229 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 256 ms
256 msScripts block taps and scrolling for 256 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 86 ms to 78 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-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 85 ms
85 msReal visitors wait 85 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 5.3 MB in 66 requests
5.3 MBYour homepage downloads 5.3 MB in 66 requests on a phone: images 3.9 MB (22), scripts 801 KiB (20) and other files 351 KiB (3). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
3.5 MB6 images are downloaded at several times the size a phone draws them, for example 2026-Corp-Banner.sustainable-scaled.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 3.5 MB.
8 images in older formats
8 images (5.0 MB) are 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.
4 images below the first screen load straight away
4 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 178.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Old Dutch Foods”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
24 internal links, 9 external
The homepage links to 24 pages on olddutchfoods.com and 9 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Old DutchFamily of Brands - Celebrating 90 Years!”.
Canonical URL set
The canonical URL is https://olddutchfoods.com/.
Structured data in place
Structured data found: LocalBusiness.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://olddutchfoods.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://olddutchfoods.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (407 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://olddutchfoods.com/brand/old-dutch-foods, https://olddutchfoods.com/brand/barrel-o-fun, https://olddutchfoods.com/brand/humpty-dumpty, https://olddutchfoods.com/community, https://olddutchfoods.com/recipes and https://olddutchfoods.com/quality-grows-here and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://olddutchfoods.com/privacy-policy has no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 382 words of copy
The homepage carries about 382 words of visible text.
7 checks passed
1 call to action
The homepage has 1 call to action, for example “Click Here to Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 olddutchfoods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2020.
Stack
- CMS
- WordPress
- Framework
- jQuery
Company
- Founded
- 1934
- Headquarters
- Roseville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on olddutchfoods.com, including 16 speed issues, 3 SEO issues and 3 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.