kwe.org website review

About 743 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

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

5 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 150 ms faster on a phone.

Your mobile performance score is 54 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

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

7 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.1 MB and 751 ms of main-thread time.

Google CDN costs a phone 494 ms of main-thread work and 733 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.

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

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

4 files are served with short cache lifetimes, so returning visitors download them again (17 KiB).

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The first text or image appears after 10.2 s on a phone. Good is under 1.8 s.

Your largest element takes 24.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “100th mobile 2”.

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 77 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.1 MB in 129 requests on a phone: images 3.6 MB (18), scripts 1.6 MB (59) and other files 353 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example tls-logo-2024.svg at 384 px wide, shown at 72 px. Resized copies would save about 37 KiB.

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

5 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Contentinfo 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 on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

13 visible links have no text or label, so screen readers cannot say where they go.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 21 characters: “Kieve Wavus Education”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

19 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 54 pages on kwe.org and 11 external pages.

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.

There is no https://www.kwe.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.

https://www.kwe.org/events and https://www.kwe.org/retreats all use the title “Retreats – Kieve Wavus Education”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kwe.org/about, https://www.kwe.org/kwe-giving, https://www.kwe.org/contact, https://www.kwe.org/centennial, https://www.kwe.org/kieve and https://www.kwe.org/wavus and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.kwe.org/retreats, whose canonical is https://www.kwe.org/events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage has only about 185 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.