kennards.com.au website review

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

20 images could be 2.7 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.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Convert Insights and cdn-cookieyes.com and others), adding 5.2 MB and 589 ms of main-thread time.

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

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

sitecorecloud.io costs a phone 0 ms of main-thread work and 4.5 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.

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

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

About 46 KiB of CSS is downloaded but never applied on this page.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Real visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kennards Hire expert onsite with a customer next to a gener…”.

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

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

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

Real visitors wait 328 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

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

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

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-24, real Chrome visitors' tap response (inp) went from 271 ms to 291 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.4 MB in 107 requests on a phone: images 4.5 MB (51), scripts 1.7 MB (19) and other files 151 KiB (29). Under 2 MB keeps phones on slow connections fast.

19 images (3.8 MB) 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.

14 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example KH3175_New_Product_Range_Campaign_Desktop_Mobile_1056x500_Ma at 1,056 px wide, shown at 211 px. Resized copies would save about 438 KiB.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (2 elements).

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 274 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link has no real href, so search engines can't follow it.

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 26 pages on kennards.com.au and 3 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.kennards.com.au/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.kennards.com.au/latest-news/national-family-business-day-2026 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.kennards.com.au/commercial/specialist-solutions/power, https://www.kennards.com.au/equipment, https://www.kennards.com.au/account-portal, https://www.kennards.com.au/trade, https://www.kennards.com.au/commercial/specialist-solutions and https://www.kennards.com.au/commercial/specialist-solutions/kennards-major-projects and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kennards.com.au/branch, https://www.kennards.com.au/credit-account-application and https://www.kennards.com.au/commercial/case-studies have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.kennards.com.au/trade took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

Requests the geolocation permission on page load.

Large scripts ship without source maps.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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