Website review, no card needed
clcillinois.edu website review
Visit site (opens in a new tab)Reviewed 2 November 202632 issues · 82 checks
This review found 32 issues worth fixing on clcillinois.edu, 4 of them high impact, across 82 checks. The most urgent: largest Contentful Paint: 8.9 s. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 851 ms |
| May 23, 2026 | 859 ms |
| May 30, 2026 | 857 ms |
| Jun 6, 2026 | 857 ms |
| Jun 13, 2026 | 830 ms |
| Jun 20, 2026 | 828 ms |
| Jun 27, 2026 | 842 ms |
| Jul 4, 2026 | 851 ms |
| Jul 11, 2026 | 859 ms |
| Jul 18, 2026 | 857 ms |
| Jul 25, 2026 | 854 ms |
| Aug 1, 2026 | 850 ms |
| Aug 8, 2026 | 845 ms |
| Aug 15, 2026 | 858 ms |
| Aug 22, 2026 | 856 ms |
| Aug 29, 2026 | 864 ms |
| Sep 5, 2026 | 877 ms |
| Sep 12, 2026 | 870 ms |
| Sep 19, 2026 | 880 ms |
| Sep 26, 2026 | 869 ms |
| Oct 3, 2026 | 862 ms |
| Oct 10, 2026 | 869 ms |
| Oct 17, 2026 | 872 ms |
| Oct 24, 2026 | 860 ms |
| Oct 31, 2026 | 836 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 78 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 77 ms |
| Jun 6, 2026 | 76 ms |
| Jun 13, 2026 | 76 ms |
| Jun 20, 2026 | 77 ms |
| Jun 27, 2026 | 78 ms |
| Jul 4, 2026 | 79 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 78 ms |
| Aug 29, 2026 | 78 ms |
| Sep 5, 2026 | 78 ms |
| Sep 12, 2026 | 78 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 80 ms |
| Oct 10, 2026 | 80 ms |
| Oct 17, 2026 | 81 ms |
| Oct 24, 2026 | 81 ms |
| Oct 31, 2026 | 80 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
500 ms · 1.1 MB13 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
657 KiBAbout 657 KiB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hotjar and youvisit.com and others), adding 734 KiB and 571 ms of main-thread time.
Use efficient cache lifetimes
372 KiB9 files are served with short cache lifetimes, so returning visitors download them again (372 KiB).
Google Tag Manager adds 335 ms
335 msGoogle Tag Manager costs a phone 335 ms of main-thread work and 360 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 248 ms. During a long task the page ignores taps.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 746 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Study one of 9 skilled trades at College of Lake County”.
Time to Interactive: 12.1 s
12.1 sThe page becomes fully interactive after 12.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.345
0.345The layout shifts by 0.345 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 305 ms
305 msScripts block taps and scrolling for 305 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.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 78 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 74 ms
74 msReal visitors wait 74 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 483 ms
483 msReal visitors wait 483 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Speed Index: 2.7 s
2.7 sVisually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
Page weight: 3.5 MB in 79 requests
3.5 MBYour homepage downloads 3.5 MB in 79 requests on a phone: images 1.9 MB (32), scripts 1.2 MB (19) and other files 251 KiB (15). Under 2 MB keeps phones on slow connections fast.
15 images in older formats
15 images (1.7 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.
15 images below the first screen load straight away
15 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
299 KiB3 images are downloaded at several times the size a phone draws them, for example hsi-logo-rectangle-white-noclc.png at 2,550 px wide, shown at 68 px. Resized copies would save about 299 KiB.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “College of Lake County | Classes, Degrees & Career Paths - College of Lake County”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
84 internal links, 12 external
The homepage links to 84 pages on clcillinois.edu and 12 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “College of Lake County is a community college with 5 locations in Lake County, IL. Find programs for future students, b…”.
One H1 headline
Your main headline reads: “Connect to your future”.
Canonical URL set
The canonical URL is https://www.clcillinois.edu/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.clcillinois.edu/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://www.clcillinois.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.
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 (737 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.clcillinois.edu/programs-and-classes and https://www.clcillinois.edu/find-your-path all use the title “Programs & Classes - College of Lake County”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.clcillinois.edu/redirects/student-portal has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.clcillinois.edu/programs-and-classes and https://www.clcillinois.edu/find-your-path use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.clcillinois.edu/find-your-path, whose canonical is https://www.clcillinois.edu/programs-and-classes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://www.clcillinois.edu/redirects/student-portal has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://trck.youvisit.com/page/120232.png?embed=217933609641661569&pageSessionId=7fba8495-3556-432c-8422-386f79d46f49&source=vhost.
8 small tap targets
8 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 721 words of copy
The homepage carries about 721 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Apply now”.
11 calls to action
The homepage has 11 calls to action, for example “Apply now”, “Get Started” and “Apply Now”.
Social proof on the page
Social proof on the homepage: 3 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 3 of them by other companies (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.
15 other companies contacted
Loading the homepage contacts 15 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 clcillinois.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Company
- Employees
- 1,434
- Founded
- 1967
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on clcillinois.edu, including 12 speed issues, 3 SEO issues and 1 conversion gap. 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.