cornerstoneprep.org website review

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

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

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

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

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

Google Tag Manager costs a phone 337 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.

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

finalsite.net costs a phone 0 ms of main-thread work and 461 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.

7 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Cloudflare and others), adding 1,015 KiB and 425 ms of main-thread time.

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

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

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

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 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cornerstone Principal Kelly Burton smiles with a ninth grad…”.

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

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

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

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

2 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 102 ms to 104 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 2.6 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

1 image is downloaded at several times the size a phone draws it, for example piper-type-1-diabete-service-dog-marley-100226-5-96518385e19 at 512 px wide, shown at 1 px. Resized copies would save about 59 KiB.

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

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.

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

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

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 187 pages on cornerstoneprep.org and 16 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 /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.

/about and /about/portrait-of-a-graduate have no <h1> headline, so visitors and search engines get no clear main topic.

/about/history-timeline, /about/staff, /about/meet-our-board, /about/contact-us and /admissions took over 3 s to send their HTML from our server.

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

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

Large scripts ship without source maps.

2 links go through two or more redirects, for example https://sis.factsmgt.com/accounts/Account/Login?ReturnUrl=%2Faccounts%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DfamilyPortalCode%26redirect_uri%3Dhttps%253A%252F%252Fsis.factsmgt.com%252Ffamily-portal%252Fsignin-oidc%26response_type%3Dcode%26scope%3Dopenid%2520profile%2520familyPortalUserInfo%2520familyPortalUserConfig%2520offline_access%2520ftApi%26code_challenge%3DuQ8ZFV33mauNjWqakB27wPyKl3b4z06ZfYbL3til7uQ%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639053942196635693.MDM2MDY1NDYtNWU0NS00MzFmLTk4NWQtZTZjM2E5YzRkZGFiOGVmZDZhMjQtZGM1ZS00MWI5LWFjZDQtMjI5NzA3MzgyOTcy%26state%3DCfDJ8Lq1N5Cgm6tFnilnlNGlkcGovimi6IAIbeTFmI1S31OOAXU2coqWiYHiF-u6p4eltBbTmvyNJ2hs1nzFRXixZQ_olhGsdl74dM_pHnEW9Wd86yRvZ9oY1R-cUaIPBXFq1SYovZvczk8FfW1zzPRlDbOe8DWv5tkC6-LZrqPcQ7qojes4DaB1RHJ0OSANVXzR8BLY491SJhLXg8W6JnF3M7ygOpNwJ5xcvvPppz90eDKELWgHWLLdaJ4BBj_t2Wpmeal_lKmPL4MexEwysbtYlnTiBhVIEpBtmBFQXgYxUb3CeR7SX1HYdR5JVdVNCfBmyqWJpcK7F88kNAwU26bIOpt78kVe2EdMKWnhjQLRBkzB0VL6LnxdemUTf7-MNk20dSorEoni-qS1eEbohnNsvWwusDoz5KH9MF6m1DDI6p3-yvNNnUhlmzSwE_e78E_XZoENSMHY-MiXOkdZuEneJfvkYQCX52Hj9A3lxnFwnOSpe2CFNGWIdE2S4zKnyOyvTQ%26x-client-SKU%3DID_NET9_0%26x-client-ver%3D8.15.0.0.

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.

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

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: 10 customer or partner logos. 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.

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

DMARC is set to p=none, so mail pretending to be cornerstoneprep.org is still delivered. Reports are on, so moving to quarantine is the next step.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 include:_spf.google.com ~all.”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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