circuitbreakerguys.dev website review

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

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

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

8 third-party services load with your homepage (Clarity, Google Tag Manager and Shopify and others), adding 1.4 MB and 1.3 s of main-thread time.

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

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

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

Clarity costs a phone 405 ms of main-thread work and 31 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 costs a phone 354 ms of main-thread work and 499 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.

Shopify costs a phone 154 ms of main-thread work and 401 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.

azurefd.net costs a phone 96 ms of main-thread work and 329 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.

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

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

About 51 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.8 MB in 481 requests on a phone: scripts 1.4 MB (147), other files 1.4 MB (266) and images 651 KiB (24). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example young-electrician-workplace_1.png at 1,352 px wide, shown at 360 px. Resized copies would save about 33 KiB.

1 image further down the page (92 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 20 characters: “Circuit Breaker Guys”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to circuitbreakerguys.com, not circuitbreakerguys.dev, so Google may credit that host instead.

There are 2 <h1> headlines (“” and “Find the Part.Restore the Power.”). One clear main headline is easier for people and search engines.

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

The homepage links to 59 pages on circuitbreakerguys.dev and 8 external pages.

There is no https://circuitbreakerguys.dev/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.

https://circuitbreakerguys.dev/collections/all, https://circuitbreakerguys.dev/policies/shipping-policy, https://circuitbreakerguys.dev/pages/about-us, https://circuitbreakerguys.dev/pages/all-products, https://circuitbreakerguys.dev/collections/circuit-breakers and https://circuitbreakerguys.dev/pages/contact and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://circuitbreakerguys.dev/collections/all, https://circuitbreakerguys.dev/pages/all-products, https://circuitbreakerguys.dev/collections/circuit-breakers and https://circuitbreakerguys.dev/collections/transformers have no <h1> headline, so visitors and search engines get no clear main topic.

https://circuitbreakerguys.dev/collections/circuit-breakers took over 3 s to send its HTML from our server.

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

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

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 402 words of visible text.

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

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

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.

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.