Website review, no card needed
blis.co.nz website review
Visit site (opens in a new tab)Reviewed 6 November 202652 issues · 97 checks
This review found 52 issues worth fixing on blis.co.nz, 18 of them high impact, across 97 checks. The most urgent: improve image delivery. 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 92 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 86 ms |
| Jun 27, 2026 | 102 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 102 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 99 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 98 ms |
| Oct 31, 2026 | 116 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
Speed
Improve image delivery
1.6 s · 2.1 MB11 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
3.5 s71 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
YouTube adds 1.3 s
1.3 sYouTube costs a phone 1.3 s of main-thread work and 1,019 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 10.5 s
A phone's processor spends 10.5 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 24
24/100Your mobile performance score is 24. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 2.2 MB and 3.1 s of main-thread time.
Reduce unused JavaScript
2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
750 ms · 259 KiBAbout 259 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google CDN adds 851 ms
851 msGoogle CDN costs a phone 851 ms of main-thread work and 349 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 817 ms. During a long task the page ignores taps.
Google Tag Manager adds 400 ms
400 msGoogle Tag Manager costs a phone 400 ms of main-thread work and 293 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.
Hubspot adds 376 ms
376 msHubspot costs a phone 376 ms of main-thread work and 362 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
323 KiB10 files are served with short cache lifetimes, so returning visitors download them again (323 KiB).
1,612 HTML elements
The page has 1,612 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 159 ms
159 msYour server sent the HTML in 159 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.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.9 s
2.9 sReal visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 31.4 s
31.4 sThe page becomes fully interactive after 31.4 s. Good is under 3.8 s.
Total Blocking Time: 3.5 s
3.5 sScripts block taps and scrolling for 3.5 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 7.8 s
7.8 sYour largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PROBIOTICS MADE TO MATTER WATCH FULL VIDEO”.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Cumulative Layout Shift: 0.164
0.164The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 92 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 6.3 MB in 200 requests
6.3 MBYour homepage downloads 6.3 MB in 200 requests on a phone: images 3.2 MB (32), scripts 2.3 MB (59) and stylesheets 393 KiB (78). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Untitled-design-29.png weighs 731 KiB. On a phone connection a single image that size takes seconds.
4 images in older formats
4 images (1.3 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 below the first screen load straight away
1 image further down the page (731 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
103 internal links, 3 external
The homepage links to 103 pages on blis.co.nz and 3 external pages.
8 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “BLIS strives to improve health through probiotic solutions. We were the pioneers who brought advanced oral probiotics f…”.
One H1 headline
Your main headline reads: “PROBIOTICS MADE TO MATTER”.
Title: 50 characters
Your title is a healthy 50 characters: “Home - BLIS Technologies - probiotic manufacturers”.
Canonical URL set
The canonical URL is https://blis.co.nz/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://blis.co.nz/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://blis.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (745 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://blis.co.nz/work-with-us/ingredients and https://blis.co.nz/ingredients all use the title “Ingredients - BLIS Technologies - probiotic manufacturers”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://blis.co.nz/health-areas/pet-oral-health and https://blis.co.nz/finished-products have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://blis.co.nz/blis-k12 and https://blis.co.nz/blis-synboost use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://blis.co.nz/work-with-us/ingredients, whose canonical is https://blis.co.nz/ingredients. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages slow to respond
https://blis.co.nz/health-areas, https://blis.co.nz/health-areas/dental-health, https://blis.co.nz/health-areas/skin-health, https://blis.co.nz/finished-products and https://blis.co.nz/work-with-us/ingredients took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
16 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 595 words of copy
The homepage carries about 595 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
7 calls to action
The homepage has 7 calls to action, for example “CONTACT US”, “Learn More” and “Download the whitepaper”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies, 1 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.
28 other companies contacted
Loading the homepage contacts 28 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 blis.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 2000
- Headquarters
- Dunedin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on blis.co.nz, including 25 speed issues, 1 SEO issue 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.