wedonthavetime.org website review

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

hcaptcha.com costs a phone 2.4 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Google CDN costs a phone 1.3 s of main-thread work and 2.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (hcaptcha.com, Google CDN and donorbox.org and others), adding 11.6 MB and 6.4 s of main-thread time.

25 images could be 2.5 MB 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.

donorbox.org costs a phone 695 ms of main-thread work and 3.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.

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

Stripe costs a phone 619 ms of main-thread work and 608 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.

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

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

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

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

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

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.

4 KiB could be saved by minifying CSS.

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 visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The World's Largest Media Platform for Climate ActionWelcom…”.

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

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

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

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

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

Your homepage downloads 37.4 MB in 687 requests on a phone: scripts 20.3 MB (292), images 11.8 MB (97) and fonts 1.8 MB (36). Under 2 MB keeps phones on slow connections fast.

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

8 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

2 frames have no title, so screen-reader users cannot tell what they contain.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

There are 2 <h1> headlines (“"Dear UN Ambassador, Political leadership has a c…” and “Join the world's largest climate solution network”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://api.wedonthavetime.org/sitemap/static/sitemap_index.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 27 pages on wedonthavetime.org and 38 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://app.wedonthavetime.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.

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.

https://app.wedonthavetime.org/frontpage/energyefficiencyaction has no <title>, so Google invents the link text in results.

https://app.wedonthavetime.org/?utm_source=wwwredirect, https://app.wedonthavetime.org/home/filter and https://app.wedonthavetime.org/play all use the title “The World’s Largest Media Platform for Climate Action”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://app.wedonthavetime.org/frontpage/energyefficiencyaction has no meta description, so Google writes the search snippet from whatever text it finds.

https://app.wedonthavetime.org/home/filter, https://app.wedonthavetime.org/home/all, https://app.wedonthavetime.org/play, https://app.wedonthavetime.org/posts/3a1a742e-4b07-423a-b506-63f7f99ccdaf, https://app.wedonthavetime.org/posts/6cf5394a-5f42-482f-b075-b9f06c9db210 and https://app.wedonthavetime.org/posts/afc414a1-2c59-433b-9940-3596f68bd785 and 3 others use the same meta description. A description written for each page earns more clicks.

https://app.wedonthavetime.org/home/filter, https://app.wedonthavetime.org/home/all, https://app.wedonthavetime.org/posts/3a1a742e-4b07-423a-b506-63f7f99ccdaf, https://app.wedonthavetime.org/posts/6cf5394a-5f42-482f-b075-b9f06c9db210, https://app.wedonthavetime.org/frontpage/energyefficiencyaction and https://app.wedonthavetime.org/posts/afc414a1-2c59-433b-9940-3596f68bd785 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://app.wedonthavetime.org/home/filter and https://app.wedonthavetime.org/frontpage/energyefficiencyaction have 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.

https://app.wedonthavetime.org/posts/6cf5394a-5f42-482f-b075-b9f06c9db210, https://app.wedonthavetime.org/posts/9fe64be2-2adc-4656-a461-c0547922682b, https://app.wedonthavetime.org/posts/73a042db-d6ad-48fb-9354-d1b95962c461, https://app.wedonthavetime.org/posts/2073af0c-6113-4fa8-b6e7-328e5a55778e and https://app.wedonthavetime.org/posts/f579875c-ab4d-47e5-85f8-6453908a7b28 took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

8 errors were logged to the browser console during Google's test (“Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 f…”).

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

Large scripts ship without source maps.

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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,111 words of visible text.