fleetadvantage.com website review

20 images could be 780 KiB 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.

8 third-party services load with your homepage (Google Tag Manager, Vimeo and Adroll and others), adding 8.5 MB and 441 ms of main-thread time.

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

Vimeo costs a phone 123 ms of main-thread work and 7.8 MB 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.

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

About 368 KiB of JavaScript is downloaded but never used on this page.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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

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

The layout shifts by 1.711 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 10.4 MB in 142 requests on a phone: other files 7.5 MB (54), images 1.8 MB (59) and scripts 862 KiB (17). Under 2 MB keeps phones on slow connections fast.

11 images (1.2 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.

14 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example NewLeasevsBuy1.2024.png at 5,192 px wide, shown at 360 px. Resized copies would save about 376 KiB.

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

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 15 characters: “Fleet Advantage”. Between 30 and 65 characters leaves room to say what you do and for whom.

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 35 pages on fleetadvantage.com and 16 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 /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.

/what-we-do, /why-fleet-advantage, /leadership-team, /awards, /community-outreach and /solutions and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /truck-performance-monitoring, whose canonical is /asset-performance-team. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/truck-performance-monitoring took over 3 s to send its HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Bootstrap tooltips require Tether (http://github.hubspot.com/tether/)”.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 475 words of visible text.

DMARC is set to p=none, so mail pretending to be fleetadvantage.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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 6 cookies, 2 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.