Website review, no card needed
elgin.edu website review
Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 88 checks
This review found 33 issues worth fixing on elgin.edu, 13 of them high impact, across 88 checks. The most urgent: cloudflare CDN adds 2.0 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 708 ms |
| May 16, 2026 | 692 ms |
| May 23, 2026 | 699 ms |
| May 30, 2026 | 709 ms |
| Jun 6, 2026 | 724 ms |
| Jun 13, 2026 | 744 ms |
| Jun 20, 2026 | 731 ms |
| Jun 27, 2026 | 720 ms |
| Jul 4, 2026 | 716 ms |
| Jul 11, 2026 | 716 ms |
| Jul 18, 2026 | 732 ms |
| Jul 25, 2026 | 740 ms |
| Aug 1, 2026 | 732 ms |
| Aug 8, 2026 | 731 ms |
| Aug 15, 2026 | 723 ms |
| Aug 22, 2026 | 713 ms |
| Aug 29, 2026 | 734 ms |
| Sep 5, 2026 | 748 ms |
| Sep 12, 2026 | 744 ms |
| Sep 19, 2026 | 760 ms |
| Sep 26, 2026 | 727 ms |
| Oct 3, 2026 | 717 ms |
| Oct 10, 2026 | 744 ms |
| Oct 17, 2026 | 761 ms |
| Oct 24, 2026 | 781 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 134 ms |
| May 16, 2026 | 132 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 164 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 175 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
Speed
Cloudflare CDN adds 2.0 s
2.0 sCloudflare CDN costs a phone 2.0 s of main-thread work and 28 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 34
34/100Your mobile performance score is 34 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,498 HTML elements
The page has 6,498 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
750 ms · 14.8 MB30 files are served with short cache lifetimes, so returning visitors download them again (14.8 MB).
8 third-party services on the page
8 third-party services load with your homepage (Cloudflare CDN, Google Tag Manager and FontAwesome CDN and others), adding 1.2 MB and 4.0 s of main-thread time.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 3.2 s. During a long task the page ignores taps.
Improve image delivery
100 ms · 1.1 MB7 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 100 ms faster on a phone.
Reduce unused JavaScript
460 ms · 423 KiBAbout 423 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.
Google Tag Manager adds 793 ms
793 msGoogle Tag Manager costs a phone 793 ms of main-thread work and 539 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.
FontAwesome CDN adds 344 ms
344 msFontAwesome CDN costs a phone 344 ms of main-thread work and 44 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.
osano.com adds 278 ms
278 msosano.com costs a phone 278 ms of main-thread work and 110 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.
Reduce unused CSS
150 ms · 53 KiBAbout 53 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.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 65 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Campus of Elgin Community College”.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 302 ms
302 msReal visitors wait 302 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 134 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 329 ms
329 msReal visitors wait 329 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 18.6 MB in 107 requests
18.6 MBYour homepage downloads 18.6 MB in 107 requests on a phone: media 14.4 MB (1), images 2.0 MB (23) and scripts 1.8 MB (42). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
234 KiB3 images are downloaded at several times the size a phone draws them, for example atd-badge-leader-college-logo.png at 1,598 px wide, shown at 177 px. Resized copies would save about 234 KiB.
4 images below the first screen load straight away
4 images further down the page (270 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (156 KiB) is 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.
About 5.3 g of CO₂ per visit
5.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.27 g of CO₂e: 632.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 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.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
59 internal links, 18 external
The homepage links to 59 pages on elgin.edu and 18 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “At Elgin Community College, we commit to student success and empower students to reach their full potential through our…”.
One H1 headline
Your main headline reads: “Home”.
Title: 41 characters
Your title is a healthy 41 characters: “Elgin.edu | Elgin Community College (ECC)”.
Canonical URL set
The canonical URL is https://elgin.edu/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://elgin.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.
3 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 (514 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://elgin.edu/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://elgin.edu/directory and https://elgin.edu/news use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://elgin.edu/directory 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 47 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
2 broken images
2 images failed to load on a phone, for example https://ad.ipredictive.com/d/track/event?upid=110747&url=https%3A%2F%2Felgin.edu%2F&cache_buster=[timestamp]&ps=2.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'appendChild')”.
2 checks passed
Tap targets are thumb-sized
24 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 440 words of copy
The homepage carries about 440 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request Information” and “Apply Now”.
5 calls to action
The homepage has 5 calls to action, for example “Request Information”, “Apply Now” and “Register”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and TikTok Pixel (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) loads with the page.
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 elgin.edu, 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 | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on elgin.edu, including 21 speed issues, 2 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.