kipandco.com website review

87 images could be 7.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 2.0 MB and 1.3 s of main-thread time.

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

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

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

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

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

Klaviyo costs a phone 186 ms of main-thread work and 323 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 176 ms of main-thread work and 374 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.

LoyaltyLion costs a phone 82 ms of main-thread work and 353 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.

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

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

5 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

30 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-31, real Chrome visitors' tap response (inp) went from 154 ms to 169 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.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.8 MB in 529 requests on a phone: images 10.6 MB (123), scripts 2.5 MB (152) and other files 1.3 MB (227). Under 2 MB keeps phones on slow connections fast.

36 images are downloaded at several times the size a phone draws them, for example b6670631-9861-4d9d-a6ac-0062bb4adbe5.jpg at 700 px wide, shown at 191 px. Resized copies would save about 1.8 MB.

1-3Banner_BonBon_480x.gif weighs 637 KiB. On a phone connection a single image that size takes seconds.

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

1 image (637 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 4.18 g of CO₂e: 501.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

There are 3 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 436 pages on kipandco.com and 13 external pages.

https://kipandco.com.au/collections/sun-drift, https://kipandco.com.au/collections/ciao, https://kipandco.com.au/collections/mini-ciao, https://kipandco.com.au/collections/golden, https://kipandco.com.au/collections/glow-bamboo and https://kipandco.com.au/collections/kip-co-x-blinky-bill have no meta description, so Google writes the search snippet from whatever text it finds.

https://kipandco.com.au/collections/new-at-kip-co, https://kipandco.com.au/collections/sun-drift and https://kipandco.com.au/collections/ciao have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://kipandco.com.au/Liquid%20error%20(snippets/product-item%20line%20122):%20invalid%20url%20input.

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 ()”.

32 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

Requests the notification permission on page load.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

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

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

The homepage carries about 491 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo 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 29 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 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.