Website review, no card needed

omeganzl.com logo

omeganzl.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 75 checks

This review found 33 issues worth fixing on omeganzl.com, 6 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of omeganzl.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. omeganzl.com at 0.4 s0.4 s
  2. omeganzl.com at 0.8 s0.8 s
  3. omeganzl.com at 1.1 s1.1 s
  4. omeganzl.com at 1.5 s1.5 s
  5. omeganzl.com at 1.9 s1.9 s
  6. omeganzl.com at 2.3 s2.3 s
  7. omeganzl.com at 2.6 s2.6 s
  8. omeganzl.com at 3.0 s3.0 s

Speed

8 to fix64
  • Reduce unused JavaScript

    2.4 s · 517 KiB

    About 517 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • 7 third-party services on the page

    7 third-party services load with your homepage (sealsubscriptions.com, Shopify and Klaviyo and others), adding 1.3 MB and 792 ms of main-thread time.

  • sealsubscriptions.com adds 574 ms

    574 ms

    sealsubscriptions.com costs a phone 574 ms of main-thread work and 81 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.

  • 2 long tasks on the main thread

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

  • Main-thread work: 2.5 s

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

  • Shopify adds 127 ms

    127 ms

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

  • 2,059 HTML elements

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

  • Improve image delivery

    250 ms · 76 KiB

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

  • Minify JavaScript

    150 ms · 43 KiB

    43 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    27 KiB

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

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    19 KiB

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

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix61
  • Largest Contentful Paint: 12.3 s

    12.3 s

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

  • Time to Interactive: 12.4 s

    12.4 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Total Blocking Time: 264 ms

    264 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.6 MB in 312 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 312 requests on a phone: scripts 1.2 MB (147), other files 790 KiB (108) and images 307 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    OmegaNZL_Hero_Image_004.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.7 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9495
  • 63 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 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.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “OmegaNZL | Premium New Zealand Health Supplements & Natural Joint Relief”.

  • Meta description is long (187 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, CollectionPage, Dataset and FAQPage) but with 1 problem, for example “ld+json block 3 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

  • One H1 headline

    Your <h1> is empty.

  • 47 internal links, 13 external

    The homepage links to 47 pages on omeganzl.com and 13 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://omeganzl.com/.

  • 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://omeganzl.com/sitemap.xml.

AI search readiness

100
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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (980 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://omeganzl.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

7 to fix55
  • 1 page without a title

    https://omeganzl.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://omeganzl.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share 2 titles

    /, https://omeganzl.com/collections/all, https://omeganzl.com/collections/shop and https://omeganzl.com/pages/contact all use the title “OmegaNZL | Premium New Zealand Health Supplements & Natural Joint Rel…”, and 1 other title repeat too. 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://omeganzl.com/customer_authentication/redirect and https://omeganzl.com/products/detox-nzl-30-capsules have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://omeganzl.com/collections/all, https://omeganzl.com/collections/shop and https://omeganzl.com/pages/contact use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://omeganzl.com/products/omeganzl, whose canonical is https://omeganzl.com/products/omeganzl-60. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://omeganzl.com/collections/all, https://omeganzl.com/customer_authentication/redirect and https://omeganzl.com/collections/shop have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://omeganzl.com/pages/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 5 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No map or directions link

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

  • 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 551 words of copy

    The homepage carries about 551 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop OmegaNZL” and “Call +1-800-791-1585 to Order Now!”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Contact” and “Shop OmegaNZL”.

  • 17 short forms

    17 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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

    4

    Opening the homepage sets 4 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 omeganzl.com, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Ecomposer Builder · Foxify Page Builder · Seal Subscriptions · Klaviyo Email Marketing Sms · Forms · Essential Cart Drawer · younet.network

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

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on omeganzl.com, including 13 speed issues, 4 SEO issues and 2 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25