pathwaystofertility.com website review

About 670 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

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

4 images could be 506 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

6 third-party services load with your homepage (Squarespace, Google Tag Manager and sqspcdn.com and others), adding 2.6 MB and 781 ms of main-thread time.

About 123 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.

Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

Squarespace costs a phone 602 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.

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 906 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.

sqspcdn.com costs a phone 55 ms of main-thread work and 330 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.

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

6 long tasks block the main thread while loading, the longest for 191 ms. During a long task the page ignores taps.

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

3 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).

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.

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

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

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

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

1 image 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 2.6 MB in 70 requests on a phone: scripts 1.4 MB (42), images 904 KiB (6) and stylesheets 163 KiB (9). Under 2 MB keeps phones on slow connections fast.

unsplash-image-moMO7tq5jtc.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).

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “Pathways to Fertility”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6436e68a0763df732b9…”.

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 105 pages on pathwaystofertility.com and 0 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.

There is no https://www.pathwaystofertility.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.

https://www.pathwaystofertility.com/blog, https://www.pathwaystofertility.com/method, https://www.pathwaystofertility.com/locations, https://www.pathwaystofertility.com/treatment-timeline, https://www.pathwaystofertility.com/are-we-a-match and https://www.pathwaystofertility.com/investing-vs-spending and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pathwaystofertility.com/the-pathway, https://www.pathwaystofertility.com/method, https://www.pathwaystofertility.com/acupuncture-for-fertility, https://www.pathwaystofertility.com/locations, https://www.pathwaystofertility.com/chinese-herbs and https://www.pathwaystofertility.com/fertility-coaching and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/6436e68a0763df732b9d6f21/23/5c5a…”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage carries about 1,088 words of visible text.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 5 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.