Website review, no card needed

gsbadgerland.org logo

gsbadgerland.org website review

Visit site (opens in a new tab)Reviewed 21 October 202647 issues · 86 checks

This review found 47 issues worth fixing on gsbadgerland.org, 18 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s2.7 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
May 9, 20263.0 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20263.0 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
130 ms115 msMay 2Oct 17127 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026122 ms
May 9, 2026121 ms
May 16, 2026120 ms
May 23, 2026121 ms
May 30, 2026120 ms
Jun 6, 2026120 ms
Jun 13, 2026120 ms
Jun 20, 2026120 ms
Jun 27, 2026121 ms
Jul 4, 2026119 ms
Jul 11, 2026120 ms
Jul 18, 2026120 ms
Jul 25, 2026119 ms
Aug 1, 2026120 ms
Aug 8, 2026117 ms
Aug 15, 2026120 ms
Aug 22, 2026121 ms
Aug 29, 2026120 ms
Sep 5, 2026121 ms
Sep 12, 2026117 ms
Sep 19, 2026121 ms
Sep 26, 2026121 ms
Oct 3, 2026122 ms
Oct 10, 2026128 ms
Oct 17, 2026127 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

Full-page screenshot of gsbadgerland.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gsbadgerland.org at 0.4 s0.4 s
  2. gsbadgerland.org at 0.8 s0.8 s
  3. gsbadgerland.org at 1.1 s1.1 s
  4. gsbadgerland.org at 1.5 s1.5 s
  5. gsbadgerland.org at 1.9 s1.9 s
  6. gsbadgerland.org at 2.3 s2.3 s
  7. gsbadgerland.org at 2.6 s2.6 s
  8. gsbadgerland.org at 3.0 s3.0 s

Speed

11 to fix58
  • Use efficient cache lifetimes

    3.7 s · 33.7 MB

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

  • Improve image delivery

    1.8 s · 4.7 MB

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

  • Render-blocking requests

    3.1 s

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

  • Reduce unused JavaScript

    2.4 s · 625 KiB

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

  • Mobile performance score: 58

    58/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and truyo.com and others), adding 4.6 MB and 439 ms of main-thread time.

  • Google Tag Manager adds 372 ms

    372 ms

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

  • Minify JavaScript

    300 ms · 67 KiB

    67 KiB could be saved by minifying JavaScript.

  • juicer.io adds 0 ms

    0 ms

    juicer.io costs a phone 0 ms of main-thread work and 3.6 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.

  • Reduce unused CSS

    300 ms · 63 KiB

    About 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 2,004 HTML elements

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

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • 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.

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 565 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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.

  • Largest Contentful Paint: 18.8 s

    18.8 s

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

  • Time to Interactive: 19.3 s

    19.3 s

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

  • First Contentful Paint: 6.0 s

    6.0 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

5 checks passed
  • Real-user INP: 120 ms

    120 ms

    Real visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 497 ms

    497 ms

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

  • Total Blocking Time: 94 ms

    94 ms

    Scripts block the page for only 94 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • 11 images over 500 KB

    11 images weigh 50.2 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 38.1 MB in 94 requests

    38.1 MB

    Your homepage downloads 38.1 MB in 94 requests on a phone: images 36.7 MB (60), scripts 1.2 MB (20) and fonts 93 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    2.8 MB

    10 images are downloaded at several times the size a phone draws them, for example 37023850 at 1,536 px wide, shown at 250 px. Resized copies would save about 2.8 MB.

  • 20 images in older formats

    20 images (51.7 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.

  • 14 images below the first screen load straight away

    14 images further down the page (4.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 10.8 g of CO₂ per visit

    10.81 g

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

Accessibility

7 to fixGoogle 8891
  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (1 element)

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (28 elements)

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

  • 6 form fields without a label

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 8269
  • No meta description

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

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at gsbadgerland.org/robots.txt, the first file search crawlers ask for.

  • 7 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • 134 internal links, 40 external

    The homepage links to 134 pages on gsbadgerland.org and 40 external pages.

2 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Girl Scouts of Badgerland Wisconsin”.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gsbadgerland.org/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.gsbadgerland.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,307 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 8 pages without a meta description

    https://www.gsbadgerland.org/en/articles/support-badgerland-girl-scouts-in-our-2026-fall-fundraiser.html, https://www.gsbadgerland.org/en/activities/mybadgerland.html, https://www.gsbadgerland.org/en/activities/cookies/cookie-central.html, https://www.gsbadgerland.org/en/activities/cookies/bff.html, https://www.gsbadgerland.org/en/activities/camp-and-outdoors/camp-2026.html and https://www.gsbadgerland.org/en/discover/about/what-girl-scouts-do.html and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://accstorefront.ccifn5lai-girlscout1-p6-public.model-t.cc.commerce.ondemand.comnull/.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    12 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 42 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

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

  • 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 342 words of copy

    The homepage carries about 342 words of visible text.

3 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “SHOP”, “Contact Us Contact Us” and “Join a Troop Join a Troop”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 gsbadgerland.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on gsbadgerland.org, including 19 speed issues, 7 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25