katelynjamesblog.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (webinarjam.com, getchipbot.com and Cloudflare CDN and others), adding 4.5 MB and 2.7 s of main-thread time.

webinarjam.com costs a phone 808 ms of main-thread work and 2.9 MB 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.

getchipbot.com costs a phone 427 ms of main-thread work and 384 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.

Cloudflare CDN costs a phone 383 ms of main-thread work and 337 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 271 ms of main-thread work and 192 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.

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

WordPress costs a phone 278 ms of main-thread work and 37 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 272 KiB of CSS is downloaded but never applied on this page.

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

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

9 KiB could be saved by minifying JavaScript.

16 KiB JavaScript is shipped twice across bundles.

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.3 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 32.6 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

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

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

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

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

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

Your homepage downloads 36.3 MB in 502 requests on a phone: images 30.9 MB (79), scripts 4.3 MB (264) and stylesheets 381 KiB (83). Under 2 MB keeps phones on slow connections fast.

8 images (699 KiB) 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.

2 images further down the page (106 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 10.30 g of CO₂e: 1235.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

All page content should be contained by landmarks: 52 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.

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

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

Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), 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 74 characters, so Google will cut it off around 60: “Blog - Katelyn James | Online Educator for Photographers and Entrepreneurs”.

There are 60 <h1> headlines (“You didn’t start your photography business to los…”, “let me help you” and “take it back!”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 198 pages on katelynjamesblog.com and 155 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://katelynjames.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://katelynjames.com/podcast, /, https://katelynjames.com/color-grading-guide, https://katelynjames.com/indoor-composition, https://katelynjames.com/bwp-free-audio and https://katelynjames.com/questionnaire and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://katelynjames.com/podcast, whose canonical is https://katelynjames.com/blog/podcast. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://katelynjames.com/kj-faves, https://katelynjames.com/podcast and / have no <h1> headline, so visitors and search engines get no clear main topic.

https://katelynjames.com/blog/category/my-life and https://katelynjames.com/blog/category/education took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: OneSignalSDK: The "My site is not fully HTTPS" option is no longer supported starting with…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

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

The homepage has only about 227 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.

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

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