Website review, no card needed
ughe.org website review
Visit site (opens in a new tab)Reviewed 19 November 202634 issues · 82 checks
This review found 34 issues worth fixing on ughe.org, 13 of them high impact, across 82 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 11.4 s |
| Jun 6, 2026 | 18.5 s |
| Jun 13, 2026 | 26.3 s |
| Jun 20, 2026 | 26.4 s |
| Jun 27, 2026 | 22.0 s |
| Jul 4, 2026 | 19.5 s |
| Jul 11, 2026 | 18.8 s |
| Jul 18, 2026 | 17.1 s |
| Jul 25, 2026 | 16.0 s |
| Aug 1, 2026 | 16.0 s |
| Aug 8, 2026 | 16.7 s |
| Aug 15, 2026 | 17.2 s |
| Aug 22, 2026 | 17.4 s |
| Aug 29, 2026 | 17.3 s |
| Sep 5, 2026 | 16.0 s |
| Sep 12, 2026 | 17.2 s |
| Sep 19, 2026 | 16.9 s |
| Sep 26, 2026 | 18.2 s |
| Oct 3, 2026 | 16.8 s |
| Oct 10, 2026 | 10.9 s |
| Oct 17, 2026 | 8.2 s |
| Oct 24, 2026 | 6.0 s |
| Oct 31, 2026 | 5.1 s |
| Nov 7, 2026 | 4.5 s |
| Nov 14, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 239 ms |
| Jun 6, 2026 | 243 ms |
| Jun 13, 2026 | 237 ms |
| Jun 20, 2026 | 236 ms |
| Jun 27, 2026 | 229 ms |
| Jul 4, 2026 | 221 ms |
| Jul 11, 2026 | 222 ms |
| Jul 18, 2026 | 212 ms |
| Jul 25, 2026 | 234 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 241 ms |
| Aug 15, 2026 | 240 ms |
| Aug 22, 2026 | 240 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 231 ms |
| Sep 12, 2026 | 241 ms |
| Sep 19, 2026 | 245 ms |
| Sep 26, 2026 | 258 ms |
| Oct 3, 2026 | 241 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 165 ms |
| Oct 24, 2026 | 144 ms |
| Oct 31, 2026 | 154 ms |
| Nov 7, 2026 | 156 ms |
| Nov 14, 2026 | 158 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
Use efficient cache lifetimes
1.3 s · 4.3 MB90 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).
Render-blocking requests
3.1 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Font display
2.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.3 s).
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 155 KiBAbout 155 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Improve image delivery
837 KiB9 images could be 837 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
230 KiBAbout 230 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.
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 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 37 KiB and 1 ms of main-thread time.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 404 ms of it running JavaScript. That is comfortably low.
Server response: 117 ms
117 msYour server sent the HTML in 117 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: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Applications are now open for Bachelor of Medicine, Bachelo…”. Most of its time is element render delay (6.0 s).
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.5 s
4.5 sThe page becomes fully interactive after 4.5 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user INP: 145 ms
145 msReal visitors wait 145 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.
Tap response (INP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 239 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 70% faster for real visitors
-70%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 11.4 s to 4.5 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).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.6 MB in 95 requests
4.6 MBYour homepage downloads 4.6 MB in 95 requests on a phone: images 2.6 MB (16), fonts 1.3 MB (7) and scripts 504 KiB (44). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (669 KiB) 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.
About 1.3 g of CO₂ per visit
1.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.31 g of CO₂e: 156.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
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 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
13 links with vague text
13 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 incomplete here.
143 internal links, 21 external
The homepage links to 143 pages on ughe.org and 21 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Home”.
Title: 34 characters
Your title is a healthy 34 characters: “University of Global Health Equity”.
Canonical URL set
The canonical URL is https://ughe.org/.
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://ughe.org/wp-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://ughe.org/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 (797 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://ughe.org/admission, https://ughe.org/get-involved, https://ughe.org/leadership, https://ughe.org/more, https://ughe.org/about and https://ughe.org/university-medalists and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages slow to respond
https://ughe.org/admission, https://ughe.org/get-involved, https://ughe.org/leadership, https://ughe.org/more, https://ughe.org/about and https://ughe.org/tenders and 3 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 64 found) and read each the way a search engine does.
6 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.
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
2 broken images
2 images failed to load on a phone, for example https://ughe.org/wp-content/uploads/2026/04/UGHE-H-600x169.png.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
2 checks passed
Tap targets are thumb-sized
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 326 words of copy
The homepage carries about 326 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “APPLY”.
5 calls to action
The homepage has 5 calls to action, for example “Apply”, “Apply to UGHE” and “All UGHE News from start till present”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ughe.org, 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
- Hosting
- DigitalOcean
Hiring
- Hiring
- 13 open roles
- Job board
- careers page
- Careers page
- ughe.org/careers (opens in a new tab)
Company
- Founded
- 2015
- Headquarters
- Rwanda
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on ughe.org, including 15 speed issues, 4 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.