Website review, no card needed

edgewood.edu logo

edgewood.edu website review

Visit site (opens in a new tab)Reviewed 31 October 202636 issues · 81 checks

This review found 36 issues worth fixing on edgewood.edu, 12 of them high impact, across 81 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.5 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
202 ms143 msMay 9Oct 24193 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026150 ms
May 16, 2026152 ms
May 23, 2026150 ms
May 30, 2026154 ms
Jun 6, 2026158 ms
Jun 13, 2026163 ms
Jun 20, 2026167 ms
Jun 27, 2026161 ms
Jul 4, 2026156 ms
Jul 11, 2026155 ms
Jul 18, 2026154 ms
Jul 25, 2026161 ms
Aug 1, 2026163 ms
Aug 8, 2026165 ms
Aug 15, 2026176 ms
Aug 22, 2026182 ms
Aug 29, 2026193 ms
Sep 5, 2026194 ms
Sep 12, 2026193 ms
Sep 19, 2026190 ms
Sep 26, 2026189 ms
Oct 3, 2026191 ms
Oct 10, 2026194 ms
Oct 17, 2026195 ms
Oct 24, 2026193 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 edgewood.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. edgewood.edu at 1.2 s1.2 s
  2. edgewood.edu at 2.4 s2.4 s
  3. edgewood.edu at 3.7 s3.7 s
  4. edgewood.edu at 4.9 s4.9 s
  5. edgewood.edu at 6.1 s6.1 s
  6. edgewood.edu at 7.3 s7.3 s
  7. edgewood.edu at 8.6 s8.6 s
  8. edgewood.edu at 9.8 s9.8 s

Speed

9 to fix39
  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 39

    39/100

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

  • Improve image delivery

    200 ms · 1.7 MB

    3 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 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 TikTok and others), adding 1.6 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 834 KiB

    About 834 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 994 ms

    994 ms

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

  • Main-thread work: 3.0 s

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

  • 11 long tasks on the main thread

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

  • Google CDN adds 130 ms

    130 ms

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

  • Use efficient cache lifetimes

    205 KiB

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

  • Reduce unused CSS

    150 ms · 50 KiB

    About 50 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.

  • Legacy JavaScript

    150 ms · 31 KiB

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.

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

9 to fix100
  • 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: 10.7 s

    10.7 s

    Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “two female students sitting and talking to each other”. Most of its time is resource load delay (6.0 s).

  • Speed Index: 15.0 s

    15.0 s

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

  • Time to Interactive: 16.7 s

    16.7 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

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

    +28%

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

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

    +18%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 192 ms

    192 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

5 to fix18
  • Page weight: 4.3 MB in 94 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 94 requests on a phone: images 1.9 MB (12), scripts 1.8 MB (34) and fonts 522 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Homepage-Hero_Fall-2026.jpg weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1,012 KiB

    2 images are downloaded at several times the size a phone draws them, for example Homepage-Hero_Fall-2026.jpg at 1,600 px wide, shown at 350 px. Resized copies would save about 1,012 KiB.

  • 3 images in older formats

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

  • 1 image below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.21 g

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

Accessibility

3 to fixGoogle 9997
  • All page content should be contained by landmarks (14 elements)

    All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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 28 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is short (26 characters)

    Your title is only 26 characters: “Home - Edgewood University”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 94 internal links, 16 external

    The homepage links to 94 pages on edgewood.edu and 16 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Edgewood is more than a college. It’s a community filled with people ready to guide you and become your biggest support…”.

  • One H1 headline

    Your main headline reads: “Begins With You”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: CollegeOrUniversity 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.edgewood.edu/sitemap_index.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.edgewood.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,117 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.edgewood.edu/this-is-edgewood is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.edgewood.edu/this-is-edgewood has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages slow to respond

    https://www.edgewood.edu/about/board-of-trustees, https://www.edgewood.edu/about/maps-and-directions, https://www.edgewood.edu/about/history, https://www.edgewood.edu/about/fast-facts, https://www.edgewood.edu/about/mission-values-inclusion and https://www.edgewood.edu/about/events and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 774 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Request Your Transcript”, “View How to Apply” and “Apply”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 cookies set on arrival

    15

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 edgewood.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
DigitalOcean

Company

Employees
448
Founded
1927
Headquarters
Madison

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 edgewood.edu, including 18 speed issues, 1 SEO issue and 5 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