Website review, no card needed

zenwiseportal.com logo

zenwiseportal.com website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 72 checks

This review found 33 issues worth fixing on zenwiseportal.com, 16 of them high impact, across 72 checks. The most urgent: avoid multiple page redirects. 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 zenwiseportal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix60
  • Avoid multiple page redirects

    5.1 s

    The page goes through 3 redirects before it starts loading, costing about 5.1 s. Link and advertise the final URL directly.

  • Mobile performance score: 60

    60/100

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

  • Document request latency

    400 ms

    The HTML itself could arrive about 400 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Google Tag Manager adds 199 ms

    199 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google Optimize and Shopify and others), adding 442 KiB and 251 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 38 KiB

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

  • Legacy JavaScript

    150 ms · 12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Reduce unused CSS

    38 KiB

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

  • Use efficient cache lifetimes

    33 KiB

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

  • Improve image delivery

    17 KiB

    1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 to fix67
  • 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 LCP: 5.7 s

    5.7 s

    Real visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 4.4 s

    4.4 s

    Real visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 10.4 s

    10.4 s

    Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zenwise Employee Store Logo”.

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Speed Index: 5.3 s

    5.3 s

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

4 checks passed
  • Real-user INP: 107 ms

    107 ms

    Real visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.07

    0.07

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

  • Total Blocking Time: 176 ms

    176 ms

    Scripts block the page for only 176 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.52 g

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

1 checks passed
  • Page weight: 1.8 MB in 96 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 96 requests on a phone: scripts 1,011 KiB (51), images 311 KiB (7) and fonts 256 KiB (4). That is a lean page.

Accessibility

2 to fixGoogle 10096
  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 5846
  • Page is set to noindex

    The robots meta tag says “noindex nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 29 internal links, 5 external

    The homepage links to 29 pages on zenwiseportal.com and 5 external pages.

5 checks passed
  • Title: 47 characters

    Your title is a healthy 47 characters: “Zenwise Employee Store – Zenwise Employee Store”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Corporation.

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

AI search readiness

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

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

  • llms.txt published

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

Other pages

5 to fix60
  • 1 page without a title

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

  • 10 linked pages hidden from search

    https://zenwiseportal.com/collections/all, https://zenwiseportal.com/pages/employee-store-faq, https://zenwiseportal.com/customer_authentication/redirect, https://zenwiseportal.com/collections/digestive-support, https://zenwiseportal.com/collections/2-0-energy-metabolism and https://zenwiseportal.com/collections/2-0-immune-support and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://zenwiseportal.com/collections/digestive-support and https://zenwiseportal.com/collections/2-0-digestive-support all use the title “Digestive Support – Zenwise Employee Store”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://zenwiseportal.com/collections/all, https://zenwiseportal.com/customer_authentication/redirect, https://zenwiseportal.com/collections/2-0-energy-metabolism, https://zenwiseportal.com/collections/2-0-immune-support, https://zenwiseportal.com/collections/2-0-joint-health and https://zenwiseportal.com/collections/2-0-omegas and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://zenwiseportal.com/customer_authentication/redirect, https://zenwiseportal.com/collections/2-0-energy-metabolism, https://zenwiseportal.com/collections/2-0-immune-support, https://zenwiseportal.com/collections/2-0-joint-health, https://zenwiseportal.com/collections/2-0-omegas and https://zenwiseportal.com/collections/2-0-womens-health and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://cdn.shopify.com/shopifycloud/customer-authentication-web/production/sprite-86bf53.sv…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix60
  • No call to action on the first screen

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

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

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

  • Only about 14 words

    The homepage has only about 14 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

4 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Place your order”, “Shop All” and “BUY NOW”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 8 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 zenwiseportal.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Opinew Reviews · cloudfront.net · rechargecdn.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

E-commerce
Shopify
Analytics
Google Tag Manager
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 zenwiseportal.com, including 12 speed issues, 6 SEO issues and 6 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