courageoussailing.org website review

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

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

About 1.9 MB 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.

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

About 166 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 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

5 third-party services load with your homepage (Google Tag Manager, Vimeo and Google Analytics and others), adding 4.3 MB and 548 ms of main-thread time.

Vimeo costs a phone 167 ms of main-thread work and 3.3 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.

Google Tag Manager costs a phone 338 ms of main-thread work and 693 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 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

19 KiB could be saved by minifying JavaScript.

5 KiB could be saved by minifying CSS.

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

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.

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 17.8 MB in 181 requests on a phone: images 13.7 MB (37), scripts 3.4 MB (65) and stylesheets 351 KiB (39). Under 2 MB keeps phones on slow connections fast.

3 images weigh 7.2 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example Video-Thumbnail-with-Play-Button-2026.png at 2,908 px wide, shown at 268 px. Resized copies would save about 2.9 MB.

8 images (8.6 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.

Video-Thumbnail-with-Play-Button-2026.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).

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 25 characters: “Home - Courageous Sailing”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 65 characters: “Community sailing for youth and adults in the greater Boston area”. 70 to 160 characters is enough to sell the click.

There are 14 <h1> headlines (“Raising sails and a new generation of sailors.”, “Wind Powered. Mission Driven.” and “Youth Programming”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

8 links have no real href, so search engines can't follow them.

The homepage links to 128 pages on courageoussailing.org and 5 external pages.

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

There is no /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.

/ap-waiver, /member-portal, /about and /courageous/mission have no meta description, so Google writes the search snippet from whatever text it finds.

/ap-waiver has no <h1> headline, so visitors and search engines get no clear main topic.

/ap-waiver has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/about took over 3 s to send its HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

courageoussailing.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

courageoussailing.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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: 15 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.

There is no form on the homepage, so every lead has to click through to another page first.

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

courageoussailing.org has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 9 cookies, 2 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.