Website review, no card needed
hallmark.edu website review
Visit site (opens in a new tab)Reviewed 26 October 202636 issues · 87 checks
This review found 36 issues worth fixing on hallmark.edu, 11 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 126 ms |
| May 16, 2026 | 129 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 141 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 206 ms |
| Sep 12, 2026 | 266 ms |
| Sep 19, 2026 | 330 ms |
| Sep 26, 2026 | 406 ms |
| Oct 3, 2026 | 429 ms |
| Oct 10, 2026 | 424 ms |
| Oct 17, 2026 | 376 ms |
| Oct 24, 2026 | 381 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
Render-blocking requests
1.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Facebook and others), adding 1.6 MB and 1.5 s of main-thread time.
Reduce unused JavaScript
600 ms · 669 KiBAbout 669 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 80). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 754 ms
754 msGoogle Tag Manager costs a phone 754 ms of main-thread work and 1.0 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.
FontAwesome CDN adds 606 ms
606 msFontAwesome CDN costs a phone 606 ms of main-thread work and 324 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
300 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 283 ms. During a long task the page ignores taps.
Improve image delivery
256 KiB4 images could be 256 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
222 KiB5 files are served with short cache lifetimes, so returning visitors download them again (222 KiB).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 51. A gap that wide usually means heavy scripts and images that hit phones hardest.
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 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DEGREE PROGRAMS DESIGNED FOR YOUR SUCCESS LET'S GET STARTED”.
Time to Interactive: 18.6 s
18.6 sThe page becomes fully interactive after 18.6 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 645 ms
645 msScripts block taps and scrolling for 645 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 197% slower for real visitors
+197%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 126 ms to 381 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 196 ms
196 msReal visitors wait 196 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.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 390 ms
390 msReal visitors wait 390 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.017
0.017The layout barely moves while loading (CLS 0.017, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 66 requests
2.8 MBYour homepage downloads 2.8 MB in 66 requests on a phone: scripts 1.8 MB (17), fonts 493 KiB (5) and images 379 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 7 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
133 internal links, 29 external
The homepage links to 133 pages on hallmark.edu and 29 external pages.
8 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Hallmark University is an accelerated, nonprofit university offering aeronautics, business, nursing, and information te…”.
One H1 headline
Your main headline reads: “DEGREE PROGRAMS DESIGNED FOR YOUR SUCCESS”.
Title: 33 characters
Your title is a healthy 33 characters: “Hallmark University - San Antonio”.
Canonical URL set
The canonical URL is https://hallmark.edu/.
Structured data in place
Structured data found: BreadcrumbList, CollegeOrUniversity, ImageObject, Organization and Place.
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.
XML sitemap found
Your XML sitemap is reachable at https://hallmark.edu/sitemap.xml.
AI search readiness
No llms.txt
There is no https://hallmark.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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (618 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://hallmark.edu/financial-planning and https://hallmark.edu/resources/financial-planning all use the title “Financial Planning - Hallmark University - San Antonio, TX”. 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://hallmark.edu/current-students/student-life-development has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://hallmark.edu/financial-planning and https://hallmark.edu/resources/financial-planning use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://hallmark.edu/nursing-school, whose canonical is https://hallmark.edu/school-of-nursing-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
9 small tap targets
9 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 293 words of copy
The homepage carries about 293 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: “LET'S GET STARTED” and “Request information instead”.
17 calls to action
The homepage has 17 calls to action, for example “Transcript and Diploma Request”, “Contact” and “Apply”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 2 of them by other companies (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.
19 other companies contacted
Loading the homepage contacts 19 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 hallmark.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 Analytics | Google Tag Manager
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 hallmark.edu, including 16 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.