Website review, no card needed
momommy.com website review
Visit site (opens in a new tab)Reviewed 10 November 202644 issues · 87 checks
This review found 44 issues worth fixing on momommy.com, 16 of them high impact, across 87 checks. The most urgent: render-blocking 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
74C- #87,904 of 126,050 reviewed websitesbeats 26%
- #54,883 of 70,345 online storesbeats 18%
- #51,505 of 63,877 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 128 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 120 ms |
| Aug 1, 2026 | 112 ms |
| Aug 15, 2026 | 121 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 111 ms |
| Nov 7, 2026 | 114 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.0 s
2.0 s
3.0 s
4.0 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Render-blocking requests
1.3 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,777 HTML elements
The page has 5,777 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
750 ms · 1.1 MB40 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, quickcep.com and loox.io and others), adding 2.8 MB and 700 ms of main-thread time.
Use efficient cache lifetimes
808 KiB18 files are served with short cache lifetimes, so returning visitors download them again (808 KiB).
Reduce unused JavaScript
150 ms · 499 KiBAbout 499 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Shopify adds 230 ms
230 msShopify costs a phone 230 ms of main-thread work and 799 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.
loox.io adds 158 ms
158 msloox.io costs a phone 158 ms of main-thread work and 879 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.
quickcep.com adds 187 ms
187 msquickcep.com costs a phone 187 ms of main-thread work and 560 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.
cloudfront.net adds 123 ms
123 mscloudfront.net costs a phone 123 ms of main-thread work and 362 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 · 69 KiBAbout 69 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
Legacy JavaScript
83 KiBPolyfills for old browsers add 83 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 19 ms
19 msYour server sent the HTML in 19 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.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “momommy”.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.313
0.313The layout shifts by 0.313 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 93 ms
93 msReal visitors wait 93 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: 474 ms
474 msReal visitors wait 474 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 128 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 176 ms
176 msScripts block the page for only 176 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.7 MB in 321 requests
5.7 MBYour homepage downloads 5.7 MB in 321 requests on a phone: images 3.0 MB (93), scripts 1.3 MB (66) and other files 860 KiB (133). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
1_4_a11a5910-2ae8-45d0-ae12-129054f27542.png 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).
3 images far larger than shown
422 KiB3 images are downloaded at several times the size a phone draws them, for example 3_1.jpg at 2,048 px wide, shown at 292 px. Resized copies would save about 422 KiB.
3 images below the first screen load straight away
3 images further down the page (516 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (53 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.6 g of CO₂ per visit
1.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.62 g of CO₂e: 194.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements must only use permitted ARIA attributes (59 elements)
Elements must only use permitted ARIA attributes: 59 elements on the page fail this check, rated serious by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
autocomplete attribute must be used correctly (1 element)
autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
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.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
47 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: 47 passed and 7 failed. 5 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.
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Custom Embroidered Gifts for Every Occasion | Gifts for Mom and Dad – momommy”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
424 internal links, 1 external
The homepage links to 424 pages on momommy.com and 1 external page.
4 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Custom Embroidered Mama & Dad Sweatshirts, Hoodies, T-shirt, Hats. Shop for personalized Mother's Day and Father's Day …”.
Canonical URL set
The canonical URL is https://www.momommy.com/.
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.momommy.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.
No llms.txt
There is no https://www.momommy.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.
2 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 (6,858 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.momommy.com/collections/hot-sale, https://www.momommy.com/collections/christmas-gifts, https://www.momommy.com/collections/christmas-sweatshirt, https://www.momommy.com/collections/christmas-decoration and https://www.momommy.com/collections/for-mom have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.momommy.com/collections/hot-sale, https://www.momommy.com/collections/christmas-gifts, https://www.momommy.com/collections/christmas-sweatshirt, https://www.momommy.com/collections/christmas-decoration and https://www.momommy.com/collections/for-mom 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 113 found) and read each the way a search engine does.
5 checks passed
Linked pages load
6 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.
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 5 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.momommy.com/.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://dkov91l6wait7.cloudfront.net/intl-tel-input/intlTelInput.css' from origin 'https:/…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
42 of 44 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.
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 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,383 words of copy
The homepage carries about 1,383 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Register”, “CONTACT & INFO” and “Contact Us”.
6 short forms
6 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 436 testimonial or review blocks, 40 customer or partner logos, a star rating and 1 trust badge.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
28 other companies contacted
Loading the homepage contacts 28 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 momommy.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ymq Product Options · Parkour Facebook Pixel · Sa Variants · Stream Email Sms · Parkour Tiktok Pixel · loox.io · quickcep.com · cloudfront.net
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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on momommy.com, including 20 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.