Website review, no card needed

keelerhardware.com.au logo

keelerhardware.com.au website review

Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 100 checks

This review found 47 issues worth fixing on keelerhardware.com.au, 19 of them high impact, across 100 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.5 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.4 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
190 ms166 msMay 30Nov 14187 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026174 ms
Jun 6, 2026176 ms
Jun 13, 2026173 ms
Jun 20, 2026171 ms
Jun 27, 2026169 ms
Jul 4, 2026170 ms
Jul 11, 2026170 ms
Jul 18, 2026171 ms
Jul 25, 2026175 ms
Aug 1, 2026173 ms
Aug 8, 2026177 ms
Aug 15, 2026177 ms
Aug 22, 2026179 ms
Aug 29, 2026180 ms
Sep 5, 2026182 ms
Sep 12, 2026183 ms
Sep 19, 2026183 ms
Sep 26, 2026183 ms
Oct 3, 2026180 ms
Oct 10, 2026180 ms
Oct 17, 2026179 ms
Oct 24, 2026183 ms
Oct 31, 2026185 ms
Nov 7, 2026187 ms
Nov 14, 2026187 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of keelerhardware.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. keelerhardware.com.au at 2.5 s2.5 s
  2. keelerhardware.com.au at 5.1 s5.1 s
  3. keelerhardware.com.au at 7.6 s7.6 s
  4. keelerhardware.com.au at 10.2 s10.2 s
  5. keelerhardware.com.au at 12.7 s12.7 s
  6. keelerhardware.com.au at 15.2 s15.2 s
  7. keelerhardware.com.au at 17.8 s17.8 s
  8. keelerhardware.com.au at 20.3 s20.3 s

Speed

15 to fix28
  • Reduce unused JavaScript

    3.3 s · 1.7 MB

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

  • Use efficient cache lifetimes

    1.6 s · 1.1 MB

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

  • Font display

    1.9 s

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

  • Main-thread work: 12.4 s

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

  • Mobile performance score: 28

    28/100

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

  • 4,857 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, zoom.us and Shopify and others), adding 3.6 MB and 2.8 s of main-thread time.

  • YouTube adds 702 ms

    702 ms

    YouTube costs a phone 702 ms of main-thread work and 995 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.

  • Reduce unused CSS

    450 ms · 249 KiB

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

  • zoom.us adds 419 ms

    419 ms

    zoom.us costs a phone 419 ms of main-thread work and 1.2 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.

  • Shopify adds 353 ms

    353 ms

    Shopify costs a phone 353 ms of main-thread work and 473 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 on the main thread

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

  • Google Tag Manager adds 311 ms

    311 ms

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

  • Render-blocking requests

    300 ms

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

  • Facebook adds 276 ms

    276 ms

    Facebook costs a phone 276 ms of main-thread work and 223 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.

  • Legacy JavaScript

    150 ms · 57 KiB

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

  • Improve image delivery

    168 KiB

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

  • Minify JavaScript

    126 KiB

    126 KiB could be saved by minifying JavaScript.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 19 ms

    19 ms

    Your server sent the HTML in 19 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 57.5 s

    57.5 s

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

  • Speed Index: 41.2 s

    41.2 s

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

  • Time to Interactive: 69.2 s

    69.2 s

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

  • First Contentful Paint: 7.1 s

    7.1 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 198 ms

    198 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 564 ms

    564 ms

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

  • Largest content (LCP) got 34% faster for real visitors

    -34%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix35
  • Page weight: 15.3 MB in 616 requests

    15.3 MB

    Your homepage downloads 15.3 MB in 616 requests on a phone: images 9.0 MB (93), scripts 4.0 MB (138) and other files 1.6 MB (326). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (3.1 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.

  • 1 image far larger than shown

    35 KiB

    1 image is downloaded at several times the size a phone draws it, for example 4357825adb1163998c39671ee98e86e6.png at 1,450 px wide, shown at 285 px. Resized copies would save about 35 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (84 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.3 g of CO₂ per visit

    4.32 g

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

Accessibility

8 to fixGoogle 8091
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 1 text element with low contrast

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

  • 25 images without alt text

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

  • All page content should be contained by landmarks (2 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 36 links without text

    36 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 (5 elements)

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9291
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “About Keeler Hardware”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “LocalBusiness: sameAs is an empty list”.

  • 547 internal links, 19 external

    The homepage links to 547 pages on keelerhardware.com.au and 19 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Keeler Hardware are renowned suppliers of Door and Architectural Hardware at the best prices. Browse our wide range tod…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Keeler Hardware | Door Hardware Supplier of Choice Australia”.

  • Canonical URL set

    The canonical URL is https://www.keelerhardware.com.au/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.keelerhardware.com.au/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,932 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.keelerhardware.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

    https://www.keelerhardware.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.keelerhardware.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://www.keelerhardware.com.au/collections/all, https://www.keelerhardware.com.au/customer_authentication/redirect, https://www.keelerhardware.com.au/policies/shipping-policy, https://www.keelerhardware.com.au/blogs/blog and https://www.keelerhardware.com.au/blogs/buying-guides have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://www.keelerhardware.com.au/collections/door-handles-knobs/entrance-pull-handles, https://www.keelerhardware.com.au/collections/door-handles-knobs/front-door-handles, https://www.keelerhardware.com.au/collections/door-handles-knobs/door-knobs, https://www.keelerhardware.com.au/collections/door-handles-knobs/door-handle-accessories, https://www.keelerhardware.com.au/collections/door-handles-knobs/lever-furniture and https://www.keelerhardware.com.au/collections/door-handles-knobs/front-door-locks and 1 other use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.keelerhardware.com.au/collections/all, https://www.keelerhardware.com.au/customer_authentication/redirect, https://www.keelerhardware.com.au/policies/shipping-policy, https://www.keelerhardware.com.au/pages/about-us, https://www.keelerhardware.com.au/blogs/blog and https://www.keelerhardware.com.au/blogs/buying-guides and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

4 to fixGoogle 5474
  • 2 broken images

    2 images failed to load on a phone, for example https://d1wwb03smk0owu.cloudfront.net/pixel?shop=keeler-hardware.myshopify.com&v=54877516535548.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://archipro.com.au/tools/pixel-tracker?id=keeler-hardware' from origin 'https://www.keelerhard…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    33 of 35 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No call to action on the first screen

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

  • Thin social proof

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 746 words of copy

    The homepage carries about 746 words of visible text.

7 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop By”, “START SHOPPING” and “SHOP NOW”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 4 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 4 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 51 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at keelerhardware.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Klaviyo Email Marketing Sms · Simple Section Rules Scheduler · Microsoft Clarity · Qteedy · Elevar Conversion Tracking · Region Restrictions · Upez · Reviews Co Uk Product And Merchant Review Collection · Swym Wishlist Plus · nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on keelerhardware.com.au, including 21 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25