Website review, no card needed
cpcbsa.org website review
Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 86 checks
This review found 39 issues worth fixing on cpcbsa.org, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67D- #107,969 of 120,337 reviewed websitesbeats 9%
- #64,439 of 68,137 online storesbeats 4%
- #2,427 of 2,782 WooCommerce storesbeats 10%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.0 s |
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 134 ms |
| May 2, 2026 | 138 ms |
| May 9, 2026 | 137 ms |
| May 16, 2026 | 136 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 132 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 135 ms |
| Oct 10, 2026 | 134 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Reduce unused JavaScript
23.5 s · 4.3 MBAbout 4.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 23.5 s faster on a phone.
YouTube adds 3.3 s
3.3 sYouTube costs a phone 3.3 s of main-thread work and 7.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
2.7 s · 328 KiBAbout 328 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
1.9 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.6 s
A phone's processor spends 9.6 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Facebook and TikTok and others), adding 8.5 MB and 4.0 s of main-thread time.
Use efficient cache lifetimes
345 KiB16 files are served with short cache lifetimes, so returning visitors download them again (345 KiB).
Improve image delivery
150 ms · 192 KiB5 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
200 ms · 61 KiBPolyfills for old browsers add 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 173 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
First Contentful Paint: 37.4 s
37.4 sThe first text or image appears after 37.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 47.0 s
47.0 sYour largest element takes 47.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Why Scout With Us? Because the Adventure, Grit & Growth You…”.
Speed Index: 37.4 s
37.4 sVisually, the page fills in at 37.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 64.6 s
64.6 sThe page becomes fully interactive after 64.6 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Real-user TTFB: 855 ms
855 msReal visitors wait 855 ms for your server to start answering (75th percentile). Good is under 800 ms.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.121
0.121The layout shifts by 0.121 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 134 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 11.8 MB in 239 requests
11.8 MBYour homepage downloads 11.8 MB in 239 requests on a phone: scripts 7.7 MB (83), images 2.1 MB (39) and fonts 765 KiB (19). Under 2 MB keeps phones on slow connections fast.
21 images below the first screen load straight away
21 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.3 g of CO₂ per visit
3.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.34 g of CO₂e: 400.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (51 elements)
All page content should be contained by landmarks: 51 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
7 H1 headlines
There are 7 <h1> headlines (“Why Scout With Us?”, “Questions about Scouting?” and “New to Scouting?”). One clear main headline is easier for people and search engines.
Meta description is long (233 characters)
Your meta description is 233 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
98 internal links, 59 external
The homepage links to 98 pages on cpcbsa.org and 59 external pages.
5 checks passed
Title: 48 characters
Your title is a healthy 48 characters: “Home - Cascade Pacific Council, Scouting America”.
Canonical URL set
The canonical URL is https://cpcscouting.org/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://cpcscouting.org/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
No llms.txt
There is no https://cpcscouting.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,061 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://cpcscouting.org/adventures, https://cpcscouting.org/summercamp, https://cpcscouting.org/wintercamp, https://cpcscouting.org/weekendcamping, https://cpcscouting.org/upcoming-events/national-jamboree and https://cpcscouting.org/rentals and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages slow to respond
https://cpcscouting.org/summercamp, https://cpcscouting.org/wintercamp, https://cpcscouting.org/upcoming-events/national-jamboree, https://cpcscouting.org/rentals and https://cpcscouting.org/programs/order-of-the-arrow took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “plugin_dir is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 690 words of copy
The homepage carries about 690 words of visible text.
3 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Order of the Arrow”, “Contact” and “Scout Shop”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and TikTok Pixel.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
26 other companies contacted
Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at cpcbsa.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on cpcbsa.org, including 18 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.