Website review, no card needed
huski.co.nz website review
Visit site (opens in a new tab)Reviewed 16 November 202632 issues · 82 checks
This review found 32 issues worth fixing on huski.co.nz, 11 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #12,006 of 123,827 reviewed websitesbeats 87%
- #7,281 of 69,682 online storesbeats 85%
- #7,053 of 63,392 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 152 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 168 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 164 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 172 ms |
| Oct 31, 2026 | 175 ms |
| Nov 7, 2026 | 179 ms |
| Nov 14, 2026 | 177 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
How it loaded on a phone
0.7 s
1.4 s
2.0 s
2.7 s
3.4 s
4.1 s
4.7 s
5.4 s
Speed
Render-blocking requests
2.3 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
450 ms · 702 KiBAbout 702 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and aov.ai and others), adding 2.0 MB and 924 ms of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 412 KiB4 images could be 412 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 389 ms
389 msShopify costs a phone 389 ms of main-thread work and 855 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.
Klaviyo adds 226 ms
226 msKlaviyo costs a phone 226 ms of main-thread work and 649 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.
Use efficient cache lifetimes
50 ms · 246 KiB26 files are served with short cache lifetimes, so returning visitors download them again (246 KiB).
Legacy JavaScript
200 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.
Reduce unused CSS
154 KiBAbout 154 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
24 KiB24 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 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.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Huski black range: tumbler, beer cooler, slim can cooler, w…”.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 283 ms
283 msScripts block taps and scrolling for 283 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 154 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user TTFB: 746 ms
746 msReal visitors wait 746 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.036
0.036The layout barely moves while loading (CLS 0.036, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 493 requests
5.0 MBYour homepage downloads 5.0 MB in 493 requests on a phone: scripts 2.2 MB (143), other files 1.5 MB (271) and images 939 KiB (28). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
231 KiB1 image is downloaded at several times the size a phone draws it, for example Huski-ChampagneFlute-White-2000px_1.jpg at 2,000 px wide, shown at 98 px. Resized copies would save about 231 KiB.
7 images below the first screen load straight away
7 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
142 internal links, 23 external
The homepage links to 142 pages on huski.co.nz and 23 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Keep your drinks at the perfect temperature, longer - beautifully chilled wine, ice-cold beer and refreshing G&T’s. Mak…”.
Title: 37 characters
Your title is a healthy 37 characters: “Huski® | A Better Drinking Experience”.
Canonical URL set
The canonical URL is https://www.huski.co.nz/.
Structured data in place
Structured data found: Organization and WebSite.
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.huski.co.nz/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (886 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.huski.co.nz/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.huski.co.nz/customer_authentication/redirect has no <title>, so Google invents the link text in results.
2 linked pages hidden from search
https://www.huski.co.nz/customer_authentication/redirect and https://www.huski.co.nz/products/huski-short-tumbler-2 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
3 pages without a meta description
https://www.huski.co.nz/collections/all, https://www.huski.co.nz/customer_authentication/redirect and https://www.huski.co.nz/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.huski.co.nz/collections/all, https://www.huski.co.nz/customer_authentication/redirect, https://www.huski.co.nz/products/huski-wine-cooler and https://www.huski.co.nz/products/huski-beer-cooler-2 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 45 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
1 broken image
1 image failed to load on a phone, for example https://www.huski.co.nz/.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
2 checks passed
Tap targets are thumb-sized
13 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 501 words of copy
The homepage carries about 501 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
21 calls to action
The homepage has 21 calls to action, for example “Shop Huski”, “Shop all” and “Shop Smoco”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 55 testimonial or review blocks, a star rating, 4 trust badges and “25,000+ Reviews”.
Analytics in place
Analytics detected: Hotjar.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 2 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.
54 other companies contacted
Loading the homepage contacts 54 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 huski.co.nz, 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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Essential A B Testing · Cozy Country Redirect · Triplewhale · Wrapped · Sales Popup Autoketing Pop · Eg Auto Add To Cart · Okendo · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Aov Cart Drawer · Glo Color Swatch · Delivery Timer · Preorder Now · Smart Menu · Variable Products · chimpstatic.com · cloudfront.net · conversionbear.com · afterpay.com · gorgias.chat · herokuapp.com · 9gtb.com · useamp.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Auckland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on huski.co.nz, including 15 speed issues, 2 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.