Website review, no card needed

caboces.org logo

caboces.org website review

Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 83 checks

This review found 40 issues worth fixing on caboces.org, 14 of them high impact, across 83 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
4.0 s3.5 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.9 s
Oct 10, 20263.8 s
Oct 17, 20263.9 s
Oct 24, 20263.8 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
96 ms85 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202687 ms
May 30, 202686 ms
Jun 6, 202688 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202689 ms
Jul 4, 202689 ms
Jul 11, 202692 ms
Jul 18, 202693 ms
Jul 25, 202690 ms
Aug 1, 202688 ms
Aug 8, 202689 ms
Aug 15, 202689 ms
Aug 22, 202689 ms
Aug 29, 202687 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202689 ms
Oct 10, 202691 ms
Oct 17, 202692 ms
Oct 24, 202695 ms
Oct 31, 202695 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 caboces.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix80
  • Render-blocking requests

    2.3 s

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

  • Use efficient cache lifetimes

    250 ms · 3.7 MB

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

  • Improve image delivery

    1.0 MB

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

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    490 ms · 156 KiB

    About 156 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 490 ms faster on a phone.

  • Minify JavaScript

    150 ms · 44 KiB

    44 KiB could be saved by minifying JavaScript.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Facebook, jQuery CDN and Cloudflare CDN and others), adding 302 KiB and 73 ms of main-thread time.

  • Font display

    100 ms

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

  • Document request latency

    27 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused CSS

    10 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 41 ms

    41 ms

    Your server sent the HTML in 41 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.

  • Real-user FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Largest Contentful Paint: 3.7 s

    3.7 s

    Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The CABOCES partners with its 22 component school districts…”. Most of its time is element render delay (2.7 s).

  • Speed Index: 5.2 s

    5.2 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user INP: 101 ms

    101 ms

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

  • Time to Interactive: 3.7 s

    3.7 s

    The page is fully interactive after 3.7 s.

  • Cumulative Layout Shift: 0.005

    0.005

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix40
  • 4 images over 500 KB

    4 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    810 KiB

    1 image is downloaded at several times the size a phone draws it, for example buses-scaled.jpg at 2,560 px wide, shown at 337 px. Resized copies would save about 810 KiB.

  • Page weight: 4.0 MB in 39 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 39 requests on a phone: images 3.5 MB (18), scripts 252 KiB (6) and fonts 116 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (3.5 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.

  • 1 image below the first screen load straight away

    1 image further down the page (115 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.12 g

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

Accessibility

4 to fixGoogle 7789
  • 5 tap targets too small

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

  • Links look like plain text

    4 links inside paragraphs rely on colour alone to stand out.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

7 to fixGoogle 7569
  • No meta description

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

  • Title is short (7 characters)

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

  • 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 70 internal links, 20 external

    The homepage links to 70 pages on caboces.org and 20 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Cattaraugus-Allegany-Erie-Wyoming BOCES”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

Other pages

4 to fix78
  • 2 pages share a title

    https://caboces.org/event/board-of-education-regular-meeting-12 and https://caboces.org/event/board-of-education-regular-meeting-13 all use the title “Board of Education – Regular Meeting | CA BOCES”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://caboces.org/professional-support-services, https://caboces.org/event/board-of-education-regular-meeting-12 and https://caboces.org/event/board-of-education-regular-meeting-13 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://caboces.org/adult-education, whose canonical is https://caboces.org/education/adult-education. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://caboces.org/resources/human-resources/employment-opportunities, https://caboces.org/adult-education, https://caboces.org/about/board-of-education, https://caboces.org/boces-administration, https://caboces.org/education/career-technical-education and https://caboces.org/education/exceptional-education and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://caboces.org/adult-education took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 9691
  • 14 small tap targets

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

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

4 to fix63
  • 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.

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

    The homepage carries about 378 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Driver Move Request”.

  • 2 short forms

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

  • 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
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 caboces.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
Hosting
Erie 1 BOCES

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on caboces.org, including 13 speed issues, 7 SEO issues and 4 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