manheimcentral.org website review

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

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

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

audioeye.com costs a phone 2.3 s of main-thread work and 352 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

5 images could be 257 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

6 third-party services load with your homepage (audioeye.com, Google Tag Manager and Cloudflare and others), adding 1.3 MB and 2.7 s of main-thread time.

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

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

finalsite.net costs a phone 2 ms of main-thread work and 529 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 210 ms. During a long task the page ignores taps.

Polyfills for old browsers add 39 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 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

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

Your homepage downloads 2.1 MB in 74 requests on a phone: scripts 1.2 MB (16), images 511 KiB (16) and fonts 186 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

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

Some list items are not inside a list.

1 tap target is too small or too close together to hit reliably with a finger.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your meta description is only 38 characters: “Home - Manheim Central School District”. 70 to 160 characters is enough to sell the click.

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

No XML sitemap at https://www.manheimcentral.org/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 262 pages on manheimcentral.org and 35 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.manheimcentral.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.manheimcentral.org/about/overview-of-mcsd, https://www.manheimcentral.org/about/community-resources/volunteering, https://www.manheimcentral.org/about/comprehensive-plan, https://www.manheimcentral.org/about/directions-to-mcsd, https://www.manheimcentral.org/about/emergency-information/suicide-awareness-prevention and https://www.manheimcentral.org/about/emergency-information/emergency-preparedness-planning took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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.

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 825 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 8 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.