kytrailer.com website review

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

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

Your mobile performance score is 65 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

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

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

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

2 third-party services load with your homepage (Google Tag Manager and cdn-cookieyes.com), adding 152 KiB and 90 ms of main-thread time.

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

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

Desktop scores 92 but mobile only 65. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “green trailer with yellow text”.

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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-10-17, real Chrome visitors' tap response (inp) went from 71 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

KTB_Railgate_3qtr_Rear_Curb_2Y1A3910_36_INCH-1024x523.png weighs 496 KiB. On a phone connection a single image that size takes seconds.

3 images (656 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example KTB_Railgate_3qtr_Rear_Curb_2Y1A3910_36_INCH-1024x523.png at 1,024 px wide, shown at 326 px. Resized copies would save about 44 KiB.

2 images further down the page (160 KiB) 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 0.28 g of CO₂e: 33.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 10 characters: “KY Trailer”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 67 pages on kytrailer.com and 4 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.

There is no https://kytrailer.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/, https://kytrailer.com/careers, https://kytrailer.com/about, https://kytrailer.com/resources, https://kytrailer.com/trailers and https://kytrailer.com/truck-bodies and 10 others all use the title “KY Trailer”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kytrailer.com/careers, https://kytrailer.com/about, https://kytrailer.com/resources, https://kytrailer.com/trailers, https://kytrailer.com/truck-bodies and https://kytrailer.com/parts-services and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kytrailer.com/resources and https://kytrailer.com/marmon-holdings-inc have 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 26 found) and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 4 cookies (measured from a US location before any click).

Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.