kingstonbrass.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, starapps.studio and ZenDesk and others), adding 12.2 MB and 1.7 s of main-thread time.

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

starapps.studio costs a phone 371 ms of main-thread work and 9.6 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.

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

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

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

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

ZenDesk costs a phone 172 ms of main-thread work and 431 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.

Attentive costs a phone 85 ms of main-thread work and 356 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.

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

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

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

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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 15.8 MB in 532 requests on a phone: scripts 12.9 MB (157), other files 1.5 MB (205) and images 591 KiB (133). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “Kingston | Handcrafted Kitchen & Bathroom Fixtures - Kingston Brass”.

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

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

The homepage links to 94 pages on kingstonbrass.com and 14 external pages.

https://www.kingstonbrass.com/collections/pull-down-kitchen-faucets, https://www.kingstonbrass.com/collections/pull-out-kitchen-faucets, https://www.kingstonbrass.com/collections/wall-mount-kitchen-faucets, https://www.kingstonbrass.com/collections/bridge-kitchen-faucets and https://www.kingstonbrass.com/collections/laundry-faucets have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kingstonbrass.com/pages/10-off-first-purchase, https://www.kingstonbrass.com/collections/kitchen-sink-faucets, https://www.kingstonbrass.com/collections/pull-down-kitchen-faucets, https://www.kingstonbrass.com/collections/pull-out-kitchen-faucets, https://www.kingstonbrass.com/collections/pre-rinse-kitchen-faucets and https://www.kingstonbrass.com/collections/widespread-kitchen-faucets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 843 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 5 mores (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.

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

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