Website review, no card needed
hbcsd.k12.ca.us website review
Visit site (opens in a new tab)Reviewed 1 November 202644 issues · 83 checks
This review found 44 issues worth fixing on hbcsd.k12.ca.us, 17 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Improve image delivery
16.3 s · 13.9 MB15 images could be 13.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 16.3 s faster on a phone.
Reduce unused JavaScript
7.0 s · 738 KiBAbout 738 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 5.7 MB47 files are served with short cache lifetimes, so returning visitors download them again (5.7 MB).
Render-blocking requests
3.8 s47 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Reduce unused CSS
1.7 s · 143 KiBAbout 143 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.2 s
A phone's processor spends 6.2 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 16.4 MB and 1.3 s of main-thread time.
parentsquare.com adds 159 ms
159 msparentsquare.com costs a phone 159 ms of main-thread work and 14.8 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.
Google CDN adds 616 ms
616 msGoogle CDN costs a phone 616 ms of main-thread work and 749 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.
Minify JavaScript
330 ms · 32 KiB32 KiB could be saved by minifying JavaScript.
Minify CSS
330 ms · 12 KiB12 KiB could be saved by minifying CSS.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 267 ms. During a long task the page ignores taps.
2,375 HTML elements
The page has 2,375 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Adobe TypeKit adds 10 ms
10 msAdobe TypeKit costs a phone 10 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.
Legacy JavaScript
150 ms · 15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.4 s
8.4 sThe first text or image appears after 8.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 49.0 s
49.0 sYour largest element takes 49.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 50.2 s
50.2 sThe page becomes fully interactive after 50.2 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 797 ms
797 msScripts block taps and scrolling for 797 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 21.3 MB in 201 requests
21.3 MBYour homepage downloads 21.3 MB in 201 requests on a phone: images 16.5 MB (24), scripts 2.4 MB (98) and other files 1.1 MB (15). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 9.0 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
6.9 MB11 images are downloaded at several times the size a phone draws them, for example img_pd_102722_ixhafc.jpg at 2,560 px wide, shown at 330 px. Resized copies would save about 6.9 MB.
12 images in older formats
12 images (10.0 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.
1 image below the first screen load straight away
1 image further down the page (2.4 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.0 g of CO₂ per visit
6.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.05 g of CO₂e: 726.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
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)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to hbcsd.us, not hbcsd.k12.ca.us, so Google may credit that host instead.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (37 characters)
Your meta description is only 37 characters: “Huntington Beach City School District”. 70 to 160 characters is enough to sell the click.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
221 internal links, 39 external
The homepage links to 221 pages on hbcsd.k12.ca.us and 39 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Homepage”.
Title: 44 characters
Your title is a healthy 44 characters: “Huntington Beach City School District - HOME”.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://hbcsd.k12.ca.us/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://hbcsd.k12.ca.us/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (872 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://hbcsd.k12.ca.us/16234_2 has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://hbcsd.k12.ca.us/16234_2 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://hbcsd.k12.ca.us/16234_2 has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages share a meta description
https://hbcsd.k12.ca.us/1399_1, https://hbcsd.k12.ca.us/strategicplan, https://hbcsd.k12.ca.us/calendar, https://hbcsd.k12.ca.us/14525_2, https://hbcsd.k12.ca.us/14526_2 and https://hbcsd.k12.ca.us/14528_2 and 7 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://hbcsd.k12.ca.us/16234_2 has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://hbcsd.k12.ca.us/16234_2 took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 141 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “ErrorUtils caught an error: Could not find element "u_1_20_SN" [Caught in: Module "__elem_a588f507_1_0_qp"] Subsequent …”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
33 of 34 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 392 words of copy
The homepage carries about 392 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Board Meeting Schedule”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
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.
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hbcsd.k12.ca.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on hbcsd.k12.ca.us, including 21 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.