Website review, no card needed
reliableconsumables.co.nz website review
Visit site (opens in a new tab)Reviewed 16 November 202626 issues · 76 checks
This review found 26 issues worth fixing on reliableconsumables.co.nz, 6 of them high impact, across 76 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
88B- #5,853 of 123,879 reviewed websitesbeats 93%
- #3,179 of 69,702 online storesbeats 93%
- #3,079 of 63,406 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Render-blocking requests
2.2 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 355 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,844 HTML elements
The page has 5,844 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (zohostratus.com.au, zohoecommerce.com and zoho.com.au and others), adding 12.1 MB and 136 ms of main-thread time.
Improve image delivery
1.2 MB19 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
zohoecommerce.com adds 33 ms
33 mszohoecommerce.com costs a phone 33 ms of main-thread work and 11.7 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.
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Reduce initial server response time
503 msReduce initial server response time. Google estimates savings of 503 ms on a phone.
Document request latency
500 msThe HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Server response: 603 ms
603 msYour server takes 603 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Reduce unused CSS
103 KiBAbout 103 KiB of CSS is downloaded but never applied on this page.
Reduce unused JavaScript
61 KiBAbout 61 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.
Core Web Vitals
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.134
0.134The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 4.6 s
4.6 sThe page becomes fully interactive after 4.6 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Total Blocking Time: 118 ms
118 msScripts block the page for only 118 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Cleaning chemicals, paper hygiene, gloves and food packagin…”.
Images and page weight
Page weight: 15.9 MB in 164 requests
15.9 MBYour homepage downloads 15.9 MB in 164 requests on a phone: images 15.2 MB (69), fonts 226 KiB (10) and scripts 162 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 4.5 g of CO₂ per visit
4.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.52 g of CO₂e: 542.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
50 elements hidden from screen readers can still receive keyboard focus.
102 form fields without a label
102 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
31 links without text
31 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 200 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.reliableconsumables.co.nz/Untitled design -…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
483 internal links, 30 external
The homepage links to 483 pages on reliableconsumables.co.nz and 30 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Shop cleaning, packaging, personal care, and office supplies at Reliable Consumables. Quality products for home and bus…”.
One H1 headline
Your main headline reads: “Stock up. Clean up. Pack up.”.
Title: 52 characters
Your title is a healthy 52 characters: “Reliable Consumables | Cleaning & Packaging Supplies”.
Canonical URL set
The canonical URL is https://www.reliableconsumables.co.nz/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.reliableconsumables.co.nz/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.reliableconsumables.co.nz/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.
3 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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,654 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.reliableconsumables.co.nz/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.reliableconsumables.co.nz/wishlist has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://www.reliableconsumables.co.nz/categories/confectionery-and-pie-bags/127697000010019003, https://www.reliableconsumables.co.nz/categories/plates-and-trays/127697000009907128, https://www.reliableconsumables.co.nz/categories/beverage-cups-and-holders/127697000010048145, https://www.reliableconsumables.co.nz/categories/cutlery-and-straws/127697000010048185, https://www.reliableconsumables.co.nz/categories/food-containers/127697000009905767 and https://www.reliableconsumables.co.nz/categories/chemicals/127697000009878004 and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 132 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
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.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
171 of 172 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 880 words of copy
The homepage carries about 880 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 all products” and “Shop”.
27 calls to action
The homepage has 27 calls to action, for example “Shop”, “Sign Up” and “Contact”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 2 trust badges.
Direct contact links
Visitors can reach you directly: 8 phone links and 5 email links.
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
5 cookies set on arrival
5Opening the homepage sets 5 cookies (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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 reliableconsumables.co.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Zoho Commerce, https://www.zoho.com/commerce
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Zoho Corporation PTY LTD
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on reliableconsumables.co.nz, including 14 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.