kaganonline.com website review

62 files are served with short cache lifetimes, so returning visitors download them again (13.4 MB).

12 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.6 s faster on a phone.

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

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

About 134 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

Google Tag Manager costs a phone 191 ms of main-thread work and 313 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.

4 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and cookieyes.com and others), adding 336 KiB and 204 ms of main-thread time.

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

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

9 KiB could be saved by minifying CSS.

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

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.

Your largest element takes 60.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KaganTools”.

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 13.8 MB in 79 requests on a phone: images 13.3 MB (49), scripts 375 KiB (10) and stylesheets 57 KiB (9). Under 2 MB keeps phones on slow connections fast.

5 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

29 images (13.0 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.

7 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example socmedia-sa2026-reviews.jpg at 958 px wide, shown at 66 px. Resized copies would save about 273 KiB.

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

7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 11 <h1> headlines (“Kagan”, “Over 1,000 Studies Support Cooperative Learning” and “Meta-Analyses Show 26% Achievement Gain”). One clear main headline is easier for people and search engines.

Your meta description is 227 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://www.kaganonline.com/sitemap.xml, so Google discovers your pages only by following links.

6 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 100 pages on kaganonline.com and 13 external pages.

There is no https://www.kaganonline.com/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.kaganonline.com/workshops/events, https://www.kaganonline.com/workshops/usa_tour, https://www.kaganonline.com/workshops/events/live_online, https://www.kaganonline.com/conferences and https://www.kaganonline.com/onDemand have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kaganonline.com/workshops/summer_academy, https://www.kaganonline.com/workshops/bring_in_kagan, https://www.kaganonline.com/workshops/workshop_topics, https://www.kaganonline.com/workshops/kagan_coaching.php, https://www.kaganonline.com/workshops/engagement_support_sessions and https://www.kaganonline.com/workshops/win-win_discipline_support_sessions and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.kaganonline.com/workshops/summer_academy, whose canonical is https://www.kaganonline.com/workshops/summer_academy/index.php. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.kaganonline.com/workshops/usa_tour has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kaganonline.com/onDemand has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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)”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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

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