e4wholesale.com website review

6 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.2 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (consentmanager.net, quickcep.com and Google Tag Manager and others), adding 1.9 MB and 1.5 s of main-thread time.

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

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

consentmanager.net costs a phone 389 ms of main-thread work and 143 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.

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

quickcep.com costs a phone 275 ms of main-thread work and 554 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 261 ms of main-thread work and 320 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.

Klaviyo costs a phone 176 ms of main-thread work and 410 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 114 ms of main-thread work and 322 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.

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

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.

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

Your largest element takes 44.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday wholesale sale: spend over $500 for 15% off wi…”.

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

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

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

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

Real visitors wait 241 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors wait 1.1 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.

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

Your homepage downloads 8.1 MB in 364 requests on a phone: images 4.6 MB (54), scripts 2.1 MB (97) and other files 1.1 MB (193). Under 2 MB keeps phones on slow connections fast.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

1 tap target is too small or too close together to hit reliably with a finger.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 70 characters, so Google will cut it off around 60: “Bridesmaid,Evening&Formal Dresses Wholesale|Dropshipping – Ever-Pretty”.

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

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

The homepage links to 171 pages on e4wholesale.com and 8 external pages.

Your Organization JSON-LD is missing 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.

There is no https://www.e4wholesale.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.e4wholesale.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.e4wholesale.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.e4wholesale.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.e4wholesale.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 images are 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

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

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