Website review, no card needed
enfamil.ca website review
Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 78 checks
This review found 28 issues worth fixing on enfamil.ca, 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
74C- #86,826 of 124,317 reviewed websitesbeats 26%
- #54,549 of 69,856 online storesbeats 18%
- #51,238 of 63,521 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 154 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 159 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 158 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 161 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
Reduce unused JavaScript
2.2 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Google Tag Manager adds 1.8 s
1.8 sGoogle Tag Manager costs a phone 1.8 s of main-thread work and 2.2 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
1.1 s · 818 KiB38 files are served with short cache lifetimes, so returning visitors download them again (818 KiB).
Signyfyd adds 1.0 s
1.0 sSignyfyd costs a phone 1.0 s of main-thread work and 282 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: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 5.5 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, Signyfyd and Optanon and others), adding 3.7 MB and 4.2 s of main-thread time.
Optanon adds 858 ms
858 msOptanon costs a phone 858 ms of main-thread work and 356 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 641 ms. During a long task the page ignores taps.
Improve image delivery
350 ms · 213 KiB4 images could be 213 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
2,292 HTML elements
The page has 2,292 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Facebook adds 150 ms
150 msFacebook costs a phone 150 ms of main-thread work and 296 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.
Legacy JavaScript
150 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Reduce unused CSS
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
30 KiB30 KiB could be saved by minifying JavaScript.
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: 6 ms
6 msYour server sent the HTML in 6 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.
Largest Contentful Paint: 14.2 s
14.2 sYour largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Sign up for up to $500 in full-sized product and coupons, e…”.
Time to Interactive: 40.5 s
40.5 sThe page becomes fully interactive after 40.5 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 154 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 464 ms
464 msReal visitors wait 464 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 394 requests
6.7 MBYour homepage downloads 6.7 MB in 394 requests on a phone: scripts 4.9 MB (169), other files 919 KiB (156) and images 293 KiB (29). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
91 KiB1 image is downloaded at several times the size a phone draws it, for example MJN_Web_Banner_Enfamil_Why_Choose_Desktop_EN_1.jpg at 1,708 px wide, shown at 370 px. Resized copies would save about 91 KiB.
1 image in older formats
1 image (52 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 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 227.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 56 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
220 internal links, 7 external
The homepage links to 220 pages on enfamil.ca and 7 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Sign up for up to $500 in full-sized product and coupons, exclusive discounts, and more!*”.
Title: 62 characters
Your title is a healthy 62 characters: “Baby Formulas from Infant to Toddler Years | Enfamil A+ Canada”.
Canonical URL set
The canonical URL is https://www.enfamil.ca/.
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.enfamil.ca/sitemap.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,163 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.enfamil.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://www.enfamil.ca/collections/toddler-formula and https://www.enfamil.ca/collections/allergy, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://www.enfamil.ca/policies/shipping-policy and https://www.enfamil.ca/blogs/help-centre have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://www.enfamil.ca/blogs/help-centre took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.
5 checks passed
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.
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 11 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'substring')”.
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.
About 761 words of copy
The homepage carries about 761 words of visible text.
6 checks passed
26 calls to action
The homepage has 26 calls to action, for example “Shop Products”, “Shop All Products” and “Start saving”.
7 short forms
7 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
33 cookies set on arrival
33Opening the homepage sets 33 cookies, 4 of them by other companies (measured from a US location before any click).
51 other companies contacted
Loading the homepage contacts 51 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.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Minmaxify Order Limits · Langshop · signifyd.com · esc-apps-cdn.com · useamp.com
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
- The footer still says © 1998.
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on enfamil.ca, including 19 speed issues, 2 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.