Website review, no card needed

necco.org logo

necco.org website review

Visit site (opens in a new tab)Reviewed 18 November 202618 issues · 82 checks

This review found 18 issues worth fixing on necco.org, 4 of them high impact, across 82 checks. The most urgent: 9 tap targets too small. 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
1.4 s989 msMay 30Nov 141.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Nov 14, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
103 ms84 msMay 30Nov 1487 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026101 ms
Jun 6, 202698 ms
Jun 13, 202695 ms
Jun 20, 202692 ms
Jun 27, 202688 ms
Jul 4, 202692 ms
Jul 11, 202691 ms
Jul 18, 202694 ms
Jul 25, 202694 ms
Aug 1, 202689 ms
Aug 8, 202694 ms
Aug 15, 202694 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202692 ms
Sep 12, 202690 ms
Sep 19, 202689 ms
Sep 26, 202691 ms
Oct 3, 202690 ms
Oct 10, 202694 ms
Oct 17, 202691 ms
Oct 24, 202688 ms
Oct 31, 202686 ms
Nov 7, 202686 ms
Nov 14, 202687 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 necco.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix91
  • Render-blocking requests

    350 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

  • Google Tag Manager adds 266 ms

    266 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google Analytics and mountain.com and others), adding 509 KiB and 308 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 22 KiB

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

  • Reduce unused JavaScript

    161 KiB

    About 161 KiB of JavaScript is downloaded but never used on this page.

  • Font display

    100 ms

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

  • Improve image delivery

    42 KiB

    3 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    21 KiB

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

  • Reduce unused CSS

    20 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A laughing child rides on a man's shoulders as a woman smil…”.

12 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 86 ms

    86 ms

    Real visitors wait 86 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 FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 592 ms

    592 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

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

    -16%

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 100 ms

    100 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

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

  • About 0.3 g of CO₂ per visit

    0.28 g

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

3 checks passed
  • Page weight: 996 KiB in 61 requests

    996 KiB

    Your homepage downloads 996 KiB in 61 requests on a phone: scripts 582 KiB (25), images 221 KiB (15) and fonts 137 KiB (4). That is a lean page.

  • 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

3 to fixGoogle 9195
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

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

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 14 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10095
  • No structured data

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 59 internal links, 17 external

    The homepage links to 59 pages on necco.org and 17 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Necco supports children of all ages through therapeutic foster care, adoption, and counseling in Ohio, Kentucky, West V…”.

  • One H1 headline

    Your main headline reads: “30 Years of Changing Lives. One Family at a Time.”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Foster Care, Adoption, Independent Living & Counseling | Necco”.

  • Canonical URL set

    The canonical URL is https://www.necco.org/.

  • 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://www.necco.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.necco.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 (368 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 16 pages share a title

    /, https://www.necco.org/foster-care, https://www.necco.org/foster-care/foster-care-in-west-virginia, https://www.necco.org/foster-care/foster-care-in-georgia, https://www.necco.org/foster-care/foster-care-in-kentucky and https://www.necco.org/foster-care/foster-care-in-ohio and 10 others all use the title “Foster Care, Adoption, Independent Living & Counseling | Necco”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.necco.org/foster-care, https://www.necco.org/foster-care/foster-care-in-west-virginia, https://www.necco.org/foster-care/foster-care-in-georgia, https://www.necco.org/foster-care/foster-care-in-kentucky, https://www.necco.org/foster-care/foster-care-in-ohio and https://www.necco.org/foster-care/foster-care-in-tennessee and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.necco.org/foster-or-adopt/select-a-state has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 29 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 10093
  • 4 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 307 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET STARTED HERE”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Get Started Here” and “Learn More About Us”.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 4 cookies set on arrival

    4

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

  • 9 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

Company

Headquarters
Cincinnati

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on necco.org, including 4 speed issues, 2 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