Website review, no card needed

drfranks.co.uk logo

drfranks.co.uk website review

Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 69 checks

This review found 26 issues worth fixing on drfranks.co.uk, 8 of them high impact, across 69 checks. The most urgent: page weight: 15.8 MB in 33 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.1 s757 msJun 6Aug 29820 ms
Show as table
DateReal-visitor load time (LCP)
Jun 6, 2026870 ms
Jun 13, 2026849 ms
Jun 20, 2026881 ms
Jun 27, 2026939 ms
Jul 4, 2026969 ms
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 2026939 ms
Aug 1, 2026850 ms
Aug 8, 2026797 ms
Aug 29, 2026820 ms
Real-visitor tap response (INP)75th percentile, phones
113 ms102 msJun 13Aug 8112 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026103 ms
Jun 20, 2026104 ms
Jun 27, 2026105 ms
Jul 4, 2026110 ms
Jul 11, 2026110 ms
Jul 18, 2026108 ms
Jul 25, 2026104 ms
Aug 1, 2026110 ms
Aug 8, 2026112 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 drfranks.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drfranks.co.uk at 1.0 s1.0 s
  2. drfranks.co.uk at 1.9 s1.9 s
  3. drfranks.co.uk at 2.9 s2.9 s
  4. drfranks.co.uk at 3.9 s3.9 s
  5. drfranks.co.uk at 4.8 s4.8 s
  6. drfranks.co.uk at 5.8 s5.8 s
  7. drfranks.co.uk at 6.8 s6.8 s
  8. drfranks.co.uk at 7.8 s7.8 s

Speed

3 to fix100
  • Improve image delivery

    15.2 MB

    5 images could be 15.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    550 ms

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

  • Main-thread work: 2.3 s

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    21 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

2 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

1 to fix100
  • Time to Interactive: 44.9 s

    44.9 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

  • Not enough real-visitor data yet

    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.

5 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Step Into the Best Version of You”.

  • Speed Index: 1.0 s

    1.0 s

    Visually, the page fills in at 1.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

5 to fix18
  • Page weight: 15.8 MB in 33 requests

    15.8 MB

    Your homepage downloads 15.8 MB in 33 requests on a phone: images 15.6 MB (9), scripts 156 KiB (12) and fonts 27 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Seb.png weighs 14.7 MB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    13.9 MB

    3 images are downloaded at several times the size a phone draws them, for example Seb.png at 4,000 px wide, shown at 342 px. Resized copies would save about 13.9 MB.

  • 1 image in older formats

    1 image (14.7 MB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (14.7 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.5 g of CO₂ per visit

    4.47 g

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

Accessibility

6 to fixGoogle 8790
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 11 text elements with low contrast

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

  • 5 tap targets too small

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 form fields without a label

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail 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. (1 element).

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

7 to fixGoogle 8375
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (161 characters)

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://drfranks.co.uk/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at drfranks.co.uk/robots.txt, the first file search crawlers ask for.

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

  • 29 internal links, 3 external

    The homepage links to 29 pages on drfranks.co.uk and 3 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Step Into theBest Version of You”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Dr. Frank's — Weight Loss Treatments & Clinical Support”.

AI search readiness

1 to fix81
  • 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://drfranks.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.

1 checks passed
  • Text is in the HTML

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

Other pages

2 to fix90
  • 9 pages share a title

    /, https://drfranks.co.uk/help, https://drfranks.co.uk/pathways, https://drfranks.co.uk/affiliate, https://drfranks.co.uk/terms and https://drfranks.co.uk/privacy and 3 others all use the title “Dr. Frank's — Weight Loss Treatments & Clinical Support”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages share a meta description

    https://drfranks.co.uk/help, https://drfranks.co.uk/pathways, https://drfranks.co.uk/affiliate, https://drfranks.co.uk/terms, https://drfranks.co.uk/privacy and https://drfranks.co.uk/cookies and 2 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No analytics detected

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

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

    The homepage carries about 998 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 Appointments” and “Book Appointment”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Book Appointments”, “Book Appointment” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and “0k+ Patients”.

  • Direct contact links

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

Privacy and tracking

  • No consent tool detected

    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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 drfranks.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
Next.js
E-commerce
10 Shopify Products;Shopify;Shopify Plus
Hosting
Firebase Hosting

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on drfranks.co.uk, including 4 speed issues, 7 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