ksbe.edu website review

31 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

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

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

About 379 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

7 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Evergage and Other Google APIs/SDKs and others), adding 1.0 MB and 527 ms of main-thread time.

Google Tag Manager costs a phone 388 ms of main-thread work and 684 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 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.

7 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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.

Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ola Pauahi, Ola Hawai‘i LEARN THE LEGACY”.

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

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 84 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 80 requests on a phone: images 1.3 MB (25), scripts 989 KiB (17) and stylesheets 420 KiB (14). Under 2 MB keeps phones on slow connections fast.

2 images (216 KiB) 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.

2 images further down the page (216 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

All page content should be contained by landmarks: 37 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h6, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 18 characters: “Kamehameha Schools”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There is no robots.txt at ksbe.edu/robots.txt, the first file search crawlers ask for.

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 205 pages on ksbe.edu and 45 external pages.

There is no https://www.ksbe.edu/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.ksbe.edu/hawaii/summer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.ksbe.edu/hawaii/summer has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ksbe.edu/malama-ola, https://www.ksbe.edu/student-safety-and-well-being, https://www.ksbe.edu/education/hawaii, https://www.ksbe.edu/education/hawaii/elementary-school, https://www.ksbe.edu/education/hawaii/middle-school and https://www.ksbe.edu/education/hawaii/high-school and 8 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ksbe.edu/digital/canvas, whose canonical is https://www.ksbe.edu/canvas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ksbe.edu/student-safety-and-well-being, https://www.ksbe.edu/education/hawaii, https://www.ksbe.edu/hawaii/summer, https://www.ksbe.edu/education/hawaii/contact-us, https://www.ksbe.edu/digital/canvas and https://www.ksbe.edu/education/kapalama and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ksbe.edu/student-safety-and-well-being, https://www.ksbe.edu/digital/canvas, https://www.ksbe.edu/education/kapalama/halau-kukalaulama and https://www.ksbe.edu/education/kapalama/residential-life took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

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: 6 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 form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and The Trade Desk (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 9 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.