Website review, no card needed
capital.edu website review
Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 90 checks
This review found 41 issues worth fixing on capital.edu, 19 of them high impact, across 90 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 321 ms |
| May 16, 2026 | 323 ms |
| May 23, 2026 | 324 ms |
| May 30, 2026 | 325 ms |
| Jun 6, 2026 | 334 ms |
| Jun 13, 2026 | 334 ms |
| Jun 20, 2026 | 334 ms |
| Jun 27, 2026 | 333 ms |
| Jul 4, 2026 | 325 ms |
| Jul 11, 2026 | 332 ms |
| Jul 18, 2026 | 333 ms |
| Jul 25, 2026 | 335 ms |
| Aug 1, 2026 | 332 ms |
| Aug 8, 2026 | 335 ms |
| Aug 15, 2026 | 335 ms |
| Aug 22, 2026 | 331 ms |
| Aug 29, 2026 | 328 ms |
| Sep 5, 2026 | 325 ms |
| Sep 12, 2026 | 314 ms |
| Sep 19, 2026 | 321 ms |
| Sep 26, 2026 | 325 ms |
| Oct 3, 2026 | 328 ms |
| Oct 10, 2026 | 328 ms |
| Oct 17, 2026 | 301 ms |
| Oct 24, 2026 | 288 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.8 s
1.7 s
2.5 s
3.3 s
4.1 s
5.0 s
5.8 s
6.6 s
Speed
Use efficient cache lifetimes
12.5 s · 7.0 MB60 files are served with short cache lifetimes, so returning visitors download them again (7.0 MB).
Improve image delivery
10.4 s · 5.2 MB18 images could be 5.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.4 s faster on a phone.
Reduce unused JavaScript
1.4 s · 648 KiBAbout 648 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 1.2 MB 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: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
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 2.0 MB and 2.1 s of main-thread time.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 340 ms. During a long task the page ignores taps.
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
youvisit.com adds 189 ms
189 msyouvisit.com costs a phone 189 ms of main-thread work and 491 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
190 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
40 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 32.0 s
32.0 sYour largest element takes 32.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Open House Campus Min”.
Time to Interactive: 40.9 s
40.9 sThe page becomes fully interactive after 40.9 s. Good is under 3.8 s.
Speed Index: 13.4 s
13.4 sVisually, the page fills in at 13.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 777 ms
777 msScripts block taps and scrolling for 777 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 321 ms to 288 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 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: 739 ms
739 msReal visitors wait 739 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 9.1 MB in 141 requests
9.1 MBYour homepage downloads 9.1 MB in 141 requests on a phone: images 6.9 MB (44), scripts 1.7 MB (44) and fonts 254 KiB (3). Under 2 MB keeps phones on slow connections fast.
14 images far larger than shown
3.6 MB14 images are downloaded at several times the size a phone draws them, for example male-and-female-standing-in-front-of-mees.jpg at 2,000 px wide, shown at 358 px. Resized copies would save about 3.6 MB.
5 images over 500 KB
5 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.
15 images in older formats
15 images (5.4 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.
11 images below the first screen load straight away
11 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.59 g of CO₂e: 311.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Main landmark should not be contained in another landmark (1 element)
Main 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 main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 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.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (261 characters)
Your meta description is 261 characters; Google truncates after about 160, so the end of your pitch is cut.
115 internal links, 27 external
The homepage links to 115 pages on capital.edu and 27 external pages.
6 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Capital University | Capital University, Columbus Ohio”.
Canonical URL set
The canonical URL is https://www.capital.edu/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness, Organization and WebSite.
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.capital.edu/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (789 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.capital.edu/llms.txt (17 KiB, 116 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://www.capital.edu/admission-aid/schedule-a-visit, https://www.capital.edu/about/mission-and-vision, https://www.capital.edu/about/leadership, https://www.capital.edu/about/facts-and-figures, https://www.capital.edu/about/capital-stories and https://www.capital.edu/about/maps-and-locations and 5 others 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 93 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
2 broken images
2 images failed to load on a phone, for example https://trck.youvisit.com/embed/60750.png?embed_type=immersive&w=358&h=300&top=7554&left=16&pagewidth=390&pageHeight=10940&screenWidth=390&screenHeight=844&hasImgtag=false&embed=635431029939577235&ab=.
5 small tap targets
5 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 690 words of copy
The homepage carries about 690 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” and “Request Info”.
17 calls to action
The homepage has 17 calls to action, for example “Apply Now”, “Request Info” and “Schedule a Visit”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
34 other companies contacted
Loading the homepage contacts 34 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 capital.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Oarnet
Hiring
- Hiring
- 56 open roles
- Teams
- Operations Core (9), Compliance Group (4), CEO Office (3), Security - AppSec (3)
- Job board
- lever
Company
- Employees
- 605
- Founded
- 1830
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on capital.edu, including 17 speed issues, 2 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.