methactonfoundation.org website review

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

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

Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (firespring.com, Google Tag Manager and sitesearch360.com and others), adding 4.3 MB and 386 ms of main-thread time.

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

firespring.com costs a phone 187 ms of main-thread work and 3.9 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.

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

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

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 100 ms).

3 long tasks block the main thread while loading, the longest for 90 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.

Your largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fueling innovation, expanding opportunity, and supporting e…”.

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

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

The layout shifts by 0.215 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.4 MB in 46 requests on a phone: images 3.4 MB (21), scripts 520 KiB (11) and fonts 360 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 97 pages on methactonfoundation.org and 19 external pages.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.methactonfoundation.org/who-we-are, whose canonical is https://www.methactonfoundation.org/who-we-are/mission.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.firespring.com/core/v2/css/stylesheet.1793979919.css' from origin 'https://www…”.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 10 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.