Website review, no card needed
macleanpower.com website review
Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 94 checks
This review found 45 issues worth fixing on macleanpower.com, 19 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72C- #90,689 of 116,487 reviewed websitesbeats 19%
- #56,840 of 66,776 online storesbeats 12%
- #1,796 of 2,670 WooCommerce storesbeats 28%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 6.5 s |
| Jun 6, 2026 | 6.7 s |
| Jun 13, 2026 | 6.8 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.6 s |
| Jul 4, 2026 | 6.4 s |
| Jul 11, 2026 | 6.2 s |
| Jul 18, 2026 | 6.0 s |
| Jul 25, 2026 | 5.9 s |
| Aug 1, 2026 | 6.0 s |
| Aug 8, 2026 | 6.3 s |
| Aug 15, 2026 | 6.5 s |
| Aug 22, 2026 | 6.6 s |
| Aug 29, 2026 | 6.5 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.4 s |
| Sep 19, 2026 | 6.6 s |
| Sep 26, 2026 | 6.6 s |
| Oct 3, 2026 | 7.0 s |
| Oct 10, 2026 | 6.7 s |
| Oct 17, 2026 | 6.6 s |
| Oct 24, 2026 | 6.4 s |
| Oct 31, 2026 | 6.1 s |
| Nov 7, 2026 | 6.2 s |
| Nov 14, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 125 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 119 ms |
| Oct 24, 2026 | 118 ms |
| Oct 31, 2026 | 116 ms |
| Nov 7, 2026 | 121 ms |
| Nov 14, 2026 | 122 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
How it loaded on a phone
2.8 s
5.6 s
8.5 s
11.3 s
14.1 s
16.9 s
19.8 s
22.6 s
Speed
Use efficient cache lifetimes
7.7 s · 3.9 MB142 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).
Render-blocking requests
10.0 s73 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.0 s.
Reduce unused JavaScript
3.1 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
YouTube adds 1.1 s
1.1 sYouTube costs a phone 1.1 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Clarity and others), adding 3.1 MB and 1.8 s of main-thread time.
Reduce unused CSS
600 ms · 172 KiBAbout 172 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Improve image delivery
200 ms · 349 KiB7 images could be 349 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 434 ms. During a long task the page ignores taps.
Google Tag Manager adds 247 ms
247 msGoogle Tag Manager costs a phone 247 ms of main-thread work and 303 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.
1,960 HTML elements
The page has 1,960 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 115 ms
115 msGoogle CDN costs a phone 115 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.
Legacy JavaScript
200 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
150 ms · 49 KiB49 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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 64 ms
64 msYour server sent the HTML in 64 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 9.3 s
9.3 sReal visitors wait 9.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.1 s
6.1 sReal visitors see the first content after 6.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.3 s
4.3 sReal visitors wait 4.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 10.5 s
10.5 sThe first text or image appears after 10.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.8 s
17.8 sYour largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Leading manufacturer of products for electric utility and t…”. Most of its time is resource load delay (7.6 s).
Speed Index: 41.7 s
41.7 sVisually, the page fills in at 41.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 43.9 s
43.9 sThe page becomes fully interactive after 43.9 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 124 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 6.5 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 131 ms
131 msReal visitors wait 131 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 8.3 MB in 224 requests
8.3 MBYour homepage downloads 8.3 MB in 224 requests on a phone: scripts 4.1 MB (95), images 2.9 MB (45) and stylesheets 867 KiB (50). Under 2 MB keeps phones on slow connections fast.
12 images in older formats
12 images (1.0 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.
5 images below the first screen load straight away
5 images further down the page (502 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
18 KiB4 images are downloaded at several times the size a phone draws them, for example DSI-Product-MobileTransformersqu-1024x1022.jpg at 1,024 px wide, shown at 332 px. Resized copies would save about 18 KiB.
About 2.4 g of CO₂ per visit
2.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.36 g of CO₂e: 283.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
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.
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.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 27 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “MacLean Power Systems - Electric Power Utility Product Manufacturer”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
11 links with vague text
11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
259 internal links, 27 external
The homepage links to 259 pages on macleanpower.com and 27 external pages.
5 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “We supply world class products and programs worldwide to fulfill the needs of customers maintaining the electric utilit…”.
Canonical URL set
The canonical URL is https://www.macleanpower.com/.
Structured data in place
Structured data found: ImageObject, Organization, Place, WebPage and WebSite.
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.macleanpower.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.macleanpower.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,132 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://www.macleanpower.com/about-us, https://www.macleanpower.com/product/anchors-utility/8-transmission-pipe-pile, https://www.macleanpower.com/product/anchors-utility/cross-plate-anchors, https://www.macleanpower.com/product/arresters, https://www.macleanpower.com/product/arresters/distribution-arresters and https://www.macleanpower.com/product/arresters/station-and-intermediate-arresters and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.macleanpower.com/about-us and https://www.macleanpower.com/products have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages slow to respond
https://www.macleanpower.com/about-us, https://www.macleanpower.com/products, https://www.macleanpower.com/product/anchors-utility, https://www.macleanpower.com/product/anchors-utility/8-transmission-pipe-pile, https://www.macleanpower.com/product/anchors-utility/cross-plate-anchors and https://www.macleanpower.com/product/arresters and 7 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 131 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “regeneratorRuntime is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 401 words of copy
The homepage carries about 401 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: “Learn More”.
16 calls to action
The homepage has 16 calls to action, for example “Buy America & BABA Certified”, “Contact Us” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
22 other companies contacted
Loading the homepage contacts 22 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 macleanpower.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on macleanpower.com, including 24 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.