westbuckland.com website review

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

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

200 KiB could be saved by minifying JavaScript.

8 third-party services load with your homepage (Google Tag Manager, imagekit.io and Facebook and others), adding 4.9 MB and 805 ms of main-thread time.

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

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

Your mobile performance score is 54 (desktop: 50). Pages that score under 90 lose visitors before the first paint.

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

imagekit.io costs a phone 243 ms of main-thread work and 3.5 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.

38 KiB could be saved by minifying CSS.

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

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

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

Vimeo costs a phone 22 ms of main-thread work and 528 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.

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

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

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.

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 see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (9.1 s).

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your homepage downloads 6.0 MB in 165 requests on a phone: images 3.5 MB (91), scripts 1.9 MB (35) and fonts 429 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

14 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images (1.6 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example Lowe-Helen-2025-07-10-111536.jpg at 1,406 px wide, shown at 350 px. Resized copies would save about 53 KiB.

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

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

Some list items are not inside a list.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

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

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

The homepage links to 149 pages on westbuckland.com and 102 external pages.

There is no https://westbuckland.com/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.

https://westbuckland.com/admissions/open-days-and-visits, https://westbuckland.com/about/west-buckland-is, https://westbuckland.com/middleschool/exam-results, https://westbuckland.com/about/ethos-aims, https://westbuckland.com/about/our-food and https://westbuckland.com/about/inspection-reports and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://westbuckland.com/admissions/open-days-and-visits, https://westbuckland.com/about, https://westbuckland.com/about/west-buckland-is, https://westbuckland.com/middleschool/exam-results, https://westbuckland.com/about/ethos-aims and https://westbuckland.com/about/our-facilities and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://westbuckland.com/admissions/open-days-and-visits, https://westbuckland.com/about, https://westbuckland.com/about/west-buckland-is, https://westbuckland.com/about/ethos-aims, https://westbuckland.com/about/our-facilities and https://westbuckland.com/about/meet-the-team and 6 others took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://westbuckland.com/wp-content/uploads/sb-instagram-feed-images/858380745_18370692763213765_762577849666065567_nfull.webp.

7 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

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.

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

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