Website review, no card needed
mommy-diary.com website review
Visit site (opens in a new tab)Reviewed 11 November 202651 issues · 92 checks
This review found 51 issues worth fixing on mommy-diary.com, 23 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.5 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 5.1 s |
| Oct 24, 2026 | 5.0 s |
| Oct 31, 2026 | 5.0 s |
| Nov 7, 2026 | 4.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 121 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 108 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 114 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 117 ms |
| Oct 31, 2026 | 113 ms |
| Nov 7, 2026 | 108 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
1.9 s
2.9 s
3.9 s
4.9 s
5.8 s
6.8 s
7.8 s
Speed
Use efficient cache lifetimes
4.1 s · 7.7 MB63 files are served with short cache lifetimes, so returning visitors download them again (7.7 MB).
Render-blocking requests
3.9 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.
Reduce unused JavaScript
2.1 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
3.3 MB9 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, consentmanager.net and flodesk.com and others), adding 2.7 MB and 1.1 s of main-thread time.
Google Tag Manager adds 558 ms
558 msGoogle Tag Manager costs a phone 558 ms of main-thread work and 676 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.
flodesk.com adds 194 ms
194 msflodesk.com costs a phone 194 ms of main-thread work and 1.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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
250 ms · 96 KiBPolyfills for old browsers add 96 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
8 KiB8 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: 26 ms
26 msYour server sent the HTML in 26 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.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.40
0.40For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.
Real-user FCP: 4.8 s
4.8 sReal visitors see the first content after 4.8 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 17.3 s
17.3 sYour largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 33.2 s
33.2 sThe page becomes fully interactive after 33.2 s. Good is under 3.8 s.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.261
0.261The layout shifts by 0.261 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 377 ms
377 msScripts block taps and scrolling for 377 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 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-11-07, real Chrome visitors' tap response (inp) went from 121 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.6 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 10.4 MB in 127 requests
10.4 MBYour homepage downloads 10.4 MB in 127 requests on a phone: images 6.4 MB (19), scripts 2.0 MB (66) and fonts 1.4 MB (10). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (808 KiB) 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.
2 images far larger than shown
349 KiB2 images are downloaded at several times the size a phone draws them, for example logo-1200x746.png at 1,200 px wide, shown at 120 px. Resized copies would save about 349 KiB.
About 3.0 g of CO₂ per visit
2.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.95 g of CO₂e: 354.4 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
ARIA input fields must have an accessible name (4 elements)
ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
Frames without titles
4 frames have no title, so screen-reader users cannot tell what they contain.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (1 element).
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 11 failed. 4 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 short (20 characters)
Your title is only 20 characters: “Home | Mommy Diary ®”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (165 characters)
Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
127 internal links, 41 external
The homepage links to 127 pages on mommy-diary.com and 41 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://mommy-diary.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage 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://mommy-diary.com/sitemap_index.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://mommy-diary.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 (668 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages share a title
https://mommy-diary.com/motherhood, https://mommy-diary.com/motherhood/baby, https://mommy-diary.com/motherhood/family, https://mommy-diary.com/motherhood/kids, https://mommy-diary.com/motherhood/postpartum and https://mommy-diary.com/motherhood/pregnancy and 6 others all use the title “| Mommy Diary ®”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://mommy-diary.com/motherhood, https://mommy-diary.com/motherhood/baby, https://mommy-diary.com/motherhood/family, https://mommy-diary.com/motherhood/kids, https://mommy-diary.com/motherhood/pregnancy and https://mommy-diary.com/motherhood/special-needs and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 65 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.
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
2 broken images
2 images failed to load on a phone, for example http://0.0.0.1/.
31 third-party cookies
31 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
22 small tap targets
22 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
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.
Thin social proof
Social proof on the homepage: 1 trust badge. 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.
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 612 words of copy
The homepage carries about 612 words of visible text.
3 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Shop”, “Shop Now” and “shop all”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
18 other companies contacted
Loading the homepage contacts 18 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 mommy-diary.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 © 2013.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on mommy-diary.com, including 21 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.