fivekeys.org website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.

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

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

34 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

8 third-party services load with your homepage (Squarespace, YouTube and Google Tag Manager and others), adding 3.6 MB and 1.5 s of main-thread time.

Squarespace costs a phone 449 ms of main-thread work and 1.0 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.

YouTube costs a phone 432 ms of main-thread work and 991 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 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

Google Tag Manager costs a phone 353 ms of main-thread work and 587 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 3.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

39 KiB could be saved by minifying JavaScript.

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

sqspcdn.com costs a phone 56 ms of main-thread work and 331 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.

Adobe TypeKit costs a phone 13 ms of main-thread work and 308 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.

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

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

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

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.

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

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

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

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

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

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

Real visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

1 image 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 167 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.5 MB in 160 requests on a phone: images 3.7 MB (44), scripts 3.1 MB (59) and fonts 344 KiB (19). Under 2 MB keeps phones on slow connections fast.

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

CharterSchool+MainSiteGraphic.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 9 characters: “Five Keys”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“”, “ANNOUNCING OUR NEW PRESIDENT” and “WHAT WE DO”). One clear main headline is easier for people and search engines.

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

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/596b4e81f14aa1a6e70…”.

The homepage links to 134 pages on fivekeys.org and 30 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

/careers, /night-of-courage-photos, /the-good-news/tour-de-five-keys and /20th-anniversary-fundraiser 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 /20th-anniversary-fundraiser, whose canonical is /21-anniversary-fundraiser. 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 48 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/596b4e81f14aa1a6e7054701/210/52a74dafe4b073…”.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.fivekeyscharter.org/20th-anniversary-fundraiser.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fivekeyscharter.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fivekeyscharter.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, 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 7 cookies, 1 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.