change.org website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

35 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Stripe and others), adding 1.5 MB and 1.2 s of main-thread time.

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

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

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

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

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

38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

Facebook costs a phone 265 ms of main-thread work and 305 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.

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

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.

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.

Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Impact story 3 of 5”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.5 MB in 119 requests on a phone: scripts 3.3 MB (62), images 857 KiB (12) and other files 98 KiB (38). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (6 elements).

The homepage links to 62 pages on change.org and 9 external pages.

There is no /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.

/topic/tariffs-en-us is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/impact-stories/10492133, /impact-stories/34968392, /impact-stories/36872619, /impact-stories/37815770 and /impact-stories/490556983 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /impact-stories/10492133, whose canonical is /impact-stories/no-more-kids-with-cancer-clean-up-the-santa-susana-field-lab. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/start-a-petition/intro has no <h1> headline, so visitors and search engines get no clear main topic.

/start-a-petition/intro 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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=142000274&tm=gtm002&Ver=2&mid=e67f904a-f156-4b01-b9b2-40cb38c4899c&bo=4&sid=0cd89310c5b611f1b0cbefa1e5ed0954&vid=0cd8b9c0c5b611f18eb25de870987fdf&vids=0&msclkid=N&pi=9.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

change.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

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.

The homepage carries about 717 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 1 more (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.

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

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.

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