jetskicovers.com website review

The page goes through 1 redirect before it starts loading, costing about 4.1 s. Link and advertise the final URL directly.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Unbounce and Affirm and others), adding 1.5 MB and 654 ms of main-thread time.

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

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

Unbounce costs a phone 131 ms of main-thread work and 357 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.

LiveChat costs a phone 90 ms of main-thread work and 364 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 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

5 long tasks block the main thread while loading, the longest for 141 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).

9 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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 3.8 MB in 276 requests on a phone: scripts 1.7 MB (105), images 895 KiB (16) and other files 797 KiB (118). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Custom-fit-LP.jpg at 1,266 px wide, shown at 338 px. Resized copies would save about 28 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.1 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”.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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 12 characters: “JetSkiCovers”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://jetskicovers.com{{ routes.search_u…”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 44 pages on jetskicovers.com and 1 external page.

Your homepage links to https://jetskicovers.com/pages/pontoon-covers, https://jetskicovers.com/pages/bimini-tops, https://jetskicovers.com/pages/car-covers, https://jetskicovers.com/pages/suv-covers, https://jetskicovers.com/pages/truck-covers and https://jetskicovers.com/pages/van-covers and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

https://jetskicovers.com/collections/all, https://jetskicovers.com/pages/boat-covers and https://jetskicovers.com/pages/jetski-covers have no meta description, so Google writes the search snippet from whatever text it finds.

https://jetskicovers.com/pages/guaranteed-fit-sea-doo-jet-ski-covers, https://jetskicovers.com/pages/guaranteed-fit-yamaha-jet-ski-covers, https://jetskicovers.com/pages/guaranteed-fit-kawasaki-jet-ski-covers and https://jetskicovers.com/pages/guaranteed-fit-polaris-jet-ski-covers use the same meta description. A description written for each page earns more clicks.

https://jetskicovers.com/pages/guaranteed-fit-sea-doo-jet-ski-covers, https://jetskicovers.com/pages/guaranteed-fit-yamaha-jet-ski-covers, https://jetskicovers.com/pages/guaranteed-fit-kawasaki-jet-ski-covers, https://jetskicovers.com/pages/guaranteed-fit-polaris-jet-ski-covers, https://jetskicovers.com/collections/all and https://jetskicovers.com/pages/boat-covers and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=11008307&Ver=2&mid=1315d3e3-9859-400f-94ed-8fb1b1b4d719&bo=1&sid=a1e8ed70db2011f1b20691014f67aa5a&vid=a1e8cb80db2011f1862745a296be20ea&vids=1&msclkid=N&pi=918639831&lg.

11 of 21 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: the server responded with a status of 404 ()”.

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

The homepage has only about 144 words of visible text; thin pages give Google and first-time buyers little to go on.

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