thon.org website review

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

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

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

The page has 3,800 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.3 MB and 831 ms of main-thread time.

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

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

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

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

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

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

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

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.

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

Your largest element takes 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “50-years-of-thon_51882273867_o”.

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

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

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

20 images 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' tap response (inp) went from 71 ms to 69 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.5 MB in 209 requests on a phone: images 3.4 MB (98), scripts 1.4 MB (49) and other files 436 KiB (22). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example [email protected] at 390 px wide, shown at 95 px. Resized copies would save about 61 KiB.

2 images (76 KiB) 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

Structured data found (Organization, VideoObject and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 85 pages on thon.org and 227 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://donate.thon.org//resources/css/embed-donate-fetch.css?v=202610271751' from origin …”.

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.

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

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 720 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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 16 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.