oa-scouting.org website review

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

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

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

Your mobile performance score is 51 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

About 231 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 952 KiB and 700 ms of main-thread time.

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

Cloudflare CDN costs a phone 16 ms of main-thread work and 368 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.

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

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

About 32 KiB of CSS is downloaded but never applied on this page.

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

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 22.3 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.3 s. Good is under 3.8 s.

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

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

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

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

6 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-17, real Chrome visitors' tap response (inp) went from 83 ms to 81 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.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

OSHA_Registration_Is_Open.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.9 MB in 44 requests on a phone: images 2.8 MB (8), scripts 620 KiB (18) and fonts 373 KiB (8). Under 2 MB keeps phones on slow connections fast.

6 images (2.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.

OSHA_Registration_Is_Open.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).

3 images further down the page (727 KiB) 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 1.10 g of CO₂e: 131.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 70 pages on oa-scouting.org and 19 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://oa-scouting.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://oa-scouting.org/contact, https://oa-scouting.org/history and https://oa-scouting.org/about/organization-structure have no meta description, so Google writes the search snippet from whatever text it finds.

https://oa-scouting.org/about and https://oa-scouting.org/about/vision-mission-purpose use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://oa-scouting.org/contact, whose canonical is https://oa-scouting.org/oa-support. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://oa-scouting.org/contact has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://p.typekit.net/p.css?s=1&k=cau7wbn&ht=tk&f=2005.2006.2009.2010.2028.2029.2032.2033&a=9075313&app=…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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: 5 testimonial or review blocks. 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.

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

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