sbcc.edu website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 1.5 MB and 641 ms of main-thread time.

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

68 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 361 ms of main-thread work and 881 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.0 s on main-thread work while loading, 680 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

8 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 50.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content, provide social media…”.

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

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

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

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

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-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 139.0 MB in 142 requests on a phone: images 137.3 MB (70), scripts 1.6 MB (26) and stylesheets 46 KiB (7). Under 2 MB keeps phones on slow connections fast.

4 images weigh 6.5 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example 2026-Enrollment-Coach-Announcement.png at 1,400 px wide, shown at 360 px. Resized copies would save about 1.1 MB.

7 images (7.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 (2.3 MB) 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 39.40 g of CO₂e: 4727.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 links inside paragraphs rely on colour alone to stand out.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Headings should not be empty: 4 elements on the page fail 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 54 characters: “sbcc.edu - Learn more about all SBCC has to offer you!”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

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

The homepage links to 101 pages on sbcc.edu and 182 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://sbcc.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://sbcc.edu/about and https://sbcc.edu/about/index.php all use the title “About - Santa Barbara City College”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sbcc.edu/about and https://sbcc.edu/about/index.php use the same meta description. A description written for each page earns more clicks.

https://sbcc.edu/extendedlearning/apply-register.php has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://scontent-iad3-2.cdninstagram.com/o1/v/t2/f2/m86/AQNfIFku06yir3fiZfbTqtzpDIQPNlltCxMWexEZN5FSEF3gnOobcW87m0NxTM17JylZSeOTtVlTbG1yv6nwKAANtDJR2UsjHkfcrwo.mp4?_nc_cat=103&_nc_sid=5e9851&_nc_ht=sc.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “google.translate.TranslateElement is not a constructor”.

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

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.