trailerplans.com website review

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

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

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

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

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

Google Tag Manager costs a phone 528 ms of main-thread work and 543 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 496 KiB of JavaScript is downloaded but never used on this page.

Facebook costs a phone 250 ms of main-thread work and 259 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.

Clarity costs a phone 257 ms of main-thread work and 30 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.

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

Google CDN costs a phone 169 ms of main-thread work and 299 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.

Shopify costs a phone 82 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.

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

About 27 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.

Polyfills for old browsers add 20 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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “What type of trailer are you building?”.

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

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

Your homepage downloads 4.0 MB in 394 requests on a phone: scripts 1.7 MB (84), other files 1.3 MB (231) and fonts 517 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

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

3 images have no alt text, which hurts accessibility and image search.

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

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 173 pages on trailerplans.com and 4 external pages.

https://thetrailerpartsoutlet.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://thetrailerpartsoutlet.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://thetrailerpartsoutlet.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://thetrailerpartsoutlet.com/collections/sale-page-2021, whose canonical is https://thetrailerpartsoutlet.com/collections/specials. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://thetrailerpartsoutlet.com/collections/trailer-axles, https://thetrailerpartsoutlet.com/collections/tk-trailer-kits, https://thetrailerpartsoutlet.com/collections/axle-suspension, https://thetrailerpartsoutlet.com/collections/trailer-axle-repair-parts, https://thetrailerpartsoutlet.com/customer_authentication/redirect and https://thetrailerpartsoutlet.com/pages/tracking have no <h1> headline, so visitors and search engines get no clear main topic.

https://thetrailerpartsoutlet.com/collections/tk-trailer-kits has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 102 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=187075202&Ver=2&mid=80729714-2568-4803-88b4-aa52a13ee3c3&bo=1&sid=6bf94ed0de8011f1bbee3d99fb8da0b4&vid=6bf97770de8011f19c1f8dd8d67b7d38&vids=1&msclkid=N&pi=918639831&l.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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