Website review, no card needed

greenparty.org.uk logo

greenparty.org.uk website review

Visit site (opens in a new tab)Reviewed 25 October 202638 issues · 88 checks

This review found 38 issues worth fixing on greenparty.org.uk, 12 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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.0 s632 msMay 2Oct 17944 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026679 ms
May 9, 2026677 ms
May 16, 2026679 ms
May 23, 2026686 ms
May 30, 2026693 ms
Jun 6, 2026754 ms
Jun 13, 2026824 ms
Jun 20, 2026835 ms
Jun 27, 2026827 ms
Jul 4, 2026825 ms
Jul 11, 2026843 ms
Jul 18, 2026884 ms
Jul 25, 2026924 ms
Aug 1, 2026944 ms
Aug 8, 2026955 ms
Aug 15, 2026954 ms
Aug 22, 2026950 ms
Aug 29, 2026972 ms
Sep 5, 2026977 ms
Sep 12, 2026959 ms
Sep 19, 2026958 ms
Sep 26, 2026965 ms
Oct 3, 2026975 ms
Oct 10, 2026937 ms
Oct 17, 2026944 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms77 msMay 2Oct 17105 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202685 ms
May 9, 202681 ms
May 16, 202681 ms
May 23, 202681 ms
May 30, 202682 ms
Jun 6, 202689 ms
Jun 13, 202694 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202697 ms
Jul 11, 2026101 ms
Jul 18, 2026106 ms
Jul 25, 2026111 ms
Aug 1, 2026109 ms
Aug 8, 2026111 ms
Aug 15, 2026106 ms
Aug 22, 2026106 ms
Aug 29, 2026107 ms
Sep 5, 2026109 ms
Sep 12, 2026108 ms
Sep 19, 2026105 ms
Sep 26, 2026110 ms
Oct 3, 2026111 ms
Oct 10, 2026104 ms
Oct 17, 2026105 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 greenparty.org.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. greenparty.org.uk at 0.6 s0.6 s
  2. greenparty.org.uk at 1.1 s1.1 s
  3. greenparty.org.uk at 1.7 s1.7 s
  4. greenparty.org.uk at 2.3 s2.3 s
  5. greenparty.org.uk at 2.8 s2.8 s
  6. greenparty.org.uk at 3.4 s3.4 s
  7. greenparty.org.uk at 4.0 s4.0 s
  8. greenparty.org.uk at 4.5 s4.5 s

Speed

10 to fix45
  • Reduce unused JavaScript

    6.5 s · 710 KiB

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

  • Improve image delivery

    2.5 s · 1.1 MB

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

  • Render-blocking requests

    2.9 s

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45 (desktop: 71). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 5 third-party services on the page

    5 third-party services load with your homepage (hcaptcha.com, Google CDN and Stripe and others), adding 2.2 MB and 1.3 s of main-thread time.

  • Use efficient cache lifetimes

    950 ms · 389 KiB

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

  • hcaptcha.com adds 770 ms

    770 ms

    hcaptcha.com costs a phone 770 ms of main-thread work and 1.1 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.

  • Reduce unused CSS

    450 ms · 92 KiB

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

  • Google CDN adds 298 ms

    298 ms

    Google CDN costs a phone 298 ms of main-thread work and 731 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.

  • Main-thread work: 2.9 s

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

  • 13 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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: 4 ms

    4 ms

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

Core Web Vitals

8 to fix100
  • First Contentful Paint: 11.2 s

    11.2 s

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

  • Largest Contentful Paint: 25.0 s

    25.0 s

    Your largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to the Green Party”.

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • Tap response (INP) got 26% slower for real visitors

    +26%

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

  • Largest content (LCP) got 39% slower for real visitors

    +39%

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

  • Total Blocking Time: 415 ms

    415 ms

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

  • 6 images without width and height

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

7 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.2 s

    1.2 s

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

  • Real-user INP: 147 ms

    147 ms

    Real visitors wait 147 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 447 ms

    447 ms

    Real visitors wait 447 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

3 to fix53
  • Page weight: 5.5 MB in 83 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 83 requests on a phone: scripts 2.4 MB (31), images 2.0 MB (10) and HTML 458 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    194 KiB

    3 images are downloaded at several times the size a phone draws them, for example Green-World-Featured-Image-8.png at 1,080 px wide, shown at 326 px. Resized copies would save about 194 KiB.

  • 2 images below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.56 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 9092
  • 5 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • 7 links without text

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

  • 3 form fields without a label

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

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

    ARIA role should be appropriate for the element: 3 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).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 9296
  • Structured data has 3 problems

    Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 3 problems, for example “WebPage: thumbnailUrl is not an absolute URL ("https://greenparty.org.uk/app/uploads/2026/02/hannah.jpeg")”.

  • 47 internal links, 18 external

    The homepage links to 47 pages on greenparty.org.uk and 18 external pages.

7 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “Support our campaign to push the Government to do better - much better - to protect and restore nature.”.

  • One H1 headline

    Your main headline reads: “Welcome to the Green Party”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Welcome to the Green Party - Green Party”.

  • Canonical URL set

    The canonical URL is https://greenparty.org.uk/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (1,286 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 13 pages without a meta description

    https://greenparty.org.uk/about, https://greenparty.org.uk/about/our-manifesto, https://greenparty.org.uk/about/our-constitution, https://greenparty.org.uk/about/people, https://greenparty.org.uk/about/policy-making and https://greenparty.org.uk/get-involved and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 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 7791
  • 5 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

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

4 to fix69
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

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

    The homepage carries about 311 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: “Join the Green Party today”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Join” and “Join the Green Party today”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Matomo and Cloudflare Web Analytics.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 hosts 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 greenparty.org.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
Matomo

Company

Founded
1990
Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on greenparty.org.uk, including 18 speed issues, 1 SEO issue 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