ussailing.org website review

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

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

About 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

42 KiB could be saved by minifying JavaScript.

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

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

8 third-party services load with your homepage (Google Tag Manager, userway.org and Cloudflare CDN and others), adding 971 KiB and 414 ms of main-thread time.

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

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 18.4 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 22.8 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

2 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' tap response (inp) went from 96 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.7 MB in 287 requests on a phone: scripts 3.3 MB (152), images 2.6 MB (41) and stylesheets 936 KiB (62). Under 2 MB keeps phones on slow connections fast.

1 image (36 KiB) is 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 2.19 g of CO₂e: 262.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

3 frames have no title, so screen-reader users cannot tell what they contain.

3 tap targets are too small or too close together to hit reliably with a finger.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

78 links have no real href, so search engines can't follow 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 Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 569 pages on ussailing.org and 97 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.ussailing.org/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.ussailing.org/education, https://www.ussailing.org/education/resources/course-calendars, https://www.ussailing.org/education/coursebooks, https://www.ussailing.org/education/instructor, https://www.ussailing.org/athlete-safety and https://www.ussailing.org/education/instructor/resources/re-certification and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ussailing.org/education/coursebooks, https://www.ussailing.org/education/instructor, https://www.ussailing.org/education/instructor/resources/re-certification, https://www.ussailing.org/education/instructor/resources/instructor-insurance, https://www.ussailing.org/education/instructor/resources/poi and https://www.ussailing.org/education/youth took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, 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 8 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.