maclarenschool.org website review

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

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

Your mobile performance score is 38 (desktop: 33). 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, sharpschool.com and Other Google APIs/SDKs and others), adding 7.1 MB and 492 ms of main-thread time.

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

sharpschool.com costs a phone 190 ms of main-thread work and 6.4 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.

Google Tag Manager costs a phone 233 ms of main-thread work and 535 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 1,541 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying JavaScript.

3 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.

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Thomas MacLaren Logo”.

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

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

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

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

For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.

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

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

8 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-17, real Chrome visitors' tap response (inp) went from 99 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.4 MB in 99 requests on a phone: images 5.8 MB (15), scripts 1.2 MB (50) and fonts 222 KiB (4). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.3 MB together. On a phone connection a single image that size takes seconds.

10 images (5.8 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.

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

1 image is downloaded at several times the size a phone draws it, for example b2f79b1b-3ca8-45fe-9d66-a6d9d54a72fa.jpeg at 2,992 px wide, shown at 390 px. Resized copies would save about 285 KiB.

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 29 characters: “Home - Thomas MacLaren School”. Between 30 and 65 characters leaves room to say what you do and for whom.

41 links have no real href, so search engines can't follow them.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 290 pages on maclarenschool.org and 7 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://www.maclarenschool.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.

https://www.maclarenschool.org/about_us/school_board/strategic_plan and https://www.maclarenschool.org/about_us/student_data_privacy/f_e_r_p_a_and_p_p_r_a_notice have no <title>, so Google invents the link text in results.

/ and https://www.maclarenschool.org/home all use the title “Home - Thomas MacLaren School”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.maclarenschool.org/home, https://www.maclarenschool.org/about_us, https://www.maclarenschool.org/about_us/vision_and_mission, https://www.maclarenschool.org/about_us/vision_and_mission/about_our_logo, https://www.maclarenschool.org/about_us/vision_and_mission/who_was_thomas_mac_laren_ and https://www.maclarenschool.org/about_us/f_a_q and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.maclarenschool.org/about_us/MacLarenLibrary, whose canonical is https://www.maclarenschool.org/news/mac_laren_library. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.maclarenschool.org/home, https://www.maclarenschool.org/about_us/school_board/strategic_plan and https://www.maclarenschool.org/about_us/student_data_privacy/f_e_r_p_a_and_p_p_r_a_notice have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

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

5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdnsm2-ss13.sharpschool.com/App_Themes/default/merged.css' from origin 'https://ww…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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