ew-ct.com website review

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

vtexassets.com costs a phone 1.1 s of main-thread work and 1.2 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.

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

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

8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Sentry and others), adding 2.2 MB and 2.3 s of main-thread time.

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

Sentry costs a phone 403 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 400 ms.

Accessibe Accessibility Overlay costs a phone 348 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.

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

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

4 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 13.1 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 15.0 s. Good is under 3.8 s.

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

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

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

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

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

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

The layout shifts by 0.159 while loading, so content jumps under the reader's thumb. Good is under 0.1.

7 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 2.5 MB in 139 requests on a phone: scripts 1.8 MB (48), images 462 KiB (35) and HTML 136 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Some list items are not inside a list.

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

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

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

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 on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 82 pages on ew-ct.com and 8 external pages.

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.

There is no https://www.ew-ct.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.

https://www.ew-ct.com/datacom/audio-and-video has no <title>, so Google invents the link text in results.

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

https://www.ew-ct.com/conduit-and-fittings/strut-and-fittings, https://www.ew-ct.com/conduit-and-fittings/raceway-and-wiring-ducts, https://www.ew-ct.com/industrial-controls-and-automation/motor-control, https://www.ew-ct.com/industrial-controls-and-automation/control-stations-and-control-panels, https://www.ew-ct.com/datacom/coax-connectivity and https://www.ew-ct.com/datacom/network-components and 2 others all use the title “Electrical Wholesalers Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ew-ct.com/datacom/audio-and-video has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

https://www.ew-ct.com/promotions, https://www.ew-ct.com/conduit-and-fittings/strut-and-fittings, https://www.ew-ct.com/conduit-and-fittings/raceway-and-wiring-ducts, https://www.ew-ct.com/industrial-controls-and-automation/motor-control, https://www.ew-ct.com/industrial-controls-and-automation/control-stations-and-control-panels and https://www.ew-ct.com/datacom/coax-connectivity 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.

https://www.ew-ct.com/datacom-page and https://www.ew-ct.com/datacom/audio-and-video took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26017032&tm=gtm002&Ver=2&mid=2ffd6a44-8d6b-4dbf-bcae-ec80672c600e&bo=1&sid=5b28cb80d53e11f193937177ad1c4a09&vid=5b28d7c0d53e11f1a46d793788fe1fb9&vids=1&msclkid=N&pi=91.

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 266 words of visible text.

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.

Opening the homepage sets 15 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.