ez-level.com website review

About 2.8 MB 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.

Wistia costs a phone 4.3 s of main-thread work and 2.9 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.

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

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

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

8 third-party services load with your homepage (Wistia, YouTube and Google Tag Manager and others), adding 6.4 MB and 6.4 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 344 ms of main-thread work and 504 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 281 ms of main-thread work and 675 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.

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

About 222 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.

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

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

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.

Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Eagles, American flag, cross, and text celebrating 250 year…”.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 119 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.3 MB in 375 requests on a phone: scripts 6.1 MB (158), media 2.8 MB (4) and images 873 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 0ba10d2c-725f-4424-be58-20ecd1985240 at 392 px wide, shown at 104 px. Resized copies would save about 23 KiB.

1 image (63 KiB) is 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.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3, h3 → h5 and h2 → h6), which makes the page harder to scan with a screen reader.

Your title is only 25 characters: “EZ-Level Cabinet Levelers”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“<img src="//www.ez-level.com/cdn/shop/files/EZ-Le…”, “Install Perfectly Level Cabinets in Minutes” and “Step 1 of 2”). One clear main headline is easier for people and search engines.

The homepage links to 48 pages on ez-level.com and 4 external pages.

https://www.ez-level.com/pages/installing_cabinets and https://www.ez-level.com/pages/videos all use the title “Installing Cabinets – EZ-Level”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ez-level.com/collections/store and https://www.ez-level.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ez-level.com/pages/installing_cabinets and https://www.ez-level.com/pages/videos use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ez-level.com/pages/videos, whose canonical is https://www.ez-level.com/pages/installing_cabinets. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ez-level.com/pages/faq, https://www.ez-level.com/pages/how-to-order, https://www.ez-level.com/pages/instructions, https://www.ez-level.com/pages/installing_cabinets, https://www.ez-level.com/pages/dealer-info-new and https://www.ez-level.com/pages/videos and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage 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=11006058&Ver=2&mid=797663c0-8373-4d9b-892c-b1d8baf50c7c&bo=1&sid=f4724200ddce11f1a6c439854083acca&vid=f47258a0ddce11f1931ce320e9dc9ebf&vids=1&msclkid=N&pi=918639831&lg.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

The homepage carries about 1,254 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 25 cookies, 2 of them by other companies (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 60 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.