mechpowertech.com website review

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

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

2 images could be 1.2 MB 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.

Your mobile performance score is 50 (desktop: 78). Pages that score under 90 lose visitors before the first paint.

The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 938 ms on a phone.

About 844 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 410 ms of main-thread work and 528 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.

Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

6 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google/Doubleclick Ads and others), adding 552 KiB and 417 ms of main-thread time.

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

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

21 KiB could be saved by minifying CSS.

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

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

Desktop scores 78 but mobile only 50. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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.

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

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

Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DESIGN PROTOTYPE MANUFACTURE Custom Parts & Enclosure Solut…”.

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

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

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

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

Your homepage downloads 8.5 MB in 59 requests on a phone: images 5.7 MB (22), scripts 1.6 MB (9) and HTML 724 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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 meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 69 pages on mechpowertech.com and 7 external pages.

https://mechpowertech.com/shop has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

3 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 6 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.