Website review, no card needed

createfertility.co.uk logo

createfertility.co.uk website review

Visit site (opens in a new tab)Reviewed 26 October 202628 issues · 81 checks

This review found 28 issues worth fixing on createfertility.co.uk, 6 of them high impact, across 81 checks. The most urgent: 26 tap targets too small. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.1 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
114 ms99 msMay 9Oct 24111 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026112 ms
May 16, 2026109 ms
May 23, 2026109 ms
May 30, 2026110 ms
Jun 6, 2026111 ms
Jun 13, 2026111 ms
Jun 20, 2026112 ms
Jun 27, 2026110 ms
Jul 4, 2026111 ms
Jul 11, 2026112 ms
Jul 18, 2026111 ms
Jul 25, 2026111 ms
Aug 1, 2026109 ms
Aug 8, 2026107 ms
Aug 15, 2026106 ms
Aug 22, 2026109 ms
Aug 29, 2026109 ms
Sep 5, 2026107 ms
Sep 12, 2026104 ms
Sep 19, 2026101 ms
Sep 26, 2026102 ms
Oct 3, 2026103 ms
Oct 10, 2026104 ms
Oct 17, 2026109 ms
Oct 24, 2026111 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

Full-page screenshot of createfertility.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. createfertility.co.uk at 0.4 s0.4 s
  2. createfertility.co.uk at 0.8 s0.8 s
  3. createfertility.co.uk at 1.1 s1.1 s
  4. createfertility.co.uk at 1.5 s1.5 s
  5. createfertility.co.uk at 1.9 s1.9 s
  6. createfertility.co.uk at 2.3 s2.3 s
  7. createfertility.co.uk at 2.6 s2.6 s
  8. createfertility.co.uk at 3.0 s3.0 s

Speed

8 to fix74
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and VWO and others), adding 1.3 MB and 1.2 s of main-thread time.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    900 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Use efficient cache lifetimes

    450 ms · 287 KiB

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

  • Reduce unused JavaScript

    472 KiB

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

  • Google Tag Manager adds 361 ms

    361 ms

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

  • Main-thread work: 3.1 s

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

  • 1,766 HTML elements

    The page has 1,766 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 11 long tasks on the main thread

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

  • Improve image delivery

    13 KiB

    2 images could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    12 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 206 ms

    206 ms

    Your server sent the HTML in 206 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 18.4 s

    18.4 s

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

  • Total Blocking Time: 618 ms

    618 ms

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 80 ms

    80 ms

    Real visitors wait 80 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 348 ms

    348 ms

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

  • Largest content (LCP) got 23% faster for real visitors

    -23%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.036

    0.036

    The layout barely moves while loading (CLS 0.036, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 107 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 107 requests on a phone: scripts 1.4 MB (39), fonts 634 KiB (5) and images 144 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.66 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8793
  • 26 tap targets too small

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

  • 2 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 link without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 1)”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 259 internal links, 9 external

    The homepage links to 259 pages on createfertility.co.uk and 9 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Personalised fertility care from one of the UK’s leading IVF and Egg Freezing clinics, with expert treatment, tailored …”.

  • One H1 headline

    Your main headline reads: “A world of fertility expertise, centred around you”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Fertility Treatments & IVF Specialists UK | CREATE Fertility”.

  • Canonical URL set

    The canonical URL is https://www.createfertility.co.uk/.

  • 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://www.createfertility.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.createfertility.co.uk/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 (1,812 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.createfertility.co.uk/legal/promotional-conditions has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.createfertility.co.uk/appointments/calendar-new 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.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343144664&tm=gtm002&Ver=2&mid=da3d35f1-3cdc-4a74-b267-68a725cb1ce3&bo=2&sid=eef3b3b0d10511f187d1abab93aa913b&vid=eef3da30d10511f190b4af2668d2981f&vids=1&msclkid=N&pi=9.

  • 16 small tap targets

    16 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

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

  • No form on the homepage

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

  • 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 1,355 words of copy

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book appointment online >” and “Ts & Cs apply”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “Book appointment online >”, “Ts & Cs apply” and “Book now”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 of them by other companies (measured from a US location before any click).

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 createfertility.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on createfertility.co.uk, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25