Website review, no card needed
dominionelectric.com website review
Visit site (opens in a new tab)Reviewed 4 November 202628 issues · 78 checks
This review found 28 issues worth fixing on dominionelectric.com, 12 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 71 ms |
| May 23, 2026 | 69 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 69 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 71 ms |
| Jun 27, 2026 | 72 ms |
| Jul 4, 2026 | 73 ms |
| Jul 11, 2026 | 73 ms |
| Jul 18, 2026 | 73 ms |
| Jul 25, 2026 | 70 ms |
| Aug 1, 2026 | 70 ms |
| Aug 8, 2026 | 71 ms |
| Aug 15, 2026 | 74 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 77 ms |
| Sep 12, 2026 | 72 ms |
| Sep 19, 2026 | 78 ms |
| Sep 26, 2026 | 77 ms |
| Oct 3, 2026 | 76 ms |
| Oct 10, 2026 | 70 ms |
| Oct 17, 2026 | 70 ms |
| Oct 24, 2026 | 71 ms |
| Oct 31, 2026 | 70 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
0.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Render-blocking requests
3.3 s48 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused CSS
1.5 s · 189 KiBAbout 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Reduce unused JavaScript
1.4 s · 267 KiBAbout 267 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
650 ms · 127 KiB3 images could be 127 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Hotjar, Google Tag Manager and jQuery CDN and others), adding 305 KiB and 349 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify CSS
40 ms · 3 KiB3 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
9 KiB2 files are served with short cache lifetimes, so returning visitors download them again (9 KiB).
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 668 ms of it running JavaScript. That is comfortably low.
Server response: 11 ms
11 msYour server sent the HTML in 11 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.
Largest Contentful Paint: 14.7 s
14.7 sYour largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user TTFB: 899 ms
899 msReal visitors wait 899 ms for your server to start answering (75th percentile). Good is under 800 ms.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 239 ms
239 msScripts block taps and scrolling for 239 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 71 ms to 70 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 71 ms
71 msReal visitors wait 71 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 128 requests
3.2 MBYour homepage downloads 3.2 MB in 128 requests on a phone: images 1.5 MB (41), fonts 712 KiB (6) and scripts 615 KiB (29). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (168 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.2 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
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
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
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Dominion Electric | Electrical Supply Store in Virginia & Maryland”.
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.
83 internal links, 38 external
The homepage links to 83 pages on dominionelectric.com and 38 external pages.
7 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “Get access to top-tier components, expert guidance, and streamlined solutions built for demanding projects in every sec…”.
One H1 headline
Your main headline reads: “Dominion Electric Supply, A Division of Border States”.
Canonical URL set
The canonical URL is https://dominionelectric.com/.
Structured data in place
Structured data found: ImageObject, Organization, Person, Service and WebPage.
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://dominionelectric.com/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://dominionelectric.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 (726 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://dominionelectric.com/careers and https://dominionelectric.com/shop-welcome-page are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without a meta description
https://dominionelectric.com/shop-welcome-page and https://dominionelectric.com/commercial have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://dominionelectric.com/commercial, whose canonical is https://dominionelectric.com/commercial-battery-storage-systems. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 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.
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
5 small tap targets
5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 618 words of copy
The homepage carries about 618 words of visible text.
4 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Shop Now” and “Learn More”.
Analytics in place
Analytics detected: Google Analytics and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Hotjar (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
8 other companies contacted
Loading the homepage contacts 8 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 dominionelectric.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
- Analytics
- Google Analytics | Hotjar
- Hosting
- Cloudflare
Hiring
- Hiring
- 5 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on dominionelectric.com, including 13 speed issues, 2 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.