Website review, no card needed

gca.gov.uk logo

gca.gov.uk website review

Visit site (opens in a new tab)Reviewed 30 October 202623 issues · 74 checks

This review found 23 issues worth fixing on gca.gov.uk, 4 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.0 s1.7 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.4 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.3 s
Jul 4, 20263.2 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.0 s
Aug 1, 20262.8 s
Aug 8, 20262.6 s
Aug 15, 20262.3 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20263.1 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20262.8 s
Oct 17, 20262.3 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
180 ms144 msMay 9Oct 24151 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026163 ms
May 16, 2026163 ms
May 23, 2026162 ms
May 30, 2026168 ms
Jun 6, 2026166 ms
Jun 13, 2026163 ms
Jun 20, 2026163 ms
Jun 27, 2026162 ms
Jul 4, 2026163 ms
Jul 11, 2026166 ms
Jul 18, 2026163 ms
Jul 25, 2026170 ms
Aug 1, 2026167 ms
Aug 8, 2026162 ms
Aug 15, 2026160 ms
Aug 22, 2026159 ms
Aug 29, 2026161 ms
Sep 5, 2026166 ms
Sep 12, 2026176 ms
Sep 19, 2026170 ms
Sep 26, 2026162 ms
Oct 3, 2026159 ms
Oct 10, 2026152 ms
Oct 17, 2026148 ms
Oct 24, 2026151 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 gca.gov.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix97
  • Use efficient cache lifetimes

    584 KiB

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

  • Improve image delivery

    514 KiB

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

  • Google Tag Manager adds 428 ms

    428 ms

    Google Tag Manager costs a phone 428 ms of main-thread work and 681 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 JavaScript

    379 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, useberry.com and Google Analytics and others), adding 760 KiB and 434 ms of main-thread time.

  • Render-blocking requests

    250 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    29 KiB

    About 29 KiB of CSS is downloaded but never applied on this page.

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

3 checks passed
  • Mobile performance score: 97

    97/100

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

  • Main-thread work: 0.7 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • 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.

  • Time to Interactive: 9.4 s

    9.4 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 3 images without width and height

    3 images 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-24, real Chrome visitors' tap response (inp) went from 163 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 170 ms

    170 ms

    Real visitors wait 170 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.

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

    -36%

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

  • Total Blocking Time: 129 ms

    129 ms

    Scripts block the page for only 129 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).

  • 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 “We use cookies to collect information about how you use gca…”.

Images and page weight

2 to fix83
  • 4 images in older formats

    4 images (644 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.

  • 3 images below the first screen load straight away

    3 images further down the page (554 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.51 g

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

2 checks passed
  • Page weight: 1.8 MB in 29 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 29 requests on a phone: scripts 831 KiB (13), images 692 KiB (7) and fonts 256 KiB (3). That is a lean page.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 10099
  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 6 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 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 0 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 10092
  • 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.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 73 internal links, 36 external

    The homepage links to 73 pages on gca.gov.uk and 36 external pages.

5 checks passed
  • Meta description: 104 characters

    Your meta description is 104 characters: “The UK's Government Commercial Agency (GCA). We achieve value for the nation through public procurement.”.

  • One H1 headline

    Your main headline reads: “Supporting better public procurement”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Government Commercial Agency - GCA”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gca.gov.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.gca.gov.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 (639 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 pages without a meta description

    https://www.gca.gov.uk/agreements, https://www.gca.gov.uk/agreements/upcoming, https://www.gca.gov.uk/suppliers, https://www.gca.gov.uk/news and https://www.gca.gov.uk/newsletter have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://www.gca.gov.uk/how-to-buy took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 9691
  • 5 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 488 words of visible text.

3 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “How to buy”, “Subscribe to newsletter” and “Contact press office”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 gca.gov.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
Hosting
AWS

Company

Founded
2026

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on gca.gov.uk, including 10 speed issues, 2 SEO issues and 3 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