loudlock.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, lifteragecheck.com and Klaviyo and others), adding 821 KiB and 540 ms of main-thread time.

10 images could be 282 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.

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

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

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

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

6 KiB could be saved by minifying CSS.

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

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

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

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.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.7 MB in 203 requests on a phone: scripts 913 KiB (58), images 809 KiB (50) and other files 748 KiB (79). Under 2 MB keeps phones on slow connections fast.

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

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

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

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

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

Structured data found (Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected non-whitespace character after JSON at position 3)”.

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

Your <h1> is empty.

The homepage links to 132 pages on loudlock.com and 1 external page.

Your homepage links to https://www.loudlock.com/collections/pop-top-vials, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.loudlock.com/pages/contact-us, https://www.loudlock.com/pages/learning-center, https://www.loudlock.com/collections/child-resistant-bags and https://www.loudlock.com/collections/packaging-labels have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.loudlock.com/products/grip-n-rip-mylar-bags-1g-1000ct, https://www.loudlock.com/products/loud-lock-grip-n-pull-mylar-bags-exit-12x9-white-300ct, https://www.loudlock.com/products/loud-lock-grip-n-pull-mylar-bags-exit-12x9-black-300ct and https://www.loudlock.com/products/loud-lock-grip-n-pull-mylar-bags use the same meta description. A description written for each page earns more clicks.

https://www.loudlock.com/pages/learning-center has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'click')”.

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 882 words of visible text.

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