Website review, no card needed

oxford.gov.uk logo

oxford.gov.uk website review

Visit site (opens in a new tab)Reviewed 28 October 202625 issues · 74 checks

This review found 25 issues worth fixing on oxford.gov.uk, 9 of them high impact, across 74 checks. The most urgent: improve image delivery. 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
973 ms880 msMay 9Oct 24914 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026899 ms
May 16, 2026893 ms
May 23, 2026899 ms
May 30, 2026934 ms
Jun 6, 2026891 ms
Jun 13, 2026901 ms
Jun 20, 2026912 ms
Jun 27, 2026899 ms
Jul 4, 2026917 ms
Jul 11, 2026925 ms
Jul 18, 2026922 ms
Jul 25, 2026918 ms
Aug 1, 2026936 ms
Aug 8, 2026931 ms
Aug 15, 2026945 ms
Aug 22, 2026956 ms
Aug 29, 2026956 ms
Sep 5, 2026962 ms
Sep 12, 2026961 ms
Sep 19, 2026950 ms
Sep 26, 2026937 ms
Oct 3, 2026927 ms
Oct 10, 2026902 ms
Oct 17, 2026902 ms
Oct 24, 2026914 ms
Real-visitor tap response (INP)75th percentile, phones
87 ms81 msMay 9Oct 2483 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202682 ms
May 16, 202682 ms
May 23, 202682 ms
May 30, 202683 ms
Jun 6, 202683 ms
Jun 13, 202684 ms
Jun 20, 202684 ms
Jun 27, 202685 ms
Jul 4, 202685 ms
Jul 11, 202686 ms
Jul 18, 202686 ms
Jul 25, 202685 ms
Aug 1, 202685 ms
Aug 8, 202684 ms
Aug 15, 202684 ms
Aug 22, 202685 ms
Aug 29, 202685 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202685 ms
Sep 26, 202684 ms
Oct 3, 202684 ms
Oct 10, 202683 ms
Oct 17, 202683 ms
Oct 24, 202683 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 oxford.gov.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix54
  • Improve image delivery

    6.3 s · 1.4 MB

    5 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.3 s faster on a phone.

  • Use efficient cache lifetimes

    800 ms · 282 KiB

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

  • Mobile performance score: 54

    54/100

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

  • Render-blocking requests

    950 ms

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

  • Reduce unused JavaScript

    450 ms · 128 KiB

    About 128 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 86 KiB

    About 86 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Optanon, Google Tag Manager and Google CDN and others), adding 383 KiB and 151 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 83 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    9 KiB

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.48

    0.48

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

  • Largest Contentful Paint: 10.1 s

    10.1 s

    Your largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Picture of Oxford's dreaming spires from South Park”.

  • Cumulative Layout Shift: 0.457

    0.457

    The layout shifts by 0.457 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 10.1 s

    10.1 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

7 checks passed
  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user INP: 89 ms

    89 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 382 ms

    382 ms

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

  • Speed Index: 3.2 s

    3.2 s

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    Copy_of_New_website_front_page_images_2.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.3 MB in 43 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 43 requests on a phone: images 1.8 MB (14), scripts 342 KiB (13) and stylesheets 91 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.6 MB) 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.

  • 5 images below the first screen load straight away

    5 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    134 KiB

    1 image is downloaded at several times the size a phone draws it, for example Website_homepage_banner__1_.jpg at 2,840 px wide, shown at 390 px. Resized copies would save about 134 KiB.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087
  • No structured data

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

  • Meta description is short (28 characters)

    Your meta description is only 28 characters: “Oxford City Council Homepage”. 70 to 160 characters is enough to sell the click.

  • No robots.txt

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

  • Open Graph partly set

    Open Graph is missing 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.

  • 113 internal links, 9 external

    The homepage links to 113 pages on oxford.gov.uk and 9 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Oxford City Council - Home page”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Oxford City Council Homepage – Oxford City Council”.

  • Canonical URL set

    The canonical URL is https://www.oxford.gov.uk/.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.oxford.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.oxford.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 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.oxford.gov.uk/newsletter, whose canonical is https://www.oxford.gov.uk/oxfords-future/email-newsletter. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://www.oxford.gov.uk/newsletter 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 86 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

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

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

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

    The homepage carries about 448 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Register”, “Apply for it online” and “Contact us”.

  • 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 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

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

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

Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1000

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on oxford.gov.uk, including 12 speed issues, 3 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