redmondschools.org website review

12 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 3.0 s faster on a phone.

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

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

Your mobile performance score is 38. 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, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Google CDN, parentsquare.com and Google Tag Manager and others), adding 6.6 MB and 1.3 s of main-thread time.

parentsquare.com costs a phone 256 ms of main-thread work and 5.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.

About 140 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 CDN costs a phone 555 ms of main-thread work and 743 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.

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

The page has 2,925 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

32 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

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

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

Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three people in blue workwear collaborate in a workshop set…”.

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

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

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

Scripts block taps and scrolling for 862 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-24, real Chrome visitors' tap response (inp) went from 86 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.4 MB in 152 requests on a phone: images 4.0 MB (24), scripts 1.5 MB (70) and fonts 1.3 MB (24). Under 2 MB keeps phones on slow connections fast.

inline_images_8887e8736113e957_1793396092705-Copy+of+Copy+of weighs 1.1 MB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example inline_images_8887e8736113e957_1793396092705-Copy+of+Copy+of at 1,080 px wide, shown at 227 px. Resized copies would save about 797 KiB.

11 images (2.3 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.

4 images further down the page (563 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 2.10 g of CO₂e: 252.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

4 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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 26 characters: “Redmond School District 2J”. 70 to 160 characters is enough to sell the click.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

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

The homepage links to 262 pages on redmondschools.org and 43 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.redmondschools.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.redmondschools.org/emergency-operations-plan is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.redmondschools.org/school-safety and https://www.redmondschools.org/school-safety-home all use the title “Redmond School District 2J - School Safety Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.redmondschools.org/emergency-operations-plan has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.redmondschools.org/our-district, https://www.redmondschools.org/331485_2, https://www.redmondschools.org/data-reporting-and-district-plans, https://www.redmondschools.org/districtstaff, https://www.redmondschools.org/mission-and-vision and https://www.redmondschools.org/school-safety and 6 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.redmondschools.org/school-safety, whose canonical is https://www.redmondschools.org/school-safety-home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.redmondschools.org/emergency-operations-plan has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.redmondschools.org/emergency-operations-plan and https://www.redmondschools.org/safeoregon took over 3 s to send their HTML from our server.

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

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: 9 trust badges. 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.

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