leatherbackgear.com website review

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

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

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

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

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

8 third-party services load with your homepage (Vimeo, sezzle.com and Privy and others), adding 1.2 MB and 468 ms of main-thread time.

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

Vimeo costs a phone 140 ms of main-thread work and 790 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 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

Your largest element takes 14.2 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 14.2 s. Good is under 3.8 s.

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

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

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

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

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 188 requests on a phone: scripts 1.2 MB (62), other files 741 KiB (98) and images 591 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

7 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Document should not have more than one banner landmark: 1 element on the page fails 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.

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

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

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

There are 2 <h1> headlines (“The Most Important thing you'll ever put into a b…” and “LEATHERBACK GEAR SHOULD BE ONE OF THEM.”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.leatherbackgear.com/search?q={search_term_string}")”.

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

The homepage links to 64 pages on leatherbackgear.com and 21 external pages.

https://www.leatherbackgear.com/collections/armor-inserts, https://www.leatherbackgear.com/collections/leatherback-gear-apparel, https://www.leatherbackgear.com/collections/backpacks and https://www.leatherbackgear.com/collections/training have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.leatherbackgear.com/products/level-iiia-backpack-armor-panel-insert-9x12 and https://www.leatherbackgear.com/products/level-iiia-backpack-armor-panel-insert-11x14 use the same meta description. A description written for each page earns more clicks.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'src'”.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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