jetboatpilot.com website review

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

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

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

8 third-party services load with your homepage (Google CDN, Shopify and automizely.com and others), adding 1.2 MB and 503 ms of main-thread time.

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

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

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

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

Shopify costs a phone 124 ms of main-thread work and 431 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.

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

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

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

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

4 KiB could be saved by minifying JavaScript.

1 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

images-bgTexture.webp weighs 619 KiB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example images-bgTexture.webp at 2,022 px wide, shown at 390 px. Resized copies would save about 614 KiB.

Your homepage downloads 3.9 MB in 312 requests on a phone: images 1.3 MB (31), scripts 1.3 MB (138) and other files 902 KiB (118). Under 2 MB keeps phones on slow connections fast.

Thrust_Vector_with_Card.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

5 images (984 KiB) 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.

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

Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

All page content should be contained by landmarks: 40 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.

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 106 pages on jetboatpilot.com and 9 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://jetboatpilot.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://jetboatpilot.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://jetboatpilot.com/pages/videos, https://jetboatpilot.com/pages/jetset, https://jetboatpilot.com/pages/sell-my-boat, https://jetboatpilot.com/customer_authentication/redirect, https://jetboatpilot.com/pages/our-clearance-sale and https://jetboatpilot.com/collections/steering-enhancement and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://jetboatpilot.com/customer_authentication/redirect, https://jetboatpilot.com/pages/our-clearance-sale and https://jetboatpilot.com/pages/accessory-picker have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “merchantWidgetScript.addEventListener is not a function”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 314 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 13 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.