regalboats.com website review

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

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

The page has 3,159 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

15 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (iubenda, Accessibe Accessibility Overlay and Google CDN and others), adding 14.0 MB and 576 ms of main-thread time.

Vimeo costs a phone 3 ms of main-thread work and 13.0 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 57 (desktop: 55). Pages that score under 90 lose visitors before the first paint.

iubenda costs a phone 386 ms of main-thread work and 285 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.

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

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

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

8 KiB could be saved by minifying JavaScript.

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

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

3 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Your homepage downloads 37.5 MB in 237 requests on a phone: images 23.1 MB (166), media 13.0 MB (6) and scripts 1.0 MB (36). Under 2 MB keeps phones on slow connections fast.

15 images weigh 9.6 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 43sav-base.jpg at 2,500 px wide, shown at 390 px. Resized copies would save about 717 KiB.

15 images (8.8 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.

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

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

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

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

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

Headings skip levels (h2 → h5, h2 → h4 and h2 → h4), 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.

50 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 194 pages on regalboats.com and 4 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.regalboats.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.regalboats.com/build-your-boat and https://www.regalboats.com/build all use the title “Build Your Boat”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.regalboats.com/our-boats, https://www.regalboats.com/build-your-boat, https://www.regalboats.com/shopping, https://www.regalboats.com/trade-in, https://www.regalboats.com/why-regal-a-family-company and https://www.regalboats.com/ultimate-trim-series and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.regalboats.com/build-your-boat, https://www.regalboats.com/shopping, https://www.regalboats.com/build, https://www.regalboats.com/model/43-sav, https://www.regalboats.com/model/ls2-bowrider and https://www.regalboats.com/model/34-xo and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were 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 longest form asks for 13 fields (10 required). Every extra field lowers completion.

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

The homepage carries about 594 words of visible text.

Opening the homepage sets 8 cookies (measured from a US location before any click).

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.