inspirationtrust.org website review

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

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Maps and others), adding 2.0 MB and 820 ms of main-thread time.

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

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

3 images could be 413 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google CDN costs a phone 275 ms of main-thread work and 30 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 2.6 s on main-thread work while loading, 821 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

reactfiles.co.uk costs a phone 0 ms of main-thread work and 853 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.

reactcdn.co.uk costs a phone 13 ms of main-thread work and 390 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.

9 long tasks block the main thread while loading, the longest for 158 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 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “care.”.

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

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

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

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

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

14 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 2.7 MB in 77 requests on a phone: images 1.3 MB (48), scripts 912 KiB (12) and fonts 451 KiB (6). Under 2 MB keeps phones on slow connections fast.

6 images (511 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.

1 image is downloaded at several times the size a phone draws it, for example loading.gif at 1,920 px wide, shown at 293 px. Resized copies would save about 232 KiB.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 28 characters: “Welcome to Inspiration Trust”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is 219 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 96 pages on inspirationtrust.org and 48 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot) and ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://inspirationtrust.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, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://inspirationtrust.org/103/welcome-from-the-ceo, https://inspirationtrust.org/16/meet-our-team-1, https://inspirationtrust.org/17/vision-values, https://inspirationtrust.org/1776/inspiration-trust-way, https://inspirationtrust.org/9/key-information-policies and https://inspirationtrust.org/19/inclusion and 9 others use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 59 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://assets.reactcdn.co.uk/fontawesome/5.11/css/all.min.css' from origin 'https://inspi…”.

Large scripts ship without source maps.

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.

Social proof on the homepage: 25 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,226 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 2 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.