Website review, no card needed

greatwesterntrailer.com logo

greatwesterntrailer.com website review

Visit site (opens in a new tab)Reviewed 24 October 202654 issues · 99 checks

This review found 54 issues worth fixing on greatwesterntrailer.com, 27 of them high impact, across 99 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.4 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
193 ms79 msMay 2Oct 17173 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202692 ms
May 9, 202694 ms
May 16, 202695 ms
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202693 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 202696 ms
Aug 8, 2026111 ms
Aug 15, 2026128 ms
Aug 22, 2026146 ms
Aug 29, 2026162 ms
Sep 5, 2026164 ms
Sep 12, 2026163 ms
Sep 19, 2026172 ms
Sep 26, 2026177 ms
Oct 3, 2026179 ms
Oct 10, 2026180 ms
Oct 17, 2026173 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of greatwesterntrailer.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. greatwesterntrailer.com at 1.3 s1.3 s
  2. greatwesterntrailer.com at 2.5 s2.5 s
  3. greatwesterntrailer.com at 3.8 s3.8 s
  4. greatwesterntrailer.com at 5.1 s5.1 s
  5. greatwesterntrailer.com at 6.4 s6.4 s
  6. greatwesterntrailer.com at 7.6 s7.6 s
  7. greatwesterntrailer.com at 8.9 s8.9 s
  8. greatwesterntrailer.com at 10.2 s10.2 s

Speed

19 to fix26
  • Use efficient cache lifetimes

    46.3 s · 48.9 MB

    273 files are served with short cache lifetimes, so returning visitors download them again (48.9 MB).

  • Improve image delivery

    17.5 s · 15.9 MB

    52 images could be 15.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.5 s faster on a phone.

  • Reduce unused JavaScript

    12.9 s · 2.8 MB

    About 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.9 s faster on a phone.

  • Render-blocking requests

    9.7 s

    52 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.7 s.

  • Reduce unused CSS

    5.3 s · 888 KiB

    About 888 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.3 s faster on a phone.

  • Font display

    2.2 s

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

  • Minify JavaScript

    1.8 s · 335 KiB

    335 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 511 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Minify CSS

    1.0 s · 169 KiB

    169 KiB could be saved by minifying CSS.

  • Mobile performance score: 26

    26/100

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

  • Main-thread work: 8.0 s

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

  • 3,597 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, CallRail and Accessibe Accessibility Overlay and others), adding 1.8 MB and 3.1 s of main-thread time.

  • CallRail adds 902 ms

    902 ms

    CallRail costs a phone 902 ms of main-thread work and 34 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    400 ms · 100 KiB

    Polyfills for old browsers add 100 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Google CDN adds 309 ms

    309 ms

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

  • Accessibe Accessibility Overlay adds 321 ms

    321 ms

    Accessibe Accessibility Overlay costs a phone 321 ms of main-thread work and 243 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.

  • Document request latency

    302 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 286 ms

    286 ms

    Your server sent the HTML in 286 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.1 s

    4.1 s

    Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.8 s

    3.8 s

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

  • First Contentful Paint: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 78.8 s

    78.8 s

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

  • Speed Index: 25.7 s

    25.7 s

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

  • Time to Interactive: 202.5 s

    202.5 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Real-user INP: 229 ms

    229 ms

    Real visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 90% slower for real visitors

    +90%

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

  • Largest content (LCP) got 42% slower for real visitors

    +42%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 45 images without width and height

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

2 checks passed
  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.059

    0.059

    The layout barely moves while loading (CLS 0.059, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 51.5 MB in 326 requests

    51.5 MB

    Your homepage downloads 51.5 MB in 326 requests on a phone: images 44.4 MB (171), scripts 4.8 MB (82) and stylesheets 1.0 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 13 images over 500 KB

    13 images weigh 9.2 MB together. On a phone connection a single image that size takes seconds.

  • 16 images far larger than shown

    6.8 MB

    16 images are downloaded at several times the size a phone draws them, for example TNT-Equip-HOME-PAGE.png at 1,254 px wide, shown at 124 px. Resized copies would save about 6.8 MB.

  • 16 images in older formats

    16 images (10.1 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.

  • About 14.6 g of CO₂ per visit

    14.58 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 8290
  • 5 buttons without a name

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

  • 4 images without alt text

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

  • 218 links without text

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

  • All page content should be contained by landmarks (47 elements)

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

  • Zoom is disabled

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

  • 5 form fields without a label

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

  • ARIA role should be appropriate for the element (9 elements)

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

  • Elements marked as presentational should be consistently ignored (4 elements)

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 7791
  • 55 links crawlers can't follow

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

  • Meta description is long (167 characters)

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

  • 2 links with vague text

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

  • 320 internal links, 6 external

    The homepage links to 320 pages on greatwesterntrailer.com and 6 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Providing Trailer Solutions Since 1997”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Semi-trailers for Sale & Lease - Great Western Trailer”.

  • Canonical URL set

    The canonical URL is https://www.greatwesterntrailer.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.greatwesterntrailer.com/index.php/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.greatwesterntrailer.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,907 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56298967&tm=gtm002&Ver=2&mid=3522b70d-6b4d-4111-bb98-a7885872a31b&bo=1&sid=4e4a8300cfbd11f190e4fb9d8651dc53&vid=4e4aca50cfbd11f19b300b79f7713228&vids=1&msclkid=N&pi=91.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'on')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    63 of 69 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • A 12-field form

    Your longest form asks for 12 fields (7 required). Every extra field lowers completion.

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 2,590 words of copy

    The homepage carries about 2,590 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST INFO”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Request Loan Payoff Amount”, “Request Title and/or Registration” and “Inquire about a charge”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 21 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 30 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at greatwesterntrailer.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on greatwesterntrailer.com, including 32 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25