loopearplugs.com website review

Google Tag Manager costs a phone 1.3 s of main-thread work and 1,011 KiB 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 11.8 s on main-thread work while loading, 6.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, PayPal and Yotpo and others), adding 11.9 MB and 3.0 s of main-thread time.

About 1.5 MB of JavaScript is downloaded but never used on this page.

Shopify costs a phone 183 ms of main-thread work and 9.7 MB 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.

30 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

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

PayPal costs a phone 355 ms of main-thread work and 392 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.

Yotpo costs a phone 306 ms of main-thread work and 284 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.

13 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need.

29 KiB JavaScript is shipped twice across bundles.

10 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 33.8 MB in 327 requests on a phone: media 27.9 MB (19), scripts 3.0 MB (116) and images 1.2 MB (45). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example e58123de801de13b598397857fa7b2819b1d7ced.jpg at 2,731 px wide, shown at 122 px. Resized copies would save about 2.2 MB.

3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

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

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

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

Elements with role="none" or role="presentation" have conflicts (7 elements).

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.loopearplugs.com/cdn/shop/files/pandectes-banner-…”.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 167 pages on loopearplugs.com and 7 external pages.

https://www.loopearplugs.com/products/build-your-bundle and https://www.loopearplugs.com/pages/about-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.loopearplugs.com/products/dream, https://www.loopearplugs.com/collections/bundles, https://www.loopearplugs.com/collections/all, https://www.loopearplugs.com/collections/accessories, https://www.loopearplugs.com/pages/earplugs-for-sleeping and https://www.loopearplugs.com/pages/contact and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187130367&Ver=2&mid=ca3c9106-e8e7-46d3-a608-5615a7c8ec28&bo=1&sid=a2aecd60d7f211f1ad297b2a125b710d&vid=a2aee140d7f211f1af5d43e1319d06b5&vids=1&msclkid=N&pi=918639831&l.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 350 words of visible text.

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