Website review, no card needed

practiceplan.co.uk logo

practiceplan.co.uk website review

Visit site (opens in a new tab)Reviewed 24 October 202632 issues · 91 checks

This review found 32 issues worth fixing on practiceplan.co.uk, 7 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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.2 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
200 ms154 msMay 2Oct 17170 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026181 ms
May 9, 2026176 ms
May 16, 2026173 ms
May 23, 2026176 ms
May 30, 2026172 ms
Jun 6, 2026174 ms
Jun 13, 2026177 ms
Jun 20, 2026171 ms
Jun 27, 2026180 ms
Jul 4, 2026190 ms
Jul 11, 2026195 ms
Jul 18, 2026195 ms
Jul 25, 2026190 ms
Aug 1, 2026173 ms
Aug 8, 2026163 ms
Aug 15, 2026159 ms
Aug 22, 2026161 ms
Aug 29, 2026169 ms
Sep 5, 2026172 ms
Sep 12, 2026176 ms
Sep 19, 2026178 ms
Sep 26, 2026187 ms
Oct 3, 2026180 ms
Oct 10, 2026179 ms
Oct 17, 2026170 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 practiceplan.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix86
  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 86

    86/100

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

  • 8 third-party services on the page

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

  • Reduce unused JavaScript

    613 KiB

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

  • Improve image delivery

    514 KiB

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

  • Google Tag Manager adds 326 ms

    326 ms

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

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • Vimeo adds 37 ms

    37 ms

    Vimeo costs a phone 37 ms of main-thread work and 523 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.

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    113 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    19 KiB

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 933 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 12.3 s

    12.3 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are the UK's number one provider of practice-branded den…”.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s 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.4 s

    1.4 s

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

  • Real-user INP: 155 ms

    155 ms

    Real visitors wait 155 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 600 ms

    600 ms

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

  • Total Blocking Time: 145 ms

    145 ms

    Scripts block the page for only 145 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 74 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 74 requests on a phone: scripts 1.3 MB (22), images 1.1 MB (20) and fonts 59 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (109 KiB) 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.

  • About 0.7 g of CO₂ per visit

    0.73 g

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

2 checks passed
  • 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

6 to fixGoogle 8690
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

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

  • 7 links without text

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 9291
  • Structured data has 1 problem

    Structured data found (LocalBusiness, Organization, SiteNavigationElement and WebPage) but with 1 problem, for example “Organization: missing @context (expected "https://schema.org")”.

  • No social preview image

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

  • 1 link with vague text

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

  • 33 internal links, 11 external

    The homepage links to 33 pages on practiceplan.co.uk and 11 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “We're the UK's leading provider of practice-branded dental membership plans to help you leave NHS dentistry or switch p…”.

  • One H1 headline

    Your main headline reads: “Dental practice plans – the plan provider you can trust”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Leading Provider of Practice Branded Dental Plans | Practice Plan”.

  • Canonical URL set

    The canonical URL is https://www.practiceplan.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.practiceplan.co.uk/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, description and contact details; logo and sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (365 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix69
  • 2 linked pages hidden from search

    https://www.practiceplan.co.uk/slt-about-us and https://www.practiceplan.co.uk/website-terms-of-use are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.practiceplan.co.uk/financial-planning-for-dentists and https://www.practiceplan.co.uk/about all use the title “Dental Plan Administration Experts | Supporting Your Practice”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.practiceplan.co.uk/mediahub and https://www.practiceplan.co.uk/about/testimonials have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.practiceplan.co.uk/financial-planning-for-dentists and https://www.practiceplan.co.uk/about use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.practiceplan.co.uk/financial-planning-for-dentists, whose canonical is https://www.practiceplan.co.uk/wesleyan. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.practiceplan.co.uk/contact, https://www.practiceplan.co.uk/team, https://www.practiceplan.co.uk/mediahub, https://www.practiceplan.co.uk/groups/dental-groups and https://www.practiceplan.co.uk/slt-about-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5480
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187241917&tm=gtm002&Ver=2&mid=e26b84b7-984f-4108-a74a-c493a2811038&bo=1&sid=43ee41b0cf6111f1a1a7fd87705cb933&vid=43ee78e0cf6111f192bae77fa989971f&vids=1&msclkid=N&pi=9.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

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

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    37 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • 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 341 words of copy

    The homepage carries about 341 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 9 cookies set on arrival

    9

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

  • 20 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 practiceplan.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

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on practiceplan.co.uk, including 13 speed issues and 3 SEO issues. 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