Website review, no card needed
endicott.edu website review
Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 86 checks
This review found 38 issues worth fixing on endicott.edu, 12 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 144 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 159 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 156 ms |
| Oct 24, 2026 | 159 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
2.4 s · 608 KiB15 files are served with short cache lifetimes, so returning visitors download them again (608 KiB).
Render-blocking requests
2.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused JavaScript
1.1 s · 546 KiBAbout 546 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
1.1 s · 227 KiB5 images could be 227 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s 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 2.4 MB and 1.0 s of main-thread time.
Reduce unused CSS
760 ms · 283 KiBAbout 283 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 627 ms
627 msGoogle Tag Manager costs a phone 627 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.
Adobe TypeKit adds 8 ms
8 msAdobe TypeKit costs a phone 8 ms of main-thread work and 761 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.
FontAwesome CDN adds 27 ms
27 msFontAwesome CDN costs a phone 27 ms of main-thread work and 374 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 159 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 18.9 s
18.9 sYour largest element takes 18.9 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: 24.5 s
24.5 sThe page becomes fully interactive after 24.5 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 308 ms
308 msScripts block taps and scrolling for 308 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 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 144 ms to 159 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user TTFB: 663 ms
663 msReal visitors wait 663 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 114 requests
4.4 MBYour homepage downloads 4.4 MB in 114 requests on a phone: images 1.6 MB (25), scripts 1.4 MB (24) and fonts 1.1 MB (34). Under 2 MB keeps phones on slow connections fast.
15 images below the first screen load straight away
15 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images far larger than shown
314 KiB6 images are downloaded at several times the size a phone draws them, for example main.jpg at 1,880 px wide, shown at 330 px. Resized copies would save about 314 KiB.
About 1.2 g of CO₂ per visit
1.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.25 g of CO₂e: 149.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
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.
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.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Endicott College” and “Endicott College”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
127 internal links, 23 external
The homepage links to 127 pages on endicott.edu and 23 external pages.
6 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “A private coeducational college located in Beverly, MA, near Boston, offering undergraduate, graduate and professional …”.
Title: 56 characters
Your title is a healthy 56 characters: “Home | Private College in Beverly, MA | Endicott College”.
Structured data in place
Structured data found: CollegeOrUniversity.
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.endicott.edu/sitemap.xml.
AI search readiness
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.endicott.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,351 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.endicott.edu/about/why-endicott/facts-and-figures and https://www.endicott.edu/news-events/soundings-magazine have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.endicott.edu/news-events/soundings-magazine has 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 98 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.
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
70 small tap targets
70 of 96 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 trust badge. 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 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,108 words of copy
The homepage carries about 1,108 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
25 calls to action
The homepage has 25 calls to action, for example “Contact Us”, “How to Apply” and “Register for Classes”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel 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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
27 other companies contacted
Loading the homepage contacts 27 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 endicott.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 Tag Manager
- Hosting
- Azure
Company
- Employees
- 1,007
- Founded
- 1939
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 endicott.edu, including 19 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.