Website review, no card needed

azoproducts.com logo

azoproducts.com website review

Visit site (opens in a new tab)Reviewed 19 November 202655 issues · 93 checks

This review found 55 issues worth fixing on azoproducts.com, 20 of them high impact, across 93 checks. The most urgent: page weight: 44.6 MB in 444 requests. 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

Real-visitor load time (LCP)75th percentile, phones
6.6 s2.8 sMay 30Nov 145.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.9 s
Jun 13, 20264.1 s
Jun 20, 20264.1 s
Jun 27, 20263.9 s
Jul 4, 20263.8 s
Jul 11, 20263.6 s
Jul 18, 20263.5 s
Jul 25, 20263.3 s
Aug 1, 20263.2 s
Aug 8, 20263.5 s
Aug 15, 20263.9 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20264.2 s
Sep 26, 20264.7 s
Oct 3, 20265.4 s
Oct 10, 20266.1 s
Oct 17, 20266.1 s
Oct 24, 20265.9 s
Oct 31, 20265.6 s
Nov 7, 20265.4 s
Nov 14, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
269 ms209 msMay 30Nov 14233 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026228 ms
Jun 6, 2026238 ms
Jun 13, 2026239 ms
Jun 20, 2026239 ms
Jun 27, 2026237 ms
Jul 4, 2026233 ms
Jul 11, 2026230 ms
Jul 18, 2026222 ms
Jul 25, 2026216 ms
Aug 1, 2026217 ms
Aug 8, 2026225 ms
Aug 15, 2026241 ms
Aug 22, 2026253 ms
Aug 29, 2026260 ms
Sep 5, 2026261 ms
Sep 12, 2026259 ms
Sep 19, 2026261 ms
Sep 26, 2026262 ms
Oct 3, 2026262 ms
Oct 10, 2026260 ms
Oct 17, 2026253 ms
Oct 24, 2026251 ms
Oct 31, 2026247 ms
Nov 7, 2026244 ms
Nov 14, 2026233 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

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

How it loaded on a phone

  1. azoproducts.com at 1.5 s1.5 s
  2. azoproducts.com at 3.0 s3.0 s
  3. azoproducts.com at 4.5 s4.5 s
  4. azoproducts.com at 6.0 s6.0 s
  5. azoproducts.com at 7.4 s7.4 s
  6. azoproducts.com at 8.9 s8.9 s
  7. azoproducts.com at 10.4 s10.4 s
  8. azoproducts.com at 11.9 s11.9 s

Speed

14 to fix33
  • Render-blocking requests

    3.0 s

    18 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 9.5 s

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

  • 3,351 HTML elements

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

  • Reduce unused JavaScript

    900 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and rebuyengine.com and others), adding 2.5 MB and 1.5 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 410 KiB

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

  • 19 long tasks on the main thread

    19 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

  • Google Tag Manager adds 747 ms

    747 ms

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

  • Reduce unused CSS

    450 ms · 99 KiB

    About 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Legacy JavaScript

    450 ms · 92 KiB

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

  • Improve image delivery

    537 KiB

    18 images could be 537 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Klaviyo adds 143 ms

    143 ms

    Klaviyo costs a phone 143 ms of main-thread work and 352 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.

  • rebuyengine.com adds 132 ms

    132 ms

    rebuyengine.com costs a phone 132 ms of main-thread work and 337 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.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Duplicated JavaScript

    71 KiB

    71 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

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

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Largest Contentful Paint: 14.3 s

    14.3 s

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

  • Time to Interactive: 32.7 s

    32.7 s

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

  • Speed Index: 11.4 s

    11.4 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

    The 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 s

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

  • Real-user INP: 230 ms

    230 ms

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

  • Largest content (LCP) got 40% slower for real visitors

    +40%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.6 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 21 images without width and height

    21 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 228 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 758 ms

    758 ms

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

6 to fix19
  • Page weight: 44.6 MB in 444 requests

    44.6 MB

    Your homepage downloads 44.6 MB in 444 requests on a phone: media 39.1 MB (4), scripts 2.9 MB (127) and images 1.2 MB (56). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    1.1 MB

    8 images are downloaded at several times the size a phone draws them, for example azo-urinary-journey-lineup.webp at 1,400 px wide, shown at 350 px. Resized copies would save about 1.1 MB.

  • 8 images in older formats

    8 images (2.5 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.

  • 7 images below the first screen load straight away

    7 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    menu-credential-badge-mobile.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 12.6 g of CO₂ per visit

    12.64 g

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

Accessibility

10 to fixGoogle 8488
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 19 images without alt text

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

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 8580
  • No H1 headline

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

  • Meta description is long (300 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 131 internal links, 15 external

    The homepage links to 131 pages on azoproducts.com and 15 external pages.

5 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Yeast Infection & UTI Symptom Relief Products - AZO®”.

  • Canonical URL set

    The canonical URL is https://azoproducts.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://azoproducts.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 2 pages without a meta description

    https://azoproducts.com/customer_authentication/redirect and https://azoproducts.com/pages/find-a-store have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://azoproducts.com/collections/all, https://azoproducts.com/customer_authentication/redirect, https://azoproducts.com/collections/most-popular, https://azoproducts.com/collections/menopause-relief, https://azoproducts.com/collections/bladder-health and https://azoproducts.com/collections/bundles and 3 others 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 63 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=140001110&tm=gtm002&Ver=2&mid=d74dd8e9-0f87-46fb-aa94-5909d1f9892c&bo=1&sid=fb0b7050e44111f1b7bd3beb660a576d&vid=fb0b9a30e44111f1abd2b9b6562ffaf3&vids=1&msclkid=N&pi=9.

  • 11 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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 1,150 words of copy

    The homepage carries about 1,150 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” and “CONTACT US”.

  • 10 calls to action

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

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks and 3 trust badges.

  • 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
  • 11 trackers load before any consent

    11

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

  • 30 cookies set on arrival

    30

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

  • 56 other companies contacted

    Loading the homepage contacts 56 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 azoproducts.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

Consentmo Gdpr · Klaviyo Email Marketing Sms · Gdpr Backpack · rechargecdn.com · yotpo.com · revenuehunt.com · rebuyengine.com · bazaarvoice.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
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Cromwell

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on azoproducts.com, including 25 speed issues, 4 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

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