fleethq.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and Signyfyd and others), adding 1.3 MB and 730 ms of main-thread time.

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

About 93 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

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

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

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 visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

13 images 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' largest content (lcp) went from 7.0 s to 6.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 134 requests on a phone: scripts 2.0 MB (37), fonts 581 KiB (16) and images 315 KiB (37). Under 2 MB keeps phones on slow connections fast.

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

1 element hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Google's crawler is blocked from indexing this page.

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

Structured data found (Corporation and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

No XML sitemap at https://www.goodyeartrucktires.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 76 pages on fleethq.com and 18 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no /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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /en-US/super-regional.html, whose canonical is /en_US/super-regional.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en_US/company/other-goodyear-sites.html, /en_US/tires/by-application, /en_US/tires/by-technology, /en_US/tires/shop-for-tires/smartway-verification, /en_US/tires/by-application/long-haul and /en_US/tires/by-application/mixed-service and 8 others took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'attr')”.

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

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

Large scripts ship without source maps.

15 links from your homepage to your own site are broken, for example https://www.goodyeartrucktires.com/en_US/company/other-goodyear-sites.html (500).

HSTS is set, but max-age is 1 days; one year is the recommended minimum.

Opening https://fleethq.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

goodyeartrucktires.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

goodyeartrucktires.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The page uses urgency cues (a countdown or limited-time wording).

fleethq.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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