jkadams.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and cloudlift.app and others), adding 2.4 MB and 1.7 s of main-thread time.

12 images could be 635 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

YouTube costs a phone 526 ms of main-thread work and 980 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.

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

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

cloudlift.app costs a phone 271 ms of main-thread work and 220 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.

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

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

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

Polyfills for old browsers add 19 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.

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 241 requests on a phone: scripts 2.5 MB (89), images 1.7 MB (25) and other files 617 KiB (75). Under 2 MB keeps phones on slow connections fast.

JK-ADAMS-PRP-2.jpg weighs 489 KiB. On a phone connection a single image that size takes seconds.

3 images further down the page (262 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

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

There are 2 <h1> headlines (“” and “Free Personalization”). One clear main headline is easier for people and search engines.

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

The homepage links to 170 pages on jkadams.com and 9 external pages.

There is no https://www.jkadams.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.jkadams.com/collections/all, https://www.jkadams.com/pages/free-personalization-promotion and https://www.jkadams.com/collections/coasters have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jkadams.com/pages/free-personalization-promotion has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5820368&tm=shpfy_ui&Ver=2&mid=e6da86d7-be79-4d02-8a02-580928abeaa3&bo=1&sid=b05d92b0da3e11f18e60c122a30453be&vid=b05db330da3e11f1bc2a7dfed3349f09&vids=0&msclkid=N&pi=9.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage carries about 594 words of visible text.

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