Website review, no card needed

goodwillncw.org logo

goodwillncw.org website review

Visit site (opens in a new tab)Reviewed 27 October 202635 issues · 81 checks

This review found 35 issues worth fixing on goodwillncw.org, 13 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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.5 s2.6 sMay 9Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
169 ms134 msMay 9Oct 24165 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026138 ms
May 23, 2026140 ms
May 30, 2026144 ms
Jun 6, 2026143 ms
Jun 13, 2026145 ms
Jun 20, 2026143 ms
Jun 27, 2026142 ms
Jul 4, 2026139 ms
Jul 11, 2026138 ms
Jul 18, 2026139 ms
Jul 25, 2026140 ms
Aug 1, 2026143 ms
Aug 8, 2026147 ms
Aug 15, 2026149 ms
Aug 22, 2026152 ms
Aug 29, 2026159 ms
Sep 5, 2026157 ms
Sep 12, 2026155 ms
Sep 19, 2026157 ms
Sep 26, 2026159 ms
Oct 3, 2026163 ms
Oct 10, 2026164 ms
Oct 17, 2026165 ms
Oct 24, 2026165 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 goodwillncw.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. goodwillncw.org at 0.4 s0.4 s
  2. goodwillncw.org at 0.8 s0.8 s
  3. goodwillncw.org at 1.2 s1.2 s
  4. goodwillncw.org at 1.5 s1.5 s
  5. goodwillncw.org at 1.9 s1.9 s
  6. goodwillncw.org at 2.3 s2.3 s
  7. goodwillncw.org at 2.7 s2.7 s
  8. goodwillncw.org at 3.1 s3.1 s

Speed

9 to fix48
  • Render-blocking requests

    7.5 s

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

  • Reduce unused JavaScript

    3.6 s · 606 KiB

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

  • Mobile performance score: 48

    48/100

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

  • Reduce unused CSS

    900 ms · 184 KiB

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

  • Use efficient cache lifetimes

    750 ms · 315 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, omappapi.com and Facebook and others), adding 1.2 MB and 754 ms of main-thread time.

  • Minify JavaScript

    410 ms · 28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 337 ms

    337 ms

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 136 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

    33 KiB

    Polyfills for old browsers add 33 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.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

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

  • First Contentful Paint: 11.0 s

    11.0 s

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

  • Largest Contentful Paint: 25.3 s

    25.3 s

    Your largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Goodwill NCW”.

  • Time to Interactive: 25.3 s

    25.3 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 347 ms

    347 ms

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 142 ms to 165 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-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 147 ms

    147 ms

    Real visitors wait 147 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 9.2 MB in 285 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 285 requests on a phone: media 6.4 MB (1), scripts 1.8 MB (98) and fonts 394 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 2.6 g of CO₂ per visit

    2.61 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8492
  • 2 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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

3 to fixGoogle 8586
  • Title is short (12 characters)

    Your title is only 12 characters: “Goodwill NCW”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Goodwill NCW” and “Discover More About Goodwill NCW”). One clear main headline is easier for people and search engines.

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

  • 136 internal links, 16 external

    The homepage links to 136 pages on goodwillncw.org and 16 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Goodwill NCW fuels our mission of Elevating People by Eliminating Barriers to Employment creating pathways through sale…”.

  • Canonical URL set

    The canonical URL is https://goodwillncw.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://goodwillncw.org/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://goodwillncw.org/career-excelerate-wisconsin and https://goodwillncw.org/youth-apprenticeship-program have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://goodwillncw.org/about/mvv, https://goodwillncw.org/about/videos, https://goodwillncw.org/career-excelerate-wisconsin and https://goodwillncw.org/project-search 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 38 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 7391
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 478 words of copy

    The homepage carries about 478 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop”, “Contact Us” and “Shop. Donate. Find your nearest location”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 13 cookies set on arrival

    13

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 goodwillncw.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Dreamhost

Company

Employees
1,198
Headquarters
Menasha

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on goodwillncw.org, including 18 speed issues, 3 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

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