Website review, no card needed

gshnj.org logo

gshnj.org website review

Visit site (opens in a new tab)Reviewed 23 October 202652 issues · 91 checks

This review found 52 issues worth fixing on gshnj.org, 22 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
2.5 s2.0 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.3 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
132 ms115 msMay 2Oct 17117 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026124 ms
May 16, 2026119 ms
May 23, 2026119 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026122 ms
Jun 27, 2026122 ms
Jul 4, 2026123 ms
Jul 11, 2026126 ms
Jul 18, 2026124 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026120 ms
Aug 15, 2026121 ms
Aug 22, 2026122 ms
Aug 29, 2026121 ms
Sep 5, 2026125 ms
Sep 12, 2026121 ms
Sep 19, 2026121 ms
Sep 26, 2026120 ms
Oct 3, 2026119 ms
Oct 10, 2026119 ms
Oct 17, 2026117 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 gshnj.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix40
  • Improve image delivery

    6.1 s · 14.2 MB

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

  • Use efficient cache lifetimes

    9.2 s · 6.1 MB

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

  • Reduce unused JavaScript

    3.3 s · 701 KiB

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

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 40

    40/100

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

  • 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 14.9 MB and 1.0 s of main-thread time.

  • juicer.io adds 0 ms

    0 ms

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

    893 ms

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

  • Main-thread work: 2.6 s

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

  • 2,273 HTML elements

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

  • ondemand.com adds 0 ms

    0 ms

    ondemand.com costs a phone 0 ms of main-thread work and 508 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.

  • 11 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 67 KiB

    67 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 63 KiB

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

  • Legacy JavaScript

    200 ms · 8 KiB

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

  • Font display

    50 ms

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

1 checks passed
  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 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: 28.7 s

    28.7 s

    Your largest element takes 28.7 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: 29.5 s

    29.5 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 710 ms

    710 ms

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Tap response (INP) held steady for real visitors

    -7%

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

5 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 396 ms

    396 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • 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
  • Page weight: 19.5 MB in 126 requests

    19.5 MB

    Your homepage downloads 19.5 MB in 126 requests on a phone: images 17.8 MB (86), scripts 1.4 MB (20) and fonts 93 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 12 images over 500 KB

    12 images weigh 10.5 MB together. On a phone connection a single image that size takes seconds.

  • 24 images far larger than shown

    6.4 MB

    24 images are downloaded at several times the size a phone draws them, for example 37339493 at 1,080 px wide, shown at 250 px. Resized copies would save about 6.4 MB.

  • 40 images in older formats

    40 images (14.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.

  • 27 images below the first screen load straight away

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

  • About 5.5 g of CO₂ per visit

    5.54 g

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

Accessibility

10 to fixGoogle 7987
  • 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 contain particular children (1 element)

    Certain ARIA roles must contain particular children: 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 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 images without alt text

    2 images have 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • 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
  • 47 automated accessibility rules passed

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

SEO

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

  • 27 links crawlers can't follow

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

  • 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 gshnj.org/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 89 internal links, 78 external

    The homepage links to 89 pages on gshnj.org and 78 external pages.

2 checks passed
  • Title: 40 characters

    Your title is a healthy 40 characters: “Girl Scouts Heart of New Jersey Homepage”.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gshnj.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.gshnj.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,172 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.gshnj.org/en/support-us/donate-locally/planned-giving-legacy.html, https://www.gshnj.org/en/support-us/camp_appeal.html and https://www.gshnj.org/en/support-us/community-advocate.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.gshnj.org/en/members/for-volunteers/rallyhood.html and https://www.gshnj.org/en/discover/New-Member-Interest.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9276
  • 6 broken images

    6 images failed to load on a phone, for example https://www.juicer.io/api/posts/506656515/images.jpg?external_id=1541395981350573&s=7a2470e0efa6df7af83508bbea032abebb889592.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 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

    13 of 15 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: a star rating. 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 311 words of copy

    The homepage carries about 311 words of visible text.

3 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “SHOP”, “Join Girl Scouts Join Girl Scouts” 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
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 20 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on gshnj.org, including 19 speed issues, 8 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