kimberlyfeaman.com website review

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

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

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

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

The page goes through 1 redirect before it starts loading, costing about 608 ms. Link and advertise the final URL directly.

7 third-party services load with your homepage (Google/Doubleclick Ads, Blogger and adtrafficquality.google and others), adding 1.5 MB and 354 ms of main-thread time.

Blogger costs a phone 87 ms of main-thread work and 320 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.

googleusercontent.com costs a phone 0 ms of main-thread work and 796 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.

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

The HTML itself could arrive about 50 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is only 13 characters: “Kimberly Anne”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 82 pages on kimberlyfeaman.com and 6 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://www.kimberlyfeaman.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.kimberlyfeaman.com/2017, https://www.kimberlyfeaman.com/2017/08, https://www.kimberlyfeaman.com/2017/09, https://www.kimberlyfeaman.com/2017/10 and https://www.kimberlyfeaman.com/2017/11 and 6 others all use the title “Kimberly Anne”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kimberlyfeaman.com/2017/08/a-broken-heart.html, https://www.kimberlyfeaman.com/2020/02/5-reasons-you-need-girls-trip.html, https://www.kimberlyfeaman.com/2019/05/early-intervention.html and https://www.kimberlyfeaman.com/2019/02/welcome-to-motherhood.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kimberlyfeaman.com/2017, https://www.kimberlyfeaman.com/2017/08, https://www.kimberlyfeaman.com/2017/09, https://www.kimberlyfeaman.com/2017/10, https://www.kimberlyfeaman.com/2017/11 and https://www.kimberlyfeaman.com/2017/12 and 5 others use the same meta description. A description written for each page earns more clicks.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

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 275 words of visible text.

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

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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.