ecobags.com website review

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

25 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Facebook and others), adding 1.8 MB and 1.1 s of main-thread time.

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

About 715 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

Klaviyo costs a phone 198 ms of main-thread work and 506 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.

Sumo costs a phone 129 ms of main-thread work and 471 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 31 KiB JavaScript that modern phones do not need.

19 KiB could be saved by minifying JavaScript.

16 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying CSS.

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 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three organic cotton mesh bags in light blue, dark blue, an…”.

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

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

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

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

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

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

Your homepage downloads 10.7 MB in 335 requests on a phone: images 7.5 MB (51), scripts 2.1 MB (99) and other files 955 KiB (142). Under 2 MB keeps phones on slow connections fast.

19 images are downloaded at several times the size a phone draws them, for example NL-117-ls.png at 2,000 px wide, shown at 167 px. Resized copies would save about 3.7 MB.

5 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

ecobags-opro-803-holidayhero-02_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (295 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.04 g of CO₂e: 365.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

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

12 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 16 elements on the page fail this check, rated minor by axe-core.

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

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

Headings skip levels (h2 → h4), 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 meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.

4 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 137 pages on ecobags.com and 4 external pages.

https://www.ecobags.com/pages/wholesale, https://www.ecobags.com/pages/custom-printing, https://www.ecobags.com/pages/made-to-order, https://www.ecobags.com/collections/best-sellers, https://www.ecobags.com/collections/produce-bags and https://www.ecobags.com/collections/graphic-bags and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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

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

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

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