Website review, no card needed
columbusstate.edu website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 79 checks
This review found 33 issues worth fixing on columbusstate.edu, 6 of them high impact, across 79 checks. The most urgent: page weight: 19.7 MB in 60 requests. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 140 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 159 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 175 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 200 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 204 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 181 ms |
| Oct 17, 2026 | 175 ms |
| Oct 24, 2026 | 163 ms |
| Oct 31, 2026 | 158 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.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.5 s
Speed
Use efficient cache lifetimes
15.8 MB11 files are served with short cache lifetimes, so returning visitors download them again (15.8 MB).
Improve image delivery
2.2 MB23 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 84
84/100Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused JavaScript
643 KiBAbout 643 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 (Azure Web Services, Siteimprove and Adobe TypeKit and others), adding 2.1 MB and 402 ms of main-thread time.
Reduce unused CSS
563 KiBAbout 563 KiB of CSS is downloaded but never applied on this page.
Azure Web Services adds 369 ms
369 msAzure Web Services costs a phone 369 ms of main-thread work and 1.6 MB 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 376 ms. During a long task the page ignores taps.
Adobe TypeKit adds 0 ms
0 msAdobe TypeKit costs a phone 0 ms of main-thread work and 403 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 537 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
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.
Real-user INP: 779 ms
779 msReal visitors wait 779 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Time to Interactive: 28.7 s
28.7 sThe page becomes fully interactive after 28.7 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 203 ms
203 msScripts block taps and scrolling for 203 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 140 ms to 158 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-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 574 ms
574 msReal visitors wait 574 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “APPLY FOR FREE IN NOVEMBER!”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 19.7 MB in 60 requests
19.7 MBYour homepage downloads 19.7 MB in 60 requests on a phone: media 13.5 MB (2), images 3.3 MB (30) and scripts 1.2 MB (6). Under 2 MB keeps phones on slow connections fast.
19 images below the first screen load straight away
19 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (831 KiB) 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.
7 images far larger than shown
277 KiB7 images are downloaded at several times the size a phone draws them, for example 2026.10.alumni.awards.news.image.jpg at 1,200 px wide, shown at 334 px. Resized copies would save about 277 KiB.
About 5.6 g of CO₂ per visit
5.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.59 g of CO₂e: 671.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 0 failed. 3 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.
Meta description is long (557 characters)
Your meta description is 557 characters; Google truncates after about 160, so the end of your pitch is cut.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
35 internal links, 27 external
The homepage links to 35 pages on columbusstate.edu and 27 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Apply for Free in November!”.
Title: 58 characters
Your title is a healthy 58 characters: “Columbus State University Home - Columbus State University”.
Canonical URL set
The canonical URL is https://www.columbusstate.edu/index.php.
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://www.columbusstate.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.columbusstate.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 (785 words), so crawlers that don't run JavaScript still read it.
Other pages
14 links to non-canonical URLs
Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://www.columbusstate.edu/degrees-and-programs, whose canonical is https://www.columbusstate.edu/degrees-and-programs/index.php. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages share a meta description
https://www.columbusstate.edu/life-at-csu and https://www.columbusstate.edu/life-at-csu/columbus-ga.php use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.columbusstate.edu/life-at-csu/columbus-ga.php has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
32 of 33 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.
Thin social proof
Social proof on the homepage: 17 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 1,115 words of copy
The homepage carries about 1,115 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Apply Now”.
8 calls to action
The homepage has 8 calls to action, for example “Apply Now”, “Learn More” and “Apply”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 3 phone links 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 cookies set on arrival
5Opening the homepage sets 5 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 columbusstate.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
- Tailwind CSS
- Hosting
- Peachnet
Company
- Employees
- 1,109
- Founded
- 1958
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 columbusstate.edu, including 16 speed issues, 3 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.