Website review, no card needed
ezpzfun.com website review
Visit site (opens in a new tab)Reviewed 5 November 202643 issues · 88 checks
This review found 43 issues worth fixing on ezpzfun.com, 14 of them high impact, across 88 checks. The most urgent: page weight: 57.4 MB in 326 requests. 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
64D- #113,172 of 120,386 reviewed websitesbeats 5%
- #66,278 of 68,161 online storesbeats 2%
- #60,727 of 62,115 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 281 ms |
| May 23, 2026 | 300 ms |
| May 30, 2026 | 300 ms |
| Jun 6, 2026 | 303 ms |
| Jun 13, 2026 | 306 ms |
| Jun 20, 2026 | 304 ms |
| Jun 27, 2026 | 302 ms |
| Jul 4, 2026 | 299 ms |
| Jul 11, 2026 | 289 ms |
| Jul 18, 2026 | 290 ms |
| Jul 25, 2026 | 288 ms |
| Aug 1, 2026 | 275 ms |
| Aug 8, 2026 | 283 ms |
| Aug 15, 2026 | 278 ms |
| Aug 22, 2026 | 282 ms |
| Aug 29, 2026 | 287 ms |
| Sep 5, 2026 | 282 ms |
| Sep 12, 2026 | 276 ms |
| Sep 19, 2026 | 243 ms |
| Sep 26, 2026 | 224 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 203 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 187 ms |
| Oct 31, 2026 | 187 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
1.3 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Main-thread work: 10.3 s
A phone's processor spends 10.3 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 15
15/100Your mobile performance score is 15. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,563 HTML elements
The page has 7,563 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (alia-prod.com, Yotpo and negate.io and others), adding 54.0 MB and 2.2 s of main-thread time.
Shopify adds 252 ms
252 msShopify costs a phone 252 ms of main-thread work and 52.5 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.
Use efficient cache lifetimes
900 ms · 938 KiB48 files are served with short cache lifetimes, so returning visitors download them again (938 KiB).
Render-blocking requests
700 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
alia-prod.com adds 568 ms
568 msalia-prod.com costs a phone 568 ms of main-thread work and 266 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.
Yotpo adds 364 ms
364 msYotpo costs a phone 364 ms of main-thread work and 394 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.
negate.io adds 317 ms
317 msnegate.io costs a phone 317 ms of main-thread work and 40 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.
gotolstoy.com adds 284 ms
284 msgotolstoy.com costs a phone 284 ms of main-thread work and 187 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 276 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 97 KiBPolyfills for old browsers add 97 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 61 KiBAbout 61 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.
Improve image delivery
77 KiB8 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
39 KiB39 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.
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: 21 ms
21 msYour server sent the HTML in 21 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 CLS: 0.79
0.79For real visitors the layout shifts by 0.79 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.8 s
26.8 sThe page becomes fully interactive after 26.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.721
0.721The layout shifts by 0.721 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Real-user TTFB: 531 ms
531 msReal visitors wait 531 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 281 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 57.4 MB in 326 requests
57.4 MBYour homepage downloads 57.4 MB in 326 requests on a phone: media 52.0 MB (5), scripts 2.6 MB (110) and images 1.6 MB (66). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
ezpz-slideshow-mobile-mothers-day.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 16.3 g of CO₂ per visit
16.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 16.28 g of CO₂e: 1953.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 273 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (297 characters)
Your meta description is 297 characters; Google truncates after about 160, so the end of your pitch is cut.
13 links with vague text
13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
882 internal links, 12 external
The homepage links to 882 pages on ezpzfun.com and 12 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Expert-Designed Baby and Toddler Feeding Products | ezpz”.
Canonical URL set
The canonical URL is https://ezpzfun.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.
XML sitemap found
Your XML sitemap is reachable at https://ezpzfun.com/sitemap.xml.
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,938 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ezpzfun.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://ezpzfun.com/collections/kits-sets-bundles has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://ezpzfun.com/pages/kits, https://ezpzfun.com/pages/rewards, https://ezpzfun.com/pages/intro-to-first-foods, https://ezpzfun.com/products/kit-1-prepare-for-starting-solids, https://ezpzfun.com/products/kit-2-learn-to-eat-and-drink and https://ezpzfun.com/products/kit-3-practice-feeding-skills and 9 others 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 (of 88 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 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 15 pages that loaded have a <title>.
Best practices
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.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'setProperty')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
17 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 248 words
The homepage has only about 248 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join to earn reward points!”.
13 calls to action
The homepage has 13 calls to action, for example “Shop by Product”, “Shop All” and “Shop by Age”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Hotjar.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
35 cookies set on arrival
35Opening the homepage sets 35 cookies (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.
75 other companies contacted
Loading the homepage contacts 75 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ezpzfun.com, 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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Redo · Yotpo Loyalty Rewards · Dr Stacked Discounts · Superfiliate · Gorgias Live Chat Helpdesk · Triplewhale · Tolstoy · Eg Auto Add To Cart · Easylocation · Page Speed Optimizer · Veeper Stop Coupon Leaks · privy.com · 506.io · mailchimp.com · chimpstatic.com · cloudfront.net · bundlepayments.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
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Parker
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on ezpzfun.com, including 22 speed issues, 4 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.