kernodle.com website review

16 images could be 4.9 MB 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.

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

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

Your mobile performance score is 59 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

About 427 KiB of JavaScript is downloaded but never used on this page.

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

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

6 third-party services load with your homepage (Google Maps, jQuery CDN and userway.org and others), adding 522 KiB and 241 ms of main-thread time.

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

93 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

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

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (9.1 s).

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

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

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

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

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

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

Your homepage downloads 54.3 MB in 183 requests on a phone: images 53.4 MB (147), scripts 760 KiB (19) and stylesheets 86 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Kernodle-Design-Location-Map-040726-scaled.png at 2,560 px wide, shown at 390 px. Resized copies would save about 283 KiB.

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

1 image (358 KiB) is 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.

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

Active <area> elements must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

2 dropdowns have no label.

1 button has no accessible name, so screen readers announce just “button”.

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

There are 5 <h1> headlines (“New Pulmonology Office Now Open”, “Convenient Access to your Online Medical Records.” and “Pediatric Care Now Available in Mebane”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 184 pages on kernodle.com and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.kernodle.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.kernodle.com/news, https://www.kernodle.com/specialties, https://www.kernodle.com/providers, https://www.kernodle.com/locations/burlington, https://www.kernodle.com/locations/mebane and https://www.kernodle.com/locations/elon and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kernodle.com/locations/oaks-professional-parkway and https://www.kernodle.com/locations/mebane-oaks use the same meta description. A description written for each page earns more clicks.

https://www.kernodle.com/specialties, https://www.kernodle.com/providers, https://www.kernodle.com/locations/mebane, https://www.kernodle.com/locations/elon, https://www.kernodle.com/locations/mebane-oaks and https://www.kernodle.com/for-patients and 3 others took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “InvalidValueError: setCenter: not a LatLng or LatLngLiteral with finite coordinates: in property lat: NaN is not an acc…”.

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.

Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 2,237 words of visible text.

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