prenatalfit.com website review

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

13 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

About 426 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

8 third-party services load with your homepage (mindbodyonline.com, teamupstatic.com and Google Tag Manager and others), adding 20.9 MB and 1.3 s of main-thread time.

teamupstatic.com costs a phone 360 ms of main-thread work and 20.2 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.

20 long tasks block the main thread while loading, the longest for 1.6 s. During a long task the page ignores taps.

About 715 KiB of JavaScript is downloaded but never used on this page.

mindbodyonline.com costs a phone 362 ms of main-thread work and 262 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.

Google Tag Manager costs a phone 259 ms of main-thread work and 178 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.

225 KiB could be saved by minifying JavaScript.

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

31 KiB could be saved by minifying CSS.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

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.

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

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

The layout shifts by 0.185 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 25.9 MB in 203 requests on a phone: images 22.7 MB (46), scripts 1.5 MB (76) and fonts 825 KiB (18). Under 2 MB keeps phones on slow connections fast.

2 images weigh 981 KiB together. On a phone connection a single image that size takes seconds.

12 images (3.2 MB) 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.

9 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Untitled-design-20-ajay-59444.png at 1,406 px wide, shown at 370 px. Resized copies would save about 136 KiB.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

24 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.

1 link inside paragraphs relies on colour alone to stand out.

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 33 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 12 characters: “Prenatal FIT”. 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 Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.prenatalfit.com/wp-sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 66 pages on prenatalfit.com and 16 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.

Your homepage links to https://www.prenatalfit.com/events-workshops, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.prenatalfit.com/about-us, https://www.prenatalfit.com/instructors, https://www.prenatalfit.com/testimonials, https://www.prenatalfit.com/faq, https://www.prenatalfit.com/photos and https://www.prenatalfit.com/class-schedule and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.prenatalfit.com/instructors, https://www.prenatalfit.com/testimonials, https://www.prenatalfit.com/photos, https://www.prenatalfit.com/massage-appointments, https://www.prenatalfit.com/events-courses and https://www.prenatalfit.com/contact-us 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.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Class extends value undefined is not a constructor or null”.

Chrome logged issues while loading the page (“Cookie”).

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.

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 698 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Mixpanel (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 5 cookies, 2 of them by other companies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.