prideivf.org website review

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

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

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

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

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

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

37 KiB could be saved by minifying CSS.

1 image could be 203 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

22 KiB could be saved by minifying JavaScript.

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

6 third-party services load with your homepage (Google Tag Manager, elfsight.com and Google/Doubleclick Ads and others), adding 326 KiB and 66 ms of main-thread time.

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 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (4.7 s).

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

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

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

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

2 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 39 requests on a phone: images 2.4 MB (12), scripts 579 KiB (6) and fonts 491 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

3 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

16 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 26 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 3 <h1> headlines (“Your Path to Starts Here”, “Whatever yourconcern” and “Begin Your Journey to Parenthood with Pride IVF”). One clear main headline is easier for people and search engines.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected double-quoted property name in JSON at position 199)”.

No XML sitemap at https://prideivf.org/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at prideivf.org/robots.txt, the first file search crawlers ask for.

11 links have no real href, so search engines can't follow them.

The homepage links to 31 pages on prideivf.org and 3 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://prideivf.org/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://prideivf.org/aboutus, https://prideivf.org/conventional-IVF, https://prideivf.org/natural-cycle-IVF, https://prideivf.org/minimal-stimulation-IVF, https://prideivf.org/hormonal-testing and https://prideivf.org/thyroid-dysfunction-management and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://prideivf.org/conventional-IVF, https://prideivf.org/natural-cycle-IVF, https://prideivf.org/minimal-stimulation-IVF, https://prideivf.org/hormonal-testing, https://prideivf.org/thyroid-dysfunction-management and https://prideivf.org/egg-freezing and 1 other all use the title “Book An Appointments”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://prideivf.org/aboutus, https://prideivf.org/conventional-IVF, https://prideivf.org/natural-cycle-IVF, https://prideivf.org/minimal-stimulation-IVF, https://prideivf.org/hormonal-testing and https://prideivf.org/thyroid-dysfunction-management and 9 others use the same meta description. A description written for each page earns more clicks.

https://prideivf.org/conventional-IVF, https://prideivf.org/natural-cycle-IVF, https://prideivf.org/minimal-stimulation-IVF, https://prideivf.org/hormonal-testing, https://prideivf.org/thyroid-dysfunction-management and https://prideivf.org/egg-freezing and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://prideivf.org/book-an-appointments has 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 15 pages linked from your homepage and read each the way a search engine does.

10 images failed to load on a phone, for example https://prideivf.org/images/loading.gif.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

Large scripts ship without source maps.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

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 1,612 words of visible text.

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

Opening the homepage sets 4 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.