Website review, no card needed

newpaltz.edu logo

newpaltz.edu website review

Visit site (opens in a new tab)Reviewed 31 October 202651 issues · 89 checks

This review found 51 issues worth fixing on newpaltz.edu, 17 of them high impact, across 89 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 s979 msMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.0 s
May 16, 20261.1 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.0 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
192 ms111 msMay 9Oct 24179 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026120 ms
May 16, 2026120 ms
May 23, 2026120 ms
May 30, 2026121 ms
Jun 6, 2026122 ms
Jun 13, 2026126 ms
Jun 20, 2026129 ms
Jun 27, 2026129 ms
Jul 4, 2026134 ms
Jul 11, 2026140 ms
Jul 18, 2026145 ms
Jul 25, 2026152 ms
Aug 1, 2026155 ms
Aug 8, 2026155 ms
Aug 15, 2026161 ms
Aug 22, 2026160 ms
Aug 29, 2026162 ms
Sep 5, 2026165 ms
Sep 12, 2026163 ms
Sep 19, 2026171 ms
Sep 26, 2026175 ms
Oct 3, 2026177 ms
Oct 10, 2026181 ms
Oct 17, 2026183 ms
Oct 24, 2026179 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 newpaltz.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix30
  • Use efficient cache lifetimes

    1.2 s · 15.7 MB

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

  • Reduce unused JavaScript

    2.3 s · 544 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 30

    30/100

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

  • Improve image delivery

    150 ms · 6.0 MB

    5 images could be 6.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 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,001 KiB and 1.3 s of main-thread time.

  • Google Tag Manager adds 651 ms

    651 ms

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

    313 ms

    Facebook costs a phone 313 ms of main-thread work and 227 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.

  • TikTok adds 275 ms

    275 ms

    TikTok costs a phone 275 ms of main-thread work and 172 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.

  • 11 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • Legacy JavaScript

    150 ms · 33 KiB

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

  • Reduce unused CSS

    100 ms · 19 KiB

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

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 57 ms

    57 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 27.2 s

    27.2 s

    Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fall 2026 Graduate Programs Open House”.

  • Time to Interactive: 29.8 s

    29.8 s

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

  • Cumulative Layout Shift: 0.615

    0.615

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

  • Total Blocking Time: 817 ms

    817 ms

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

  • Real-user INP: 239 ms

    239 ms

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

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

    +51%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 120 ms to 179 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-10-24, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 4.0 s

    4.0 s

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

  • 17 images without width and height

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

5 checks passed
  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 403 ms

    403 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix18
  • 2 images over 500 KB

    2 images weigh 35.8 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    35.5 MB

    4 images are downloaded at several times the size a phone draws them, for example 20261016-5_Beyond the Ridge Campaign Launch_359.jpg at 8,256 px wide, shown at 330 px. Resized copies would save about 35.5 MB.

  • Page weight: 23.7 MB in 92 requests

    23.7 MB

    Your homepage downloads 23.7 MB in 92 requests on a phone: media 14.9 MB (1), images 7.7 MB (39) and scripts 1.0 MB (19). Under 2 MB keeps phones on slow connections fast.

  • 16 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (29.9 MB) is 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 6.7 g of CO₂ per visit

    6.72 g

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

Accessibility

5 to fixGoogle 9491
  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (33 elements)

    All page content should be contained by landmarks: 33 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 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.

  • 32 automated accessibility rules passed

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

SEO

6 to fixGoogle 9274
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • No XML sitemap

    No XML sitemap at https://www.newpaltz.edu/sitemap.xml, so Google discovers your pages only by following links.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 118 internal links, 39 external

    The homepage links to 118 pages on newpaltz.edu and 39 external pages.

3 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “SUNY New Paltz, The State University of New York, is a four-year, public liberal arts college located in the Hudson Val…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “SUNY New Paltz | The State University of New York at New Paltz”.

  • robots.txt in place

    robots.txt is in place.

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

5 to fix57
  • 1 linked page is broken

    Your homepage links to https://www.newpaltz.edu/ugc/programs.html, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://www.newpaltz.edu/admissions/apply.html and https://www.newpaltz.edu/admissions/scholarships.html all use the title “SUNY New Paltz - Undergraduate Admissions”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.newpaltz.edu/admissions/international has no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.newpaltz.edu/prospective-students, https://www.newpaltz.edu/transfer, https://www.newpaltz.edu/financialaid, https://www.newpaltz.edu/parentsweekend, https://www.newpaltz.edu/commencement and https://www.newpaltz.edu/about/directions.html use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.newpaltz.edu/admissions/international 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 71 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 9 small tap targets

    9 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 9 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 1,024 words of visible text.

3 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Apply”, “Contact Us” and “Schedule of Classes”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, TikTok Pixel and Cloudflare Web Analytics.

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

  • 11 cookies set on arrival

    11

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 newpaltz.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
Newpaltzedu

Company

Employees
1,305
Founded
1828

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on newpaltz.edu, including 21 speed issues, 6 SEO issues 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