Website review, no card needed
csi.edu website review
Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 83 checks
This review found 31 issues worth fixing on csi.edu, 9 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 981 ms |
| Jun 6, 2026 | 971 ms |
| Jun 13, 2026 | 928 ms |
| Jun 20, 2026 | 917 ms |
| Jun 27, 2026 | 931 ms |
| Jul 4, 2026 | 925 ms |
| Jul 11, 2026 | 929 ms |
| Jul 18, 2026 | 949 ms |
| Jul 25, 2026 | 927 ms |
| Aug 1, 2026 | 935 ms |
| Aug 8, 2026 | 926 ms |
| Aug 15, 2026 | 945 ms |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 993 ms |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 985 ms |
| Oct 17, 2026 | 951 ms |
| Oct 24, 2026 | 923 ms |
| Oct 31, 2026 | 913 ms |
| Nov 7, 2026 | 944 ms |
| Nov 14, 2026 | 963 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 85 ms |
| Jul 18, 2026 | 85 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 87 ms |
| Nov 7, 2026 | 87 ms |
| Nov 14, 2026 | 86 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
Use efficient cache lifetimes
6.5 s · 1.7 MB24 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Improve image delivery
2.0 s · 559 KiB7 images could be 559 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Reduce unused JavaScript
1.5 s · 240 KiBAbout 240 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.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 219 ms
219 msGoogle Tag Manager costs a phone 219 ms of main-thread work and 492 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 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Clarity and Google Analytics and others), adding 624 KiB and 298 ms of main-thread time.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 310 ms of it running JavaScript. That is comfortably low.
Server response: 54 ms
54 msYour server sent the HTML in 54 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.5 s
15.5 sYour largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “fall colors on the trees that cover the roadway coming into…”.
Time to Interactive: 15.5 s
15.5 sThe page becomes fully interactive after 15.5 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 90 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 691 ms
691 msReal visitors wait 691 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).
Total Blocking Time: 42 ms
42 msScripts block the page for only 42 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
csi-impactbanner-2026-5.jpg weighs 501 KiB. On a phone connection a single image that size takes seconds.
Page weight: 2.3 MB in 46 requests
2.3 MBYour homepage downloads 2.3 MB in 46 requests on a phone: images 1.3 MB (15), scripts 617 KiB (14) and fonts 333 KiB (4). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.2 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 far larger than shown
194 KiB1 image is downloaded at several times the size a phone draws it, for example fall-campus-impact-1.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 194 KiB.
5 images below the first screen load straight away
5 images further down the page (325 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 2 failed. 1 more 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.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
171 internal links, 92 external
The homepage links to 171 pages on csi.edu and 92 external pages.
6 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “Find affordable degrees, small classes, and personalized support to reach your goals at the College of Southern Idaho.”.
One H1 headline
Your main headline reads: “ENROLL FOR SPRING CLASSES”.
Title: 31 characters
Your title is a healthy 31 characters: “CSI - College of Southern Idaho”.
Canonical URL set
The canonical URL is https://www.csi.edu/default.aspx.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.csi.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.csi.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 (975 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://www.csi.edu/contact/default.aspx, https://www.csi.edu/admissions/visit-csi/default.aspx, https://www.csi.edu/admissions/default.aspx, https://www.csi.edu/registrar/courses.aspx, https://www.csi.edu/online/default.aspx and https://www.csi.edu/off-campus/default.aspx have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.
6 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.
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
6 small tap targets
6 of 18 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 “Loading the script 'site://www.csi.edu/_common/_files/js/all-pages/premion-pixels.js' violates the following Content Se…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 387 words of copy
The homepage carries about 387 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: “GET STARTED”.
16 calls to action
The homepage has 16 calls to action, for example “APPLY”, “CONTACT” and “Apply”.
1 short form
A short form (1 field at most) is right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
11 other companies contacted
Loading the homepage contacts 11 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 csi.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
- Hosting
- Azure
Company
- Founded
- 1965
- Headquarters
- Twin Falls
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on csi.edu, including 12 speed issues, 4 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.