smusd.org website review

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

12 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, parentsquare.com and Other Google APIs/SDKs and others), adding 8.7 MB and 816 ms of main-thread time.

parentsquare.com costs a phone 153 ms of main-thread work and 6.7 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 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Google CDN costs a phone 473 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.

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

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

Adobe TypeKit costs a phone 11 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.

Amazon Web Services costs a phone 0 ms of main-thread work and 503 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.

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

32 KiB could be saved by minifying JavaScript.

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

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

12 KiB could be saved by minifying CSS.

Desktop scores 80 but mobile only 49. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

Your largest element takes 36.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Engaging Students...Inspiring Futures. Welcome to San Marco…”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.0 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.

Your homepage downloads 9.5 MB in 155 requests on a phone: images 6.3 MB (26), scripts 1.4 MB (69) and fonts 1.2 MB (25). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

9 images (2.8 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.

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

4 images are downloaded at several times the size a phone draws them, for example img_lnk__04ggai316rjoebpbjji.png at 800 px wide, shown at 227 px. Resized copies would save about 332 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 323.1 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.

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

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

Your meta description is only 34 characters: “San Marcos Unified School District”. 70 to 160 characters is enough to sell the click.

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 318 pages on smusd.org and 52 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://smusd.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://smusd.org/153539_2 has no <title>, so Google invents the link text in results.

https://smusd.org/10349_1 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://smusd.org/153539_2 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://smusd.org/10349_1 all use the title “San Marcos Unified School District - Home”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://smusd.org/153539_2 has no meta description, so Google writes the search snippet from whatever text it finds.

https://smusd.org/10349_1, https://smusd.org/about-us, https://smusd.org/district-overview, https://smusd.org/superintendent-executive-team, https://smusd.org/public-records-request and https://smusd.org/accountability-report-cards and 8 others use the same meta description. A description written for each page earns more clicks.

https://smusd.org/153539_2 has no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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