Website review, no card needed
ag.purdue.edu website review
Visit site (opens in a new tab)Reviewed 25 October 202641 issues · 87 checks
This review found 41 issues worth fixing on ag.purdue.edu, 13 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 112 ms |
| May 9, 2026 | 109 ms |
| May 16, 2026 | 117 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 118 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 115 ms |
| Aug 22, 2026 | 115 ms |
| Aug 29, 2026 | 115 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 127 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
Speed
Improve image delivery
7.0 s · 2.1 MB9 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.0 s faster on a phone.
Render-blocking requests
5.8 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.8 s.
Reduce unused JavaScript
3.7 s · 662 KiBAbout 662 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 69). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Clarity and others), adding 1.5 MB and 1.3 s of main-thread time.
Google Tag Manager adds 870 ms
870 msGoogle Tag Manager costs a phone 870 ms of main-thread work and 892 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 · 102 KiBAbout 102 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.
Minify JavaScript
300 ms · 60 KiB60 KiB could be saved by minifying JavaScript.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.
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.
Cloudflare CDN adds 72 ms
72 msCloudflare CDN costs a phone 72 ms of main-thread work and 341 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
200 ms · 37 KiB6 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).
Phones get a much slower page than desktops
Desktop scores 69 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Largest Contentful Paint: 29.9 s
29.9 sYour largest element takes 29.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INSPIRED BY OPPORTUNITY, DRIVEN BY PURPOSE LEARN MORE”.
Time to Interactive: 30.4 s
30.4 sThe page becomes fully interactive after 30.4 s. Good is under 3.8 s.
First Contentful Paint: 7.0 s
7.0 sThe first text or image appears after 7.0 s on a phone. Good is under 1.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 898 ms
898 msReal visitors wait 898 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 557 ms
557 msScripts block taps and scrolling for 557 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 87 requests
5.5 MBYour homepage downloads 5.5 MB in 87 requests on a phone: images 3.4 MB (21), scripts 1.3 MB (21) and fonts 637 KiB (11). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
cooney-1800x945.jpg weighs 493 KiB. On a phone connection a single image that size takes seconds.
4 images far larger than shown
907 KiB4 images are downloaded at several times the size a phone draws them, for example cooney-1800x945.jpg at 1,800 px wide, shown at 270 px. Resized copies would save about 907 KiB.
7 images in older formats
7 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 (350 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 185.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Meta description is long (289 characters)
Your meta description is 289 characters; Google truncates after about 160, so the end of your pitch is cut.
15 links with vague text
15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
105 internal links, 94 external
The homepage links to 105 pages on ag.purdue.edu and 94 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Purdue University College of Agriculture”.
Title: 42 characters
Your title is a healthy 42 characters: “College of Agriculture - Purdue University”.
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://ag.purdue.edu/ag-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://ag.purdue.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 (920 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://ag.purdue.edu/directory/index.html, https://ag.purdue.edu/students/majors.html and https://ag.purdue.edu/department/oap/cate/excellence/deans-scholars-current.html have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://ag.purdue.edu/directory/index.html 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 47 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'style')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 275 words of copy
The homepage carries about 275 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact College of Ag” and “LEARN MORE”.
17 calls to action
The homepage has 17 calls to action, for example “Contact College of Ag”, “Apply” and “Shop”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
20 other companies contacted
Loading the homepage contacts 20 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 ag.purdue.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
Hiring
- Hiring
- 4 open roles
- Teams
- Sales (2), Engineering (1), Finance (1)
- Job board
- greenhouse
- Careers page
- boards.greenhouse.io/ag (opens in a new tab)
Company
- Founded
- 1869
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on ag.purdue.edu, including 21 speed issues, 6 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.