Website review, no card needed

capita.co.uk logo

capita.co.uk website review

Visit site (opens in a new tab)Reviewed 18 October 202648 issues · 75 checks

This review found 48 issues worth fixing on capita.co.uk, 14 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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.7 s1.3 sApr 25Oct 101.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.4 s
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
260 ms214 msApr 25Oct 10252 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026228 ms
May 2, 2026230 ms
May 9, 2026231 ms
May 16, 2026220 ms
May 23, 2026220 ms
May 30, 2026226 ms
Jun 6, 2026234 ms
Jun 13, 2026244 ms
Jun 20, 2026249 ms
Jun 27, 2026255 ms
Jul 4, 2026249 ms
Jul 11, 2026219 ms
Jul 18, 2026220 ms
Jul 25, 2026220 ms
Aug 1, 2026222 ms
Aug 8, 2026248 ms
Aug 15, 2026241 ms
Aug 22, 2026236 ms
Aug 29, 2026236 ms
Sep 5, 2026235 ms
Sep 12, 2026236 ms
Sep 19, 2026236 ms
Sep 26, 2026238 ms
Oct 3, 2026244 ms
Oct 10, 2026252 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 capita.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix58
  • Use efficient cache lifetimes

    2.3 s · 571 KiB

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

  • Reduce unused JavaScript

    1.4 s · 469 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Wistia, Google Tag Manager and Civic and others), adding 2.9 MB and 985 ms of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Wistia adds 489 ms

    489 ms

    Wistia costs a phone 489 ms of main-thread work and 2.4 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.

  • Improve image delivery

    300 ms · 99 KiB

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

  • Google Tag Manager adds 349 ms

    349 ms

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

  • Font display

    350 ms

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

  • Main-thread work: 2.7 s

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

  • 1,556 HTML elements

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

  • 6 long tasks on the main thread

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

  • Render-blocking requests

    200 ms

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

  • Reduce unused CSS

    150 ms · 11 KiB

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

  • Legacy JavaScript

    38 KiB

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

    Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Why Capita We're an AI-enabled business services partner, t…”.

  • Time to Interactive: 13.2 s

    13.2 s

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

  • Real-user INP: 259 ms

    259 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

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

  • Total Blocking Time: 435 ms

    435 ms

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

  • 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

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • 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 TTFB: 710 ms

    710 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.6 MB in 45 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 45 requests on a phone: scripts 1.1 MB (23), other files 979 KiB (3) and media 962 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    87 KiB

    1 image is downloaded at several times the size a phone draws it, for example reciteme_button.png at 730 px wide, shown at 40 px. Resized copies would save about 87 KiB.

  • 1 image in older formats

    1 image (89 KiB) 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.

  • About 1.0 g of CO₂ per visit

    1.02 g

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

1 checks passed
  • Images load when needed

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

Accessibility

9 to fixGoogle 9990
  • Interactive controls must not be nested (10 elements)

    Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.

  • ARIA tab nodes must have an accessible name (4 elements)

    ARIA tab nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • Heading levels should only increase by one (3 elements)

    Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

11 to fixGoogle 9250
  • No meta description

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

  • No H1 headline

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

  • Title is short (20 characters)

    Your title is only 20 characters: “Challenge Validation”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.capita.com/sitemap.xml, so Google discovers your pages only by following links.

  • 15 links with vague text

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

  • No robots.txt

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,361 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact centres” and “Contact us”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 7 other companies contacted

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

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

Upkeep, stack and company

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on capita.co.uk, including 19 speed issues, 11 SEO issues and 4 conversion gaps. 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