kaplanco.com website review

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

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

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

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

Google Tag Manager costs a phone 1.3 s of main-thread work and 877 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 11.6 s on main-thread work while loading, 7.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 18. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Osano CMP and Hubspot and others), adding 2.1 MB and 3.4 s of main-thread time.

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

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

Osano CMP costs a phone 417 ms of main-thread work and 79 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.

Hubspot costs a phone 389 ms of main-thread work and 160 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.

Facebook costs a phone 378 ms of main-thread work and 213 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.

logr-in.com costs a phone 257 ms of main-thread work and 147 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.

The page has 1,653 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

104 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need.

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.

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 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nurture empathy through meaningful pretend play moments!”.

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

Scripts block taps and scrolling for 3.5 s in total while the page loads. Good is under 200 ms.

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

The layout shifts by 0.292 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 8.3 MB in 169 requests on a phone: images 5.3 MB (56), scripts 2.6 MB (50) and other files 178 KiB (54). Under 2 MB keeps phones on slow connections fast.

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

9 images are downloaded at several times the size a phone draws them, for example video-thumb.webp at 1,703 px wide, shown at 390 px. Resized copies would save about 323 KiB.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 95 characters, so Google will cut it off around 60: “Teaching Supplies & Child Care Resources for Early Education Classrooms | Kaplan Early Le…”.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

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

The homepage links to 286 pages on kaplanco.com and 41 external pages.

There is no https://kaplanco.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://kaplanco.com/CustomerService/catalogRequestForm.asp, https://kaplanco.com/store/trans/quickOrderForm.asp, https://kaplanco.com/secure/myKaplan/myKaplan, https://kaplanco.com/secure/CustomerService/orderTracking.asp, https://kaplanco.com/secure/CustomerService/productRegistration.asp and https://kaplanco.com/secure/CustomerService/RMA_Start.asp and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://kaplanco.com/about/contactKaplan, https://kaplanco.com/CustomerService/contactSalesForm.asp, https://kaplanco.com/CustomerService/catalogRequestForm.asp, https://kaplanco.com/store/trans/quickOrderForm.asp, https://kaplanco.com/secure/myKaplan/myKaplan and https://kaplanco.com/secure/CustomerService/orderTracking.asp and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

Chrome logged issues while loading the page (“Content security policy”).

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 homepage carries about 485 words of visible text.

Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

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

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