isee.ai website review

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

7 images could be 487 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 11.7 MB and 427 ms of main-thread time.

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

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

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

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

imgix costs a phone 0 ms of main-thread work and 641 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.

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

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

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

Desktop scores 96 but mobile only 56. 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.

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

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

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

The page becomes fully interactive after 12.8 s. Good is under 3.8 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 12.3 MB in 36 requests on a phone: media 9.9 MB (5), scripts 1.1 MB (12) and images 644 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

The homepage links to 25 pages on isee.ai and 4 external pages.

There is no https://www.isee.ai/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://www.isee.ai/news, https://www.isee.ai/news/holman-and-isee-partner-to-optimize-utilization-of-autonomous-yard-trucks, https://www.isee.ai/news/freightwaves-isee-partners-with-investor-holman-on-autonomous-yard-trucks, https://www.isee.ai/news/access-newswire-this-innovative-collaboration-combines-isees-autonomous-technology-with-holmans-fleet-leasing-upfitting-and-management-capabilities and https://www.isee.ai/news/freightwaves-how-private-yards-became-autonomous-truckings-most-promising-frontier use the same meta description. A description written for each page earns more clicks.

https://www.isee.ai/news/holman-and-isee-partner-to-optimize-utilization-of-autonomous-yard-trucks, https://www.isee.ai/news/freightwaves-isee-partners-with-investor-holman-on-autonomous-yard-trucks, https://www.isee.ai/news/access-newswire-this-innovative-collaboration-combines-isees-autonomous-technology-with-holmans-fleet-leasing-upfitting-and-management-capabilities and https://www.isee.ai/news/freightwaves-how-private-yards-became-autonomous-truckings-most-promising-frontier have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.isee.ai/contact has 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 10 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

Before a visitor clicks anything, the page loads Google Analytics and 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.

Opening the homepage sets 6 cookies (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.