Website review, no card needed

walterswholesale.com logo

walterswholesale.com website review

Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 89 checks

This review found 44 issues worth fixing on walterswholesale.com, 13 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
4.0 s3.0 sMay 16Oct 313.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.2 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.5 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.8 s
Oct 31, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
133 ms101 msMay 16Oct 31114 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026115 ms
May 30, 2026112 ms
Jun 6, 2026115 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026113 ms
Jul 4, 2026113 ms
Jul 11, 2026121 ms
Jul 18, 2026127 ms
Jul 25, 2026129 ms
Aug 1, 2026123 ms
Aug 8, 2026120 ms
Aug 15, 2026114 ms
Aug 22, 2026115 ms
Aug 29, 2026115 ms
Sep 5, 2026117 ms
Sep 12, 2026121 ms
Sep 19, 2026115 ms
Sep 26, 2026108 ms
Oct 3, 2026105 ms
Oct 10, 2026105 ms
Oct 17, 2026107 ms
Oct 24, 2026109 ms
Oct 31, 2026114 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 walterswholesale.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. walterswholesale.com at 0.6 s0.6 s
  2. walterswholesale.com at 1.2 s1.2 s
  3. walterswholesale.com at 1.8 s1.8 s
  4. walterswholesale.com at 2.4 s2.4 s
  5. walterswholesale.com at 3.0 s3.0 s
  6. walterswholesale.com at 3.6 s3.6 s
  7. walterswholesale.com at 4.2 s4.2 s
  8. walterswholesale.com at 4.8 s4.8 s

Speed

11 to fix69
  • Improve image delivery

    1.2 s · 361 KiB

    8 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Sentry and Accessibe Accessibility Overlay and others), adding 2.4 MB and 1.2 s of main-thread time.

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    150 ms · 635 KiB

    About 635 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.

  • vtexassets.com adds 568 ms

    568 ms

    vtexassets.com costs a phone 568 ms of main-thread work and 1.5 MB 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.

  • Use efficient cache lifetimes

    150 ms · 281 KiB

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

  • Reduce unused CSS

    300 ms · 66 KiB

    About 66 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.

  • Sentry adds 285 ms

    285 ms

    Sentry costs a phone 285 ms of main-thread work and 91 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.3 s

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

  • Accessibe Accessibility Overlay adds 163 ms

    163 ms

    Accessibe Accessibility Overlay costs a phone 163 ms of main-thread work and 484 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.

  • Google Tag Manager adds 153 ms

    153 ms

    Google Tag Manager costs a phone 153 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.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

6 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 CLS: 0.26

    0.26

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • Time to Interactive: 15.9 s

    15.9 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • 11 images without width and height

    11 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-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +10%

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

7 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 119 ms

    119 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 519 ms

    519 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.033

    0.033

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

  • Total Blocking Time: 59 ms

    59 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.9 MB in 137 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 137 requests on a phone: scripts 1.8 MB (48), images 863 KiB (32) and HTML 138 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    141 KiB

    3 images are downloaded at several times the size a phone draws them, for example 560e8f79-6f00-4aa1-9944-9b550f3a9639___e4197ed20c704e62378d1 at 1,668 px wide, shown at 367 px. Resized copies would save about 141 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (49 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 8188
  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 4 tap targets too small

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

  • 13 images without alt text

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

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

    All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 21 links without text

    21 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

6 to fixGoogle 8570
  • No H1 headline

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

  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “Walters Wholesale Electric | Electrical Supplies & Solutions in Southern California”.

  • Meta description is long (246 characters)

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

  • Structured data has 1 problem

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

  • No social preview image

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

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 72 internal links, 1 external

    The homepage links to 72 pages on walterswholesale.com and 1 external page.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.walterswholesale.com/.

  • 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://hzelectric.myvtex.com/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://www.walterswholesale.com/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 (171 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 1 linked page hidden from search

    https://www.walterswholesale.com/conduit is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages share a title

    https://www.walterswholesale.com/conduit-and-fittings/strut-and-fittings, https://www.walterswholesale.com/conduit-and-fittings/raceway-and-wiring-ducts, https://www.walterswholesale.com/industrial-controls-and-automation/motor-control, https://www.walterswholesale.com/industrial-controls-and-automation/control-stations-and-control-panels, https://www.walterswholesale.com/industrial-controls-and-automation/plcs-and-hmi and https://www.walterswholesale.com/datacom/audio-and-video and 3 others all use the title “Walters Wholesale Electric”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://www.walterswholesale.com/conduit-and-fittings-page, https://www.walterswholesale.com/conduit-and-fittings/strut-and-fittings, https://www.walterswholesale.com/conduit, https://www.walterswholesale.com/conduit-and-fittings/raceway-and-wiring-ducts, https://www.walterswholesale.com/industrial-controls-and-automation-page and https://www.walterswholesale.com/industrial-controls-and-automation/motor-control and 8 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.walterswholesale.com/eaton, https://www.walterswholesale.com/conduit-and-fittings-page, https://www.walterswholesale.com/conduit-and-fittings/strut-and-fittings, https://www.walterswholesale.com/conduit, https://www.walterswholesale.com/conduit-and-fittings/raceway-and-wiring-ducts and https://www.walterswholesale.com/industrial-controls-and-automation-page and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://www.walterswholesale.com/conduit-and-fittings/strut-and-fittings, https://www.walterswholesale.com/conduit-and-fittings/raceway-and-wiring-ducts, https://www.walterswholesale.com/industrial-controls-and-automation/motor-control, https://www.walterswholesale.com/industrial-controls-and-automation/control-stations-and-control-panels, https://www.walterswholesale.com/industrial-controls-and-automation/plcs-and-hmi and https://www.walterswholesale.com/datacom/audio-and-video and 3 others have 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.

  • 8 pages slow to respond

    https://www.walterswholesale.com/industrial-controls-and-automation/motor-control, https://www.walterswholesale.com/industrial-controls-and-automation/control-stations-and-control-panels, https://www.walterswholesale.com/industrial-controls-and-automation/plcs-and-hmi, https://www.walterswholesale.com/datacom-page, https://www.walterswholesale.com/datacom/audio-and-video and https://www.walterswholesale.com/datacom/coax-connectivity and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26017032&tm=gtm002&Ver=2&mid=16c8c39a-1098-4145-b453-e997f6f1cc4a&bo=1&sid=ab68b460d73611f194b18bd2fdb9f8be&vid=ab68bf70d73611f1a3a89b23e0d195a6&vids=1&msclkid=N&pi=91.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    71 of 78 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 223 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop All” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

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

  • 20 other companies contacted

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

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on walterswholesale.com, including 17 speed issues, 6 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