themom.co website review

94 files are served with short cache lifetimes, so returning visitors download them again (7.9 MB).

About 5.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 20.8 s faster on a phone.

About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.8 s faster on a phone.

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.6 s.

8 images could be 523 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.

208 KiB could be saved by minifying JavaScript.

203 KiB could be saved by minifying CSS.

Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.3 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 3.3 MB and 2.1 s of main-thread time.

Google CDN costs a phone 759 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.

Google Tag Manager costs a phone 779 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.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

Facebook costs a phone 364 ms of main-thread work and 453 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 block the main thread while loading, the longest for 314 ms. During a long task the page ignores taps.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

The first text or image appears after 32.5 s on a phone. Good is under 1.8 s.

Your largest element takes 54.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “moms celebrating the launch of MomCo with confetti”.

Visually, the page fills in at 32.5 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 67.2 s. Good is under 3.8 s.

Scripts block taps and scrolling for 645 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 885 ms for your server to start answering (75th percentile). Good is under 800 ms.

9 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.2 MB in 182 requests on a phone: scripts 7.0 MB (77), stylesheets 2.0 MB (31) and images 1.7 MB (24). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 3.47 g of CO₂e: 416.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

Your title is only 16 characters: “Home | The MomCo”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 197 characters; Google truncates after about 160, so the end of your pitch is cut.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 36 pages on themom.co and 14 external pages.

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.

https://www.themom.co/home and https://www.themom.co/index all use the title “Home | The MomCo”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.themom.co/my-profile, https://www.themom.co/donate, https://www.themom.co/charter-my-group, https://www.themom.co/contact, https://www.themom.co/podcast-network and https://www.themom.co/advertise and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.themom.co/my-profile has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.themom.co/my-profile, https://www.themom.co/find-a-meetup, https://www.themom.co/charter-my-group and https://www.themom.co/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.themom.co/articles, https://www.themom.co/index and https://www.themom.co/start-a-meetup took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "auto".”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 993 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

Opening the homepage sets 11 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.