Website review, no card needed

uis.edu logo

uis.edu website review

Visit site (opens in a new tab)Reviewed 27 October 202636 issues · 84 checks

This review found 36 issues worth fixing on uis.edu, 16 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of uis.edu (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uis.edu at 0.5 s0.5 s
  2. uis.edu at 1.1 s1.1 s
  3. uis.edu at 1.6 s1.6 s
  4. uis.edu at 2.1 s2.1 s
  5. uis.edu at 2.6 s2.6 s
  6. uis.edu at 3.2 s3.2 s
  7. uis.edu at 3.7 s3.7 s
  8. uis.edu at 4.2 s4.2 s

Speed

14 to fix11
  • Render-blocking requests

    14.2 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 14.2 s.

  • Reduce unused JavaScript

    7.3 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.3 s faster on a phone.

  • Use efficient cache lifetimes

    2.3 s · 2.0 MB

    23 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • Minify JavaScript

    3.5 s · 633 KiB

    633 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    3.1 s · 592 KiB

    About 592 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Mobile performance score: 11

    11/100

    Your mobile performance score is 11 (desktop: 33). 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.9 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, PageSense and rlets.com and others), adding 1,019 KiB and 1.8 s of main-thread time.

  • Improve image delivery

    350 ms · 1.5 MB

    14 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Google Tag Manager adds 675 ms

    675 ms

    Google Tag Manager costs a phone 675 ms of main-thread work and 504 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.

  • Legacy JavaScript

    550 ms · 86 KiB

    Polyfills for old browsers add 86 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 583 ms. During a long task the page ignores taps.

  • PageSense adds 422 ms

    422 ms

    PageSense costs a phone 422 ms of main-thread work and 95 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.

  • rlets.com adds 261 ms

    261 ms

    rlets.com costs a phone 261 ms of main-thread work and 62 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.

  • Document request latency

    61 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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: 46 ms

    46 ms

    Your server sent the HTML in 46 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix13
  • First Contentful Paint: 14.3 s

    14.3 s

    The first text or image appears after 14.3 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 39.3 s

    39.3 s

    Your largest element takes 39.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use Cookies on this site to enhance your experience and …”.

  • Time to Interactive: 39.4 s

    39.4 s

    The page becomes fully interactive after 39.4 s. Good is under 3.8 s.

  • Speed Index: 14.3 s

    14.3 s

    Visually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.464

    0.464

    The layout shifts by 0.464 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

1 to fix70
  • Page weight: 7.9 MB in 149 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 149 requests on a phone: scripts 3.5 MB (51), images 2.2 MB (30) and fonts 1.5 MB (11). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (358 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.

  • 1 image below the first screen load straight away

    1 image further down the page (145 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.24 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.24 g of CO₂e: 268.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10099
  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9295
  • 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 crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 165 internal links, 22 external

    The homepage links to 165 pages on uis.edu and 22 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Welcome to the University of Illinois Springfield (UIS), a top-tier public university offering innovative academic prog…”.

  • One H1 headline

    Your main headline reads: “Visit Campus”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “University of Illinois Springfield”.

  • Canonical URL set

    The canonical URL is https://uis.edu/.

  • Structured data in place

    Structured data found: CollegeOrUniversity and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://uis.edu/sitemap.xml.

AI search readiness

1 to fix88
  • 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://uis.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 (1,171 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://uis.edu/apply and https://uis.edu/admission-aid/how-apply all use the title “Apply”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://uis.edu/apply and https://uis.edu/admission-aid/how-apply use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://uis.edu/admission-aid/how-apply, whose canonical is https://uis.edu/apply. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 116 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.

  • 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

4 to fixGoogle 6574
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134001416&Ver=2&mid=2c440014-5e87-44ee-a3e8-63641be5e26a&bo=1&sid=2ecd1470d22011f1a095b9fd714b3bd1&vid=2ecd1f50d22011f1ab4b9da549e58897&vids=1&msclkid=N&pi=918639831&l.

  • 10 third-party cookies

    10 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: H is not a constructor”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    45 of 46 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 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 990 words of copy

    The homepage carries about 990 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” and “Inquire”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Apply”, “How to Apply” and “Request Info”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 36 other companies contacted

    Loading the homepage contacts 36 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 uis.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
React
Analytics
Google Tag Manager
Hosting
UIS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on uis.edu, including 21 speed issues, 2 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25