Website review, no card needed

atsu.edu logo

atsu.edu website review

Visit site (opens in a new tab)Reviewed 29 October 202644 issues · 84 checks

This review found 44 issues worth fixing on atsu.edu, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
5.2 s4.3 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.4 s
May 16, 20264.6 s
May 23, 20264.6 s
May 30, 20264.7 s
Jun 6, 20264.9 s
Jun 13, 20265.0 s
Jun 20, 20265.1 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20264.8 s
Jul 18, 20264.9 s
Jul 25, 20264.9 s
Aug 1, 20264.8 s
Aug 8, 20264.7 s
Aug 15, 20264.7 s
Aug 22, 20264.6 s
Aug 29, 20264.6 s
Sep 5, 20264.6 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.4 s
Oct 17, 20264.5 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
576 ms305 msMay 9Oct 24545 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026336 ms
May 16, 2026355 ms
May 23, 2026355 ms
May 30, 2026355 ms
Jun 6, 2026367 ms
Jun 13, 2026371 ms
Jun 20, 2026381 ms
Jun 27, 2026371 ms
Jul 4, 2026371 ms
Jul 11, 2026379 ms
Jul 18, 2026392 ms
Jul 25, 2026408 ms
Aug 1, 2026407 ms
Aug 8, 2026406 ms
Aug 15, 2026404 ms
Aug 22, 2026403 ms
Aug 29, 2026408 ms
Sep 5, 2026405 ms
Sep 12, 2026413 ms
Sep 19, 2026420 ms
Sep 26, 2026408 ms
Oct 3, 2026424 ms
Oct 10, 2026441 ms
Oct 17, 2026481 ms
Oct 24, 2026545 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

Full-page screenshot of atsu.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atsu.edu at 0.6 s0.6 s
  2. atsu.edu at 1.1 s1.1 s
  3. atsu.edu at 1.6 s1.6 s
  4. atsu.edu at 2.2 s2.2 s
  5. atsu.edu at 2.7 s2.7 s
  6. atsu.edu at 3.3 s3.3 s
  7. atsu.edu at 3.8 s3.8 s
  8. atsu.edu at 4.4 s4.4 s

Speed

14 to fix31
  • Reduce unused JavaScript

    5.8 s · 1.1 MB

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

  • Improve image delivery

    2.3 s · 1.3 MB

    20 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Render-blocking requests

    2.6 s

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

  • Use efficient cache lifetimes

    1.6 s · 835 KiB

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 2.6 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, Facebook and Google CDN and others), adding 2.3 MB and 1.9 s of main-thread time.

  • Google Tag Manager adds 839 ms

    839 ms

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

    450 ms · 234 KiB

    About 234 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Font display

    450 ms

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

  • Google CDN adds 318 ms

    318 ms

    Google CDN costs a phone 318 ms of main-thread work and 736 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.

  • Facebook adds 349 ms

    349 ms

    Facebook costs a phone 349 ms of main-thread work and 364 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

    300 ms · 40 KiB

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

  • 19 long tasks on the main thread

    19 long tasks block the main thread while loading, the longest for 258 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.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

11 to fix67
  • 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.

  • First Contentful Paint: 10.7 s

    10.7 s

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

  • Largest Contentful Paint: 27.8 s

    27.8 s

    Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 29.5 s

    29.5 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Total Blocking Time: 674 ms

    674 ms

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

  • Real-user INP: 380 ms

    380 ms

    Real visitors wait 380 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 48% slower for real visitors

    +48%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 336 ms to 545 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user TTFB: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.171

    0.171

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

  • 23 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

Images and page weight

2 to fix63
  • Page weight: 14.2 MB in 166 requests

    14.2 MB

    Your homepage downloads 14.2 MB in 166 requests on a phone: media 7.5 MB (3), images 2.8 MB (42) and scripts 2.5 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 20 images below the first screen load straight away

    20 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (338 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.

  • About 4.0 g of CO₂ per visit

    4.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.02 g of CO₂e: 482.5 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 fix100
  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 9285
  • 2 H1 headlines

    There are 2 <h1> headlines (“2025 Commencement Ceremonies” and “Begin your journey at ATSU”). One clear main headline is easier for people and search engines.

  • Meta description is long (210 characters)

    Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 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.

  • 234 internal links, 30 external

    The homepage links to 234 pages on atsu.edu and 30 external pages.

5 checks passed
  • Title: 57 characters

    Your title is a healthy 57 characters: “A.T. Still University | Osteopathic Medical School | ATSU”.

  • Canonical URL set

    The canonical URL is https://www.atsu.edu/.

  • Structured data in place

    Structured data found: CollegeOrUniversity.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.atsu.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://www.atsu.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,846 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 2 pages share a title

    https://www.atsu.edu/about-atsu/campus-locations and https://www.atsu.edu/about-atsu/campuses all use the title “Campus Locations”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.atsu.edu/faculty-staff-profiles and https://www.atsu.edu/museum-of-osteopathic-medicine have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.atsu.edu/about-atsu/campus-locations, https://www.atsu.edu/alumni, https://www.atsu.edu/contact-atsu, https://www.atsu.edu/apply-to-atsu, https://www.atsu.edu/about-atsu and https://www.atsu.edu/about-atsu/history and 4 others use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.atsu.edu/accreditation, whose canonical is https://www.atsu.edu/about-atsu/accreditation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.atsu.edu/about-atsu/campus-locations, https://www.atsu.edu/apply-to-atsu, https://www.atsu.edu/about-atsu, https://www.atsu.edu/about-atsu/history, https://www.atsu.edu/accreditation and https://www.atsu.edu/about-atsu/campuses and 3 others have 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 109 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5984074&tm=gtm002&Ver=2&mid=783b3224-5059-4a3c-bdb6-aaec66e3e5b7&bo=1&sid=e0d6a130d3b211f1824ccf6f9cdc95fa&vid=e0d6c1a0d3b211f18f901f2dd83c2f1b&vids=1&msclkid=N&pi=918.

  • 4 JavaScript errors while loading

    4 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

    97 of 109 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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,210 words of copy

    The homepage carries about 1,210 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: “Contact Us” and “Schedule a tour”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact atsu”, “Apply” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 4 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

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 5 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.

  • 20 cookies set on arrival

    20

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

  • 48 other companies contacted

    Loading the homepage contacts 48 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 atsu.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
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on atsu.edu, including 25 speed issues, 4 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