Website review, no card needed
kcau.ac.ke website review
Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 89 checks
This review found 41 issues worth fixing on kcau.ac.ke, 18 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.7 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 240 ms |
| May 16, 2026 | 239 ms |
| May 23, 2026 | 241 ms |
| May 30, 2026 | 243 ms |
| Jun 6, 2026 | 250 ms |
| Jun 13, 2026 | 244 ms |
| Jun 20, 2026 | 245 ms |
| Jun 27, 2026 | 245 ms |
| Jul 4, 2026 | 243 ms |
| Jul 11, 2026 | 251 ms |
| Jul 18, 2026 | 252 ms |
| Jul 25, 2026 | 257 ms |
| Aug 1, 2026 | 261 ms |
| Aug 8, 2026 | 272 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 269 ms |
| Aug 29, 2026 | 270 ms |
| Sep 5, 2026 | 269 ms |
| Sep 12, 2026 | 272 ms |
| Sep 19, 2026 | 275 ms |
| Sep 26, 2026 | 277 ms |
| Oct 3, 2026 | 280 ms |
| Oct 10, 2026 | 289 ms |
| Oct 17, 2026 | 291 ms |
| Oct 24, 2026 | 296 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
1.9 s
3.8 s
5.7 s
7.7 s
9.6 s
11.5 s
13.4 s
15.3 s
Speed
Use efficient cache lifetimes
4.3 s · 2.5 MB106 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Render-blocking requests
5.0 s49 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Reduce unused JavaScript
4.2 s · 693 KiBAbout 693 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Reduce unused CSS
1.0 s · 214 KiBAbout 214 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and LinkedIn Ads and others), adding 1.6 MB and 732 ms of main-thread time.
Google Tag Manager adds 494 ms
494 msGoogle Tag Manager costs a phone 494 ms of main-thread work and 793 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,771 HTML elements
The page has 1,771 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
JSDelivr CDN adds 11 ms
11 msJSDelivr CDN costs a phone 11 ms of main-thread work and 478 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Minify JavaScript
150 ms · 19 KiB19 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 8 KiB8 KiB could be saved by minifying CSS.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 129 ms. During a long task the page ignores taps.
Improve image delivery
126 KiB2 images could be 126 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 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: 457 ms
457 msYour server sent the HTML in 457 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: 6.3 s
6.3 sReal visitors wait 6.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 22.9 s
22.9 sYour largest element takes 22.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (9.3 s).
Speed Index: 22.1 s
22.1 sVisually, the page fills in at 22.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.6 s
24.6 sThe page becomes fully interactive after 24.6 s. Good is under 3.8 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Real-user INP: 342 ms
342 msReal visitors wait 342 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 240 ms to 296 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 279 ms
279 msScripts block taps and scrolling for 279 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.
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.7 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.019
0.019The layout barely moves while loading (CLS 0.019, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 155 requests
4.4 MBYour homepage downloads 4.4 MB in 155 requests on a phone: scripts 1.8 MB (53), images 1.4 MB (36) and fonts 830 KiB (7). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (180 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.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.8 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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (62 elements)
All page content should be contained by landmarks: 62 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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 65 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (302 characters)
Your meta description is 302 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
233 internal links, 88 external
The homepage links to 233 pages on kcau.ac.ke and 88 external pages.
6 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “KCA University - KCA University”.
Canonical URL set
The canonical URL is https://www.kcau.ac.ke/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.kcau.ac.ke/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.kcau.ac.ke/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 (1,635 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://www.kcau.ac.ke/university-council, https://www.kcau.ac.ke/office-of-the-deputy-vice-chancellor-teaching-and-learning-dvc-tl, https://www.kcau.ac.ke/office-of-the-deputy-vice-chancellor-research-innovation-and-outreach-rio-2, https://www.kcau.ac.ke/university-management-board, https://www.kcau.ac.ke/mission-vision and https://www.kcau.ac.ke/history have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.kcau.ac.ke/directorate-of-quality-assurance, https://www.kcau.ac.ke/legal-services-department and https://www.kcau.ac.ke/ict use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://www.kcau.ac.ke/personnel/fcpa-dr-martin-oduor-otieno-cbs, https://www.kcau.ac.ke/personnel/prof-isaiah-i-c-wakindiki-phd-ebs, https://www.kcau.ac.ke/office-of-the-vice-chancellor-ceo, https://www.kcau.ac.ke/office-of-the-deputy-vice-chancellor-teaching-and-learning-dvc-tl, https://www.kcau.ac.ke/office-of-the-deputy-vice-chancellor-strategy-finance-and-operations-sfo and https://www.kcau.ac.ke/office-of-the-deputy-vice-chancellor-research-innovation-and-outreach-rio-2 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.kcau.ac.ke/personnel/fcpa-dr-martin-oduor-otieno-cbs, https://www.kcau.ac.ke/personnel/prof-isaiah-i-c-wakindiki-phd-ebs and https://www.kcau.ac.ke/office-of-the-vice-chancellor-ceo took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 81 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
46 small tap targets
46 of 70 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Creating a worker from 'blob:https://www.kcau.ac.ke/96ef2d61-d143-4b2e-86a5-47abb542a0f8' violates the following Conten…”.
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
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 716 words of copy
The homepage carries about 716 words of visible text.
4 checks passed
18 calls to action
The homepage has 18 calls to action, for example “How to Apply”, “Join Us” and “Request a Counseling Session”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 kcau.ac.ke, 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
- Hosting
- Kenet
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 kcau.ac.ke, including 22 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.