Website review, no card needed

fairmontstate.edu logo

fairmontstate.edu website review

Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 86 checks

This review found 38 issues worth fixing on fairmontstate.edu, 9 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
1.5 s1.1 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
162 ms107 msMay 30Nov 14155 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026118 ms
Jun 6, 2026117 ms
Jun 13, 2026113 ms
Jun 20, 2026119 ms
Jun 27, 2026117 ms
Jul 4, 2026115 ms
Jul 11, 2026118 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026117 ms
Aug 8, 2026117 ms
Aug 15, 2026126 ms
Aug 22, 2026130 ms
Aug 29, 2026139 ms
Sep 5, 2026145 ms
Sep 12, 2026145 ms
Sep 19, 2026150 ms
Sep 26, 2026146 ms
Oct 3, 2026147 ms
Oct 10, 2026150 ms
Oct 17, 2026149 ms
Oct 24, 2026156 ms
Oct 31, 2026153 ms
Nov 7, 2026151 ms
Nov 14, 2026155 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 fairmontstate.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fairmontstate.edu at 0.4 s0.4 s
  2. fairmontstate.edu at 0.8 s0.8 s
  3. fairmontstate.edu at 1.1 s1.1 s
  4. fairmontstate.edu at 1.5 s1.5 s
  5. fairmontstate.edu at 1.9 s1.9 s
  6. fairmontstate.edu at 2.3 s2.3 s
  7. fairmontstate.edu at 2.6 s2.6 s
  8. fairmontstate.edu at 3.0 s3.0 s

Speed

11 to fix51
  • Use efficient cache lifetimes

    2.6 s · 2.1 MB

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

  • Reduce unused JavaScript

    2.3 s · 330 KiB

    About 330 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Improve image delivery

    600 ms · 3.6 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Snapchat and others), adding 4.4 MB and 1.1 s of main-thread time.

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 520 ms

    520 ms

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

  • juicer.io adds 70 ms

    70 ms

    juicer.io costs a phone 70 ms of main-thread work and 3.3 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.

  • Legacy JavaScript

    300 ms · 28 KiB

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

  • Render-blocking requests

    300 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Main-thread work: 2.3 s

    A phone's processor spends 2.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,680 HTML elements

    The page has 1,680 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 41 KiB

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

  • Font display

    50 ms

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

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

    3 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Largest Contentful Paint: 17.7 s

    17.7 s

    Your largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A group of students walking across campus”.

  • Time to Interactive: 18.0 s

    18.0 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user INP: 208 ms

    208 ms

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

  • Real-user CLS: 0.20

    0.20

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

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

    +30%

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

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

  • Real-user TTFB: 801 ms

    801 ms

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

  • Total Blocking Time: 366 ms

    366 ms

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

  • 5 images without width and height

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

3 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix40
  • Page weight: 6.6 MB in 148 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 148 requests on a phone: images 4.8 MB (70), scripts 1.0 MB (27) and fonts 574 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 21 images far larger than shown

    1.4 MB

    21 images are downloaded at several times the size a phone draws them, for example 38507818 at 1,439 px wide, shown at 338 px. Resized copies would save about 1.4 MB.

  • 34 images in older formats

    34 images (4.5 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.

  • 2 images below the first screen load straight away

    2 images further down the page (148 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.86 g

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

Accessibility

1 to fixGoogle 10099
  • 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.

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9279
  • Title is short (25 characters)

    Your title is only 25 characters: “Fairmont State University”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Fall 2027 Application is now Open” and “Welcome Home”). One clear main headline is easier for people and search engines.

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 202 internal links, 26 external

    The homepage links to 202 pages on fairmontstate.edu and 26 external pages.

4 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Take flight and make your dreams a reality with a degree from Fairmont State University, where passion and hard work le…”.

  • Canonical URL set

    The canonical URL is https://www.fairmontstate.edu/default.aspx.

  • 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.fairmontstate.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.fairmontstate.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,861 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 11 pages without a meta description

    https://www.fairmontstate.edu/apply.aspx, https://www.fairmontstate.edu/admissions/request-info.aspx, https://www.fairmontstate.edu/contact/default.aspx, https://www.fairmontstate.edu/about/president/default.aspx, https://www.fairmontstate.edu/about/board-governors/default.aspx and https://www.fairmontstate.edu/about/institutional-research-effectiveness/accreditation/default.aspx 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 165 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 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is 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 “Manifest: Line: 1, column: 1, Syntax error.”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

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

    The homepage carries about 665 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY NOW”.

  • 15 calls to action

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

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 46 testimonial or review blocks and “3200+ Students”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 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
  • 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 Clarity 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.

  • 10 cookies set on arrival

    10

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 fairmontstate.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 Tag Manager
Hosting
Total Uptime Technologies, LLC

Company

Employees
578
Founded
1865
Headquarters
Fairmont

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on fairmontstate.edu, including 23 speed issues, 5 SEO issues and 1 conversion gap. 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