ksdiggs.com website review

About 844 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.

18 images could be 490 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, TikTok and Klaviyo and others), adding 1.2 MB and 962 ms of main-thread time.

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

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

Shopify costs a phone 236 ms of main-thread work and 420 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 2,444 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 175 ms of main-thread work and 317 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.

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

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

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

13 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.

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “95% OF CHILD SEXUAL ABUSE IS PREVENTABLE THROUGH EDUCATION.…”.

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

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

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

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

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

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

Your homepage downloads 4.0 MB in 340 requests on a phone: scripts 1.4 MB (143), images 1.4 MB (76) and other files 669 KiB (90). Under 2 MB keeps phones on slow connections fast.

image-child-1-removebg-preview.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (43 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

5 buttons have no accessible name, so screen readers announce just “button”.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

2 images have no alt text, which hurts accessibility and image search.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 85 characters, so Google will cut it off around 60: “Diverse Kid's Books on Body Safety, Consent, and Mental Health – Diggs Publishing LLC”.

The homepage links to 85 pages on ksdiggs.com and 24 external pages.

https://ksdiggs.com/collections/books, https://ksdiggs.com/collections/all, https://ksdiggs.com/pages/about-me, https://ksdiggs.com/pages/about-team, https://ksdiggs.com/collections/bundles and https://ksdiggs.com/collections/e-books and 3 others use the same meta description. A description written for each page earns more clicks.

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

21 of 73 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 “Uncaught (in promise) TypeError: Cannot destructure property 'name' of 'e' as it is undefined.”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 943 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 21 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.