seacoastunited.com website review

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

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

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

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

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

16 KiB could be saved by minifying CSS.

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

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

8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Facebook and others), adding 1.4 MB and 1.3 s of main-thread time.

Google/Doubleclick Ads costs a phone 786 ms of main-thread work and 892 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.

102 KiB could be saved by minifying JavaScript.

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

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

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.

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

Your largest element takes 181.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “7v7 Futures Fall Finale Learn MORE & REGISTER”.

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

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

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

The layout shifts by 0.333 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 2.7 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-17, real Chrome visitors' tap response (inp) went from 78 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

Your homepage downloads 35.6 MB in 109 requests on a phone: images 32.7 MB (29), scripts 2.3 MB (23) and stylesheets 221 KiB (8). Under 2 MB keeps phones on slow connections fast.

2 images weigh 11.8 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example b757e57d-5815-4a1b-ae36-af386d39a567-d369704a-8956-4898-bea2 at 2,348 px wide, shown at 294 px. Resized copies would save about 10.3 MB.

12 images (14.4 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.

13 images further down the page (14.4 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.10 g of CO₂e: 1212.0 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”.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

13 images have no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

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

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

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

Your meta description is only 15 characters: “Seacoast United”. 70 to 160 characters is enough to sell the click.

There are 8 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

No XML sitemap at https://www.seacoastunited.com/sitemap.xml, so Google discovers your pages only by following links.

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 103 pages on seacoastunited.com and 36 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.seacoastunited.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.seacoastunited.com/page/home and / all use the title “Home -- Seacoast United”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.seacoastunited.com/page/about, https://www.seacoastunited.com/page/careers-and-internships, https://www.seacoastunited.com/page/refund-policy, https://www.seacoastunited.com/page/alumni, https://www.seacoastunited.com/page/news and https://www.seacoastunited.com/page/facilities and 9 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.seacoastunited.com/page/about, whose canonical is https://www.seacoastunited.com/site?slug=about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

9 of 38 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.”).

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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