kellerheartt.com website review

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

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

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

About 917 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (hsappstatic.net, Shopify and Google Tag Manager and others), adding 1.8 MB and 1.2 s of main-thread time.

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

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

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

hsappstatic.net costs a phone 368 ms of main-thread work and 715 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.

Shopify costs a phone 333 ms of main-thread work and 340 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.

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

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

3 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 254 requests on a phone: scripts 2.0 MB (94), other files 863 KiB (118) and stylesheets 212 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Some list items are not inside a list.

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

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

Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 289 pages on kellerheartt.com and 56 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.kellerheartt.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.

We fetched 15 pages linked from your homepage (of 118 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=5060893&Ver=2&mid=f5c4e4f0-210b-4417-9a06-bdcf7176fbfa&bo=1&sid=6d425aa0d87411f19a5153781c9d21c1&vid=6d428470d87411f1bf563bdf339ce2ac&vids=0&msclkid=N&pi=918639831&lg=.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

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

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