Website review, no card needed

cnw.com.au logo

cnw.com.au website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 90 checks

This review found 41 issues worth fixing on cnw.com.au, 15 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
2.6 s1.6 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
201 ms157 msMay 9Oct 24178 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026162 ms
May 16, 2026162 ms
May 23, 2026166 ms
May 30, 2026171 ms
Jun 6, 2026175 ms
Jun 13, 2026179 ms
Jun 20, 2026180 ms
Jun 27, 2026183 ms
Jul 4, 2026179 ms
Jul 11, 2026179 ms
Jul 18, 2026179 ms
Jul 25, 2026179 ms
Aug 1, 2026181 ms
Aug 8, 2026181 ms
Aug 15, 2026188 ms
Aug 22, 2026189 ms
Aug 29, 2026195 ms
Sep 5, 2026196 ms
Sep 12, 2026187 ms
Sep 19, 2026186 ms
Sep 26, 2026183 ms
Oct 3, 2026181 ms
Oct 10, 2026179 ms
Oct 17, 2026179 ms
Oct 24, 2026178 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 cnw.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cnw.com.au at 0.9 s0.9 s
  2. cnw.com.au at 1.9 s1.9 s
  3. cnw.com.au at 2.8 s2.8 s
  4. cnw.com.au at 3.7 s3.7 s
  5. cnw.com.au at 4.7 s4.7 s
  6. cnw.com.au at 5.6 s5.6 s
  7. cnw.com.au at 6.6 s6.6 s
  8. cnw.com.au at 7.5 s7.5 s

Speed

13 to fix34
  • Use efficient cache lifetimes

    4.5 s · 1.3 MB

    140 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Reduce unused JavaScript

    4.5 s · 919 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 34

    34/100

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

  • 4,050 HTML elements

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

  • Improve image delivery

    800 ms · 356 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, purechatcdn.com and Facebook and others), adding 1.7 MB and 974 ms of main-thread time.

  • Google Tag Manager adds 356 ms

    356 ms

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

    300 ms · 68 KiB

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

  • Main-thread work: 3.5 s

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

  • Minify JavaScript

    300 ms · 39 KiB

    39 KiB could be saved by minifying JavaScript.

  • purechatcdn.com adds 199 ms

    199 ms

    purechatcdn.com costs a phone 199 ms of main-thread work and 326 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.

  • Mapbox adds 97 ms

    97 ms

    Mapbox costs a phone 97 ms of main-thread work and 361 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.

  • Legacy JavaScript

    150 ms · 35 KiB

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

  • 9 long tasks on the main thread

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • 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: 355 ms

    355 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 20.7 s

    20.7 s

    Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SAL - New to the Essential Range”.

  • Time to Interactive: 24.3 s

    24.3 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Cumulative Layout Shift: 0.286

    0.286

    The layout shifts by 0.286 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 64 images without width and height

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

  • Total Blocking Time: 437 ms

    437 ms

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 188 ms

    188 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 713 ms

    713 ms

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

Images and page weight

2 to fix81
  • Page weight: 3.6 MB in 258 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 258 requests on a phone: scripts 2.2 MB (113), images 991 KiB (82) and fonts 151 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1790559731_Haier_WebsiteHero-MOB__750x600_480.webp 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 1.0 g of CO₂ per visit

    1.01 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.0 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

5 to fixGoogle 8991
  • Orphan list items

    Some list items are not inside a list.

  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

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

  • 4 images without alt text

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

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 46 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: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10089
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “CNW Electrical Wholesaler | Wholesale Supplier for Electrical Products”.

  • Structured data has 1 problem

    Structured data found (WholesaleStore) but with 1 problem, for example “WholesaleStore: sameAs is not an absolute URL ("https://www.facebook.com/CNWElectrical, https://www…”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 981 internal links, 8 external

    The homepage links to 981 pages on cnw.com.au and 8 external pages.

6 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “100% Australian family owned, CNW Electrical Wholesale has the electrical supplies you need. Start saving now!”.

  • One H1 headline

    Your main headline reads: “CNW Electrical Wholesale”.

  • Canonical URL set

    The canonical URL is https://shop.cnw.com.au/.

  • 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://shop.cnw.com.au:443/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://shop.cnw.com.au/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 (2,799 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 2 linked pages hidden from search

    https://shop.cnw.com.au/store-finder and https://shop.cnw.com.au/tools are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://shop.cnw.com.au/Promotions/Essential-Range/c/ESSENTIALRANGE and https://shop.cnw.com.au/c/ESSENTIALRANGE all use the title “Essential Range | Promotions | All Categories | CNW Electrical Wholes…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://shop.cnw.com.au/store-finder, https://shop.cnw.com.au/c/CNW_BLACKFRIDAY, https://shop.cnw.com.au/Promotions/Essential-Range/c/ESSENTIALRANGE, https://shop.cnw.com.au/suppliers, https://shop.cnw.com.au/tools and https://shop.cnw.com.au/c/ESSENTIALRANGE and 4 others use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://shop.cnw.com.au/c/CNW_BLACKFRIDAY, https://shop.cnw.com.au/Promotions/Essential-Range/c/ESSENTIALRANGE, https://shop.cnw.com.au/c/ESSENTIALRANGE, https://shop.cnw.com.au/c/ALLCATEGORIES, https://shop.cnw.com.au/All-Categories/Switches-and-Sockets/c/SWITCHESANDSOCKETS and https://shop.cnw.com.au/All-Categories/Lighting/c/LIGHTING and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://shop.cnw.com.au/c/ESSENTIALRANGE, https://shop.cnw.com.au/All-Categories/Switches-and-Sockets/c/SWITCHESANDSOCKETS, https://shop.cnw.com.au/All-Categories/Lighting/c/LIGHTING, https://shop.cnw.com.au/c/CABLEANDWIRE, https://shop.cnw.com.au/c/AIRCONDITIONING and https://shop.cnw.com.au/c/AIRCONDITIONER took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Every page has a title

    All 13 pages that loaded have a <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=343179769&tm=gtm002&Ver=2&mid=97a2b36a-5713-48cd-9c1d-0aaba47ea429&bo=1&sid=e3efae50d28711f1849a730ad1df54ac&vid=e3eff7a0d28711f1b68ba56d85cdce3c&vids=1&msclkid=N&gtm_.

  • 36 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://cms.bgwgroup.com.au/components/branches/fetch_random_review.php' from origin 'https://shop.…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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.

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

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

    The homepage carries about 354 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: “Shop Essential Range” and “Shop By Category”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Request”, “Shop Essential Range” and “Shop Electrical”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 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.

  • 24 cookies set on arrival

    24

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 cnw.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Macquarie Technology Operations Pty Limited

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on cnw.com.au, including 20 speed issues, 2 SEO issues and 3 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