Website review, no card needed

nongs.ca logo

nongs.ca website review

Visit site (opens in a new tab)Reviewed 13 November 202626 issues · 71 checks

This review found 26 issues worth fixing on nongs.ca, 5 of them high impact, across 71 checks. The most urgent: invalid ARIA attributes. 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 nongs.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nongs.ca at 0.6 s0.6 s
  2. nongs.ca at 1.2 s1.2 s
  3. nongs.ca at 1.9 s1.9 s
  4. nongs.ca at 2.5 s2.5 s
  5. nongs.ca at 3.1 s3.1 s
  6. nongs.ca at 3.7 s3.7 s
  7. nongs.ca at 4.4 s4.4 s
  8. nongs.ca at 5.0 s5.0 s

Speed

6 to fix67
  • Reduce unused JavaScript

    900 ms · 198 KiB

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

  • Mobile performance score: 67

    67/100

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

  • Use efficient cache lifetimes

    550 ms · 93 KiB

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

  • Render-blocking requests

    600 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Shopify adds 273 ms

    273 ms

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

  • Main-thread work: 2.8 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, POWr and wholesalegorilla.app and others), adding 648 KiB and 476 ms of main-thread time.

  • Duplicated JavaScript

    250 ms · 54 KiB

    54 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 250 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 59 KiB

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

  • 8 long tasks on the main thread

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

  • Improve image delivery

    100 ms · 5 KiB

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

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 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: 9 ms

    9 ms

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

Core Web Vitals

4 to fix65
  • Largest Contentful Paint: 9.2 s

    9.2 s

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

  • Time to Interactive: 9.2 s

    9.2 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 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.

2 checks passed
  • Total Blocking Time: 152 ms

    152 ms

    Scripts block the page for only 152 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.55 g

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

4 checks passed
  • Page weight: 1.9 MB in 183 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 183 requests on a phone: scripts 794 KiB (45), other files 736 KiB (101) and images 181 KiB (27). That is a lean page.

  • 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

2 to fixGoogle 9596
  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • [role="img"] and [role="image"] elements must have alternative text (10 elements)

    [role="img"] and [role="image"] elements must have alternative text: 10 elements on the page fail this check, rated serious by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 4 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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

3 to fixGoogle 8581
  • No meta description

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

  • Title is short (25 characters)

    Your title is only 25 characters: “Purapharm Supplier Portal”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 58 internal links, 4 external

    The homepage links to 58 pages on nongs.ca and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Our Story”.

  • Canonical URL set

    The canonical URL is https://nongs.ca/.

  • Structured data in place

    Structured data found: Organization 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://nongs.ca/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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

6 to fix69
  • 1 linked page hidden from search

    https://nongs.ca/pages/ws-account-create is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages share 4 titles

    https://nongs.ca/products/%E5%85%AD%E5%91%B3%E5%9C%B0%E9%BB%83%E4%B8%B8%E9%85%8D%E6%96%B9%E9%A1%86%E7%B2%92-liu-wei-di-huang-wan and https://nongs.ca/products/%e5%85%ad%e5%91%b3%e5%9c%b0%e9%bb%83%e4%b8%b8%e9%85%8d%e6%96%b9%e9%a1%86%e7%b2%92-liu-wei-di-huang-wan all use the title “六味地黃丸配方顆粒 Liu Wei Di Huang Wan – Purapharm Supplier Portal”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://nongs.ca/collections/all, https://nongs.ca/collections/singles-pinyin, https://nongs.ca/collections/single-nong-s-concentrated-chinese-medicine-granules, https://nongs.ca/collections/%E4%BA%8C%E8%87%B3%E4%BA%94%E5%8A%83 and https://nongs.ca/collections/latin-b-c have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://nongs.ca/products/%E5%85%AD%E5%91%B3%E5%9C%B0%E9%BB%83%E4%B8%B8%E9%85%8D%E6%96%B9%E9%A1%86%E7%B2%92-liu-wei-di-huang-wan and https://nongs.ca/products/%e5%85%ad%e5%91%b3%e5%9c%b0%e9%bb%83%e4%b8%b8%e9%85%8d%e6%96%b9%e9%a1%86%e7%b2%92-liu-wei-di-huang-wan use the same meta description. A description written for each page earns more clicks.

  • 6 links to non-canonical URLs

    Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://nongs.ca/products/%E8%8F%8A%E8%8A%B1-flos-chrysanthemi, whose canonical is https://nongs.ca/products/%e8%8f%8a%e8%8a%b1-flos-chrysanthemi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://nongs.ca/pages/ws-account-create and https://nongs.ca/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://nongs.ca/products/%e5%9b%9b%e7%89%a9%e6%b9%af%e9%85%8d%e6%96%b9%e9%a1%86%e7%b2%92-si-wu-tang, https://nongs.ca/products/%E6%A1%91%E8%8F%8A%E9%A3%B2%E9%85%8D%E6%96%B9%E9%A1%86%E7%B2%92-sang-ju-yin and https://nongs.ca/products/%e6%a1%91%e8%8f%8a%e9%a3%b2%e9%85%8d%e6%96%b9%e9%a1%86%e7%b2%92-sang-ju-yin took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 15 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 590 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REGISTER NOW”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Register now”, “LEARN MORE” and “Contact Us”.

  • 6 short forms

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

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.

  • 10 cookies set on arrival

    10

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 nongs.ca, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Wholesale Gorilla · Nova Multi Currency Converter · Quickview · Smart Menu · powr.io

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 26 issues on nongs.ca, including 10 speed issues, 3 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