ticketforchange.org website review

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

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

1 image could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 third-party service load with your homepage (cdn-cookieyes.com), adding 34 KiB and 16 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Pop-up-site-charte-2024-3-768x768.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (52 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.

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

ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 83 pages on ticketforchange.org and 8 external pages.

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.

There is no https://ticketforchange.org/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.

https://ticketforchange.org/nos-podcasts has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

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

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

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 198 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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