Website review, no card needed

benfieldelectric.com logo

benfieldelectric.com website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 83 checks

This review found 26 issues worth fixing on benfieldelectric.com, 10 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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.2 s1.3 sApr 25Oct 101.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.4 s
May 2, 20261.5 s
May 9, 20261.5 s
May 16, 20261.7 s
May 23, 20261.8 s
May 30, 20262.0 s
Jul 18, 20262.1 s
Aug 1, 20261.8 s
Oct 10, 20261.7 s

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 benfieldelectric.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix48
  • Reduce unused JavaScript

    6.0 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.

  • Use efficient cache lifetimes

    1.4 s · 336 KiB

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

  • Mobile performance score: 48

    48/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, hibu.com and Other Google APIs/SDKs and others), adding 2.9 MB and 1.2 s of main-thread time.

  • Google CDN adds 664 ms

    664 ms

    Google CDN costs a phone 664 ms of main-thread work and 1.8 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.

  • Reduce unused CSS

    450 ms · 70 KiB

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

  • Improve image delivery

    300 ms · 105 KiB

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

  • Main-thread work: 3.9 s

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

  • hibu.com adds 213 ms

    213 ms

    hibu.com costs a phone 213 ms of main-thread work and 413 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.

  • Minify CSS

    150 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • 18 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    9 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 35 ms

    35 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 16.8 s

    16.8 s

    Your largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PREMIER INDEPENDENT WHOLESALE ELECTRICAL DISTRIBUTOR Founde…”.

  • Time to Interactive: 29.8 s

    29.8 s

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

  • Speed Index: 10.3 s

    10.3 s

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

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

    +20%

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

  • Total Blocking Time: 338 ms

    338 ms

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

5 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 CLS: 0.01

    0.01

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 792 ms

    792 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 6.0 MB in 138 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 138 requests on a phone: scripts 2.9 MB (45), images 1.5 MB (45) and other files 722 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.71 g

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

3 checks passed
  • 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

3 to fixGoogle 9796
  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Electric Supply | Electrical Supply | Wholesale Electric New York, NY”.

  • 20 links crawlers can't follow

    20 links have no real href, so search engines can't follow them.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 40 internal links, 10 external

    The homepage links to 40 pages on benfieldelectric.com and 10 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “We offer a large selection of control system services and solutions. Over 400 years of combined experience. Delivery se…”.

  • One H1 headline

    Your main headline reads: “Premier Independent Wholesale Electrical Distributor”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness 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://www.benfieldelectric.com/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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 linked pages hidden from search

    https://www.benfieldelectric.com/line-cards and https://www.benfieldelectric.com/blog are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a meta description

    https://www.benfieldelectric.com/upper-management and https://www.benfieldelectric.com/code-of-conduct use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error registering recaptcha for form "Inline Form Created 2023/05/15, 12:32:09 PM" TypeError: Cannot read properties of…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    37 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • No social proof

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

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

    The homepage carries about 834 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a Quote” and “Call For A Quote”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Request a Quote”, “Call For A Quote” and “Learn More”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 benfieldelectric.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
jQuery
Analytics
Google Tag Manager

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 benfieldelectric.com, including 15 speed issues, 3 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