Website review, no card needed
enfamil.com website review
Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 88 checks
This review found 35 issues worth fixing on enfamil.com, 14 of them high impact, across 88 checks. The most urgent: google Tag Manager adds 1.2 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
75C- #79,437 of 121,016 reviewed websitesbeats 30%
- #50,669 of 68,495 online storesbeats 22%
- #47,874 of 62,417 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 137 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 141 ms |
| Oct 31, 2026 | 143 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.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.1 s
Speed
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 721 KiB 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.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.4 s
A phone's processor spends 8.4 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Optanon and others), adding 2.9 MB and 2.6 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 860 ms
860 msGoogle CDN costs a phone 860 ms of main-thread work and 1.1 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.
Render-blocking requests
850 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 569 ms. During a long task the page ignores taps.
Optanon adds 279 ms
279 msOptanon costs a phone 279 ms of main-thread work and 254 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.
Use efficient cache lifetimes
251 KiB18 files are served with short cache lifetimes, so returning visitors download them again (251 KiB).
2,101 HTML elements
The page has 2,101 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
site.com adds 17 ms
17 mssite.com costs a phone 17 ms of main-thread work and 714 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
68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
26 KiB1 image could be 26 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 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.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.1 s
5.1 sReal visitors see the first content after 5.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.9 s
4.9 sReal visitors wait 4.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 25.0 s
25.0 sThe page becomes fully interactive after 25.0 s. Good is under 3.8 s.
Total Blocking Time: 2.9 s
2.9 sScripts block taps and scrolling for 2.9 s in total while the page loads. Good is under 200 ms.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Brainy with tub of Enfamil NeuroPro Infant and #1 Pediatric…”.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.069
0.069The layout barely moves while loading (CLS 0.069, good is under 0.1).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 5.0 MB in 147 requests
5.0 MBYour homepage downloads 5.0 MB in 147 requests on a phone: scripts 3.3 MB (68), other files 795 KiB (23) and fonts 285 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.41 g of CO₂e: 168.9 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
35 tap targets too small
35 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 180 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
25 links with vague text
25 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
121 internal links, 53 external
The homepage links to 121 pages on enfamil.com and 53 external pages.
8 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Discover tailored formulas to help meet your child’s nutritional needs. Pediatrician recommended for newborns, infants …”.
One H1 headline
Your main headline reads: “Find the Right Formula”.
Title: 53 characters
Your title is a healthy 53 characters: “Enfamil Newborn, Infant & Toddler Nutrition | Enfamil”.
Canonical URL set
The canonical URL is https://www.enfamil.com/.
Structured data in place
Structured data found: Organization.
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.enfamil.com/sitemap.xml.
AI search readiness
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (3,031 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.enfamil.com/llms.txt (12 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.enfamil.com/quality-assurance, whose canonical is https://www.enfamil.com/why-enfamil/quality-assurance. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
11 small tap targets
11 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=text&args[]= for the full message or use the non-m…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 3 trust badges. 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 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 1,971 words of copy
The homepage carries about 1,971 words of visible text.
5 checks passed
31 calls to action
The homepage has 31 calls to action, for example “Join Enfamil Family Beginnings”, “Join Now” and “Join Now to Start Earning”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
14 other companies contacted
Loading the homepage contacts 14 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 enfamil.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Next.js
- E-commerce
- Shopify
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on enfamil.com, including 21 speed issues, 1 SEO issue and 4 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.