witcc.edu website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Snapchat and Facebook and others), adding 2.0 MB and 1.7 s of main-thread time.

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

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

Google Tag Manager costs a phone 684 ms of main-thread work and 526 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.

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

geckochat.io costs a phone 130 ms of main-thread work and 811 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.

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

Desktop scores 56 but mobile only 18. 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.

3 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 32.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Western Iowa Tech Your opportunity to reach higher, to grow…”.

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

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 165 requests on a phone: images 4.2 MB (39), scripts 1.7 MB (35) and fonts 614 KiB (11). Under 2 MB keeps phones on slow connections fast.

6EE8B918-F387-FFDC-E16BC15E8A0F5D20_carouselimage.png weighs 2.8 MB. On a phone connection a single image that size takes seconds.

6 images (3.6 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 is downloaded at several times the size a phone draws it, for example C7435839-CA00-EE06-D50E36D9915A7A88_carouselimage.jpg at 2,000 px wide, shown at 432 px. Resized copies would save about 96 KiB.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 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.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No XML sitemap at https://www.witcc.edu/sitemap.xml, so Google discovers your pages only by following links.

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 117 pages on witcc.edu and 15 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.

The HTML your server sends has 347 of the 602 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.witcc.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.witcc.edu/sioux-city, https://www.witcc.edu/regional-centers, https://www.witcc.edu/about/board/board-policies, https://www.witcc.edu/about/employees, https://www.witcc.edu/maps and https://www.witcc.edu/about/history and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Error: Newer chat widget found - loading that instead!”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel and 1 more (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 18 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.