seattleboat.com website review

About 4.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.

audioeye.com costs a phone 3.3 s of main-thread work and 349 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 2.4 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 11.4 s on main-thread work while loading, 7.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Google CDN and others), adding 3.5 MB and 7.0 s of main-thread time.

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

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

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

Facebook costs a phone 312 ms of main-thread work and 297 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.

dealerspike.net costs a phone 72 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.

8 images could be 111 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.

3 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Desktop scores 53 but mobile only 27. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Made for Memories. Built on Experience. Premium boats, expe…”.

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

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

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

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

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

Your homepage downloads 5.5 MB in 164 requests on a phone: scripts 3.7 MB (65), images 1.2 MB (22) and fonts 304 KiB (6). Under 2 MB keeps phones on slow connections fast.

4 images (944 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.

1 image further down the page (23 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 1.56 g of CO₂e: 187.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

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

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

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

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

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

Your title is 108 characters, so Google will cut it off around 60: “Seattle Boat Co. - New & Used Boats, Parts, Service, and Financing in Seattle, Tapps, Ken…”.

There are 2 <h1> headlines (“YOUR BOATING JOURNEY STARTS HERE” and “Our Mission is simple”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 1300 (line)”.

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

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

The homepage links to 72 pages on seattleboat.com and 15 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 https://www.seattleboat.com/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.seattleboat.com/map-hours-directions-boats-dealership--locations, https://www.seattleboat.com/--inventory, https://www.seattleboat.com/--xfeaturedinventory, https://www.seattleboat.com/credit-financing-boats-dealership--financing, https://www.seattleboat.com/consignment-boats-dealership--consignment and https://www.seattleboat.com/trade-in-value-boats-dealership--xtrade_value and 8 others use the same meta description. A description written for each page earns more clicks.

https://www.seattleboat.com/trade-in-value-boats-dealership--xtrade_value, https://www.seattleboat.com/service-request-boats-dealership--xservice_request and https://www.seattleboat.com/request-parts-boats-dealership--xparts_request have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://seattle-boat-ui.web.app/lahzochat.js' from origin 'https://www.seattleboat.com' has been b…”.

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.

Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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