Website review, no card needed

exceltruckgroup.com logo

exceltruckgroup.com website review

Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 82 checks

This review found 34 issues worth fixing on exceltruckgroup.com, 12 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
3.7 s2.7 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.4 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.6 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.2 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
115 ms87 msMay 9Oct 24111 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202692 ms
May 16, 202692 ms
May 23, 202691 ms
May 30, 202690 ms
Jun 6, 202693 ms
Jun 13, 202694 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202696 ms
Jul 25, 202697 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202697 ms
Aug 22, 2026103 ms
Aug 29, 2026109 ms
Sep 5, 2026111 ms
Sep 12, 2026110 ms
Sep 19, 2026109 ms
Sep 26, 2026104 ms
Oct 3, 2026105 ms
Oct 10, 2026112 ms
Oct 17, 2026111 ms
Oct 24, 2026111 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 exceltruckgroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. exceltruckgroup.com at 0.4 s0.4 s
  2. exceltruckgroup.com at 0.8 s0.8 s
  3. exceltruckgroup.com at 1.1 s1.1 s
  4. exceltruckgroup.com at 1.5 s1.5 s
  5. exceltruckgroup.com at 1.9 s1.9 s
  6. exceltruckgroup.com at 2.3 s2.3 s
  7. exceltruckgroup.com at 2.6 s2.6 s
  8. exceltruckgroup.com at 3.0 s3.0 s

Speed

10 to fix58
  • Reduce unused JavaScript

    3.8 s · 387 KiB

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

  • Render-blocking requests

    3.4 s

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

  • Reduce unused CSS

    1.1 s · 198 KiB

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

  • Improve image delivery

    600 ms · 1.3 MB

    11 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 58

    58/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, cloudfront.net and Other Google APIs/SDKs and others), adding 1.8 MB and 380 ms of main-thread time.

  • Google CDN adds 266 ms

    266 ms

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

  • 2,286 HTML elements

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

  • cloudfront.net adds 80 ms

    80 ms

    cloudfront.net costs a phone 80 ms of main-thread work and 633 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.

  • Google Tag Manager adds 0 ms

    0 ms

    Google Tag Manager costs a phone 0 ms of main-thread work and 311 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.

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • 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.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 680 ms of it running JavaScript. That is comfortably low.

  • Server response: 39 ms

    39 ms

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

Core Web Vitals

8 to fix67
  • 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 CLS: 0.45

    0.45

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

  • Largest Contentful Paint: 13.7 s

    13.7 s

    Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Building our future Coming Soon”.

  • First Contentful Paint: 7.6 s

    7.6 s

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

  • Time to Interactive: 14.0 s

    14.0 s

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

  • Speed Index: 7.6 s

    7.6 s

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

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

    +21%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

6 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 108 ms

    108 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 40 ms

    40 ms

    Scripts block the page for only 40 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 4.4 MB in 105 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 105 requests on a phone: images 2.3 MB (24), scripts 1.1 MB (15) and other files 349 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.25 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9292
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 29 text elements with low contrast

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 form fields without a label

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

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

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (18 elements).

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9283
  • Title is short (24 characters)

    Your title is only 24 characters: “Home - Excel Truck Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 8 H1 headlines

    There are 8 <h1> headlines (“BUILDING OUR FUTURE”, “ROCK HILL, SC - NOW OPEN!” and “WELCOME TO EXCEL TRUCK GROUP”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 19 links with vague text

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

  • 433 internal links, 41 external

    The homepage links to 433 pages on exceltruckgroup.com and 41 external pages.

5 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Excel Truck Group offers the best quality New & Used Trucks for you. Discover your perfect Truck today. Click here to b…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: AutoDealer, ImageObject, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.exceltruckgroup.com/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

3 checks passed
  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.exceltruckgroup.com/llms.txt (18 KiB, 108 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9293
  • 5 small tap targets

    5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • A 11-field form

    Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

  • 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 766 words of copy

    The homepage carries about 766 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 55 calls to action

    The homepage has 55 calls to action, for example “Join Our Team”, “Order Used Trucks Safely” and “Get A Quote”.

  • Social proof on the page

    Social proof on the homepage: 16 testimonial or review blocks and 3 customer or partner logos.

  • Analytics in place

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

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 exceltruckgroup.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
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on exceltruckgroup.com, including 18 speed issues, 4 SEO issues and 1 conversion gap. 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