leitnerdesigns.com website review

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

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

15 images could be 2.9 MB 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 (YouTube, elfsightcdn.com and Clarity and others), adding 8.5 MB and 1.8 s of main-thread time.

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

YouTube costs a phone 771 ms of main-thread work and 2.5 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.

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

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

Shopify costs a phone 89 ms of main-thread work and 4.4 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.

elfsightcdn.com costs a phone 357 ms of main-thread work and 626 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 116 ms of main-thread work and 333 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 85 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

7 KiB could be saved by minifying JavaScript.

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.

4 KiB could be saved by minifying CSS.

Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1_SHOP_BEDRACKS.webp__PID:2ff10a9e-b419-459f-9164-2dab4d8c0…”.

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

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

The layout shifts by 0.611 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Your homepage downloads 10.8 MB in 360 requests on a phone: images 4.6 MB (35), scripts 3.9 MB (113) and other files 1.0 MB (165). Under 2 MB keeps phones on slow connections fast.

4 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example HOMEPAGE_FEATURED_ACSROOF_bc022156-72ae-4f05-83bc-8b76f9adc6 at 3,000 px wide, shown at 360 px. Resized copies would save about 2.6 MB.

10 images (3.7 MB) are 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.

9 images further down the page (3.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.05 g of CO₂e: 366.5 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.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

Your title is 70 characters, so Google will cut it off around 60: “Truck Bed Rack Systems | Rack Systems for Trucks | LEITNER Designs ACS”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“” and “THE FINEST BED RACKS & PLATFORM RACKS”). One clear main headline is easier for people and search engines.

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

The homepage links to 62 pages on leitnerdesigns.com and 10 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.leitnerdesigns.com/pages/shop-acs-roof-platform-racks, https://www.leitnerdesigns.com/pages/leitner-accessories, https://www.leitnerdesigns.com/pages/trucks-1, https://www.leitnerdesigns.com/blogs/news, https://www.leitnerdesigns.com/pages/warranty-policy and https://www.leitnerdesigns.com/pages/installation and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.leitnerdesigns.com/pages/trucks-1, https://www.leitnerdesigns.com/pages/warranty-claims, https://www.leitnerdesigns.com/pages/install-videos and https://www.leitnerdesigns.com/pages/acs-roof have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.leitnerdesigns.com/collections/parts and https://www.leitnerdesigns.com/products/fierfly-light took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187044418&Ver=2&mid=4a739133-dba7-4908-9c3b-f78483957954&bo=1&sid=3b206af0dca811f19384db5ccbacf5aa&vid=3b20a8d0dca811f1a3e045840537f470&vids=1&msclkid=N&pi=918639831&l.

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

4 of 16 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 “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage carries about 476 words of visible text.

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