Website review, no card needed

acco.org logo

acco.org website review

Visit site (opens in a new tab)Reviewed 8 November 202649 issues · 94 checks

This review found 49 issues worth fixing on acco.org, 22 of them high impact, across 94 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
3.8 s2.9 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.3 s
Jun 27, 20263.5 s
Jul 4, 20263.7 s
Jul 11, 20263.5 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.1 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
103 ms61 msMay 16Oct 3171 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202683 ms
May 23, 202687 ms
May 30, 202683 ms
Jun 6, 202680 ms
Jun 13, 202674 ms
Jun 20, 202666 ms
Jun 27, 202670 ms
Jul 4, 202671 ms
Jul 11, 202671 ms
Jul 18, 202679 ms
Jul 25, 202680 ms
Aug 1, 202675 ms
Aug 8, 202677 ms
Aug 15, 202674 ms
Aug 22, 202678 ms
Aug 29, 202689 ms
Sep 5, 202695 ms
Sep 12, 202698 ms
Sep 19, 202697 ms
Sep 26, 202691 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202682 ms
Oct 24, 202674 ms
Oct 31, 202671 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 acco.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. acco.org at 0.6 s0.6 s
  2. acco.org at 1.2 s1.2 s
  3. acco.org at 1.8 s1.8 s
  4. acco.org at 2.4 s2.4 s
  5. acco.org at 3.0 s3.0 s
  6. acco.org at 3.6 s3.6 s
  7. acco.org at 4.2 s4.2 s
  8. acco.org at 4.8 s4.8 s

Speed

12 to fix29
  • Improve image delivery

    46.5 s · 21.3 MB

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

  • Use efficient cache lifetimes

    9.0 s · 1.6 MB

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

  • Reduce unused JavaScript

    7.2 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.

  • Font display

    1.9 s

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. 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, givebuttercdn.com and Stripe and others), adding 2.7 MB and 1.3 s of main-thread time.

  • Render-blocking requests

    750 ms

    16 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Google Tag Manager adds 396 ms

    396 ms

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

  • givebuttercdn.com adds 335 ms

    335 ms

    givebuttercdn.com costs a phone 335 ms of main-thread work and 995 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: 3.0 s

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

  • 1,716 HTML elements

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

  • Google Maps adds 128 ms

    128 ms

    Google Maps costs a phone 128 ms of main-thread work and 394 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.

  • Legacy JavaScript

    200 ms · 19 KiB

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

  • Reduce unused CSS

    150 ms · 55 KiB

    About 55 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.

  • 12 long tasks on the main thread

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • 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: 5 ms

    5 ms

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

Core Web Vitals

12 to fix33
  • 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 CLS: 0.31

    0.31

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 66.7 s

    66.7 s

    Your largest element takes 66.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GO GOLD ® AND GIVE”.

  • Time to Interactive: 66.7 s

    66.7 s

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

  • Speed Index: 13.1 s

    13.1 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Cumulative Layout Shift: 0.27

    0.27

    The layout shifts by 0.27 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

  • Total Blocking Time: 581 ms

    581 ms

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

  • 20 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

2 checks passed
  • Real-user INP: 74 ms

    74 ms

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

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

    -15%

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

Images and page weight

5 to fix18
  • Page weight: 27.7 MB in 181 requests

    27.7 MB

    Your homepage downloads 27.7 MB in 181 requests on a phone: images 24.4 MB (53), scripts 2.8 MB (62) and fonts 374 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 21.4 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    16.0 MB

    9 images are downloaded at several times the size a phone draws them, for example SFAC-ACCO-1-copy.png at 2,910 px wide, shown at 300 px. Resized copies would save about 16.0 MB.

  • 23 images in older formats

    23 images (23.2 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.

  • 18 images below the first screen load straight away

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

  • About 7.9 g of CO₂ per visit

    7.86 g

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

Accessibility

8 to fixGoogle 8389
  • 9 text elements with low contrast

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

  • 29 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

  • 20 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 7776
  • No meta description

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

  • Title is short (11 characters)

    Your title is only 11 characters: “Home - ACCO”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 31 links with vague text

    31 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Because Kids Can't Fight Cancer Alone...” and “Welcome to ACCO Fighting for Nearly 50 Years for …”). One clear main headline is easier for people and search engines.

  • 484 internal links, 31 external

    The homepage links to 484 pages on acco.org and 31 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://www.acco.org/sitemap_index.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.acco.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 (4,420 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.acco.org/the-grassroots-e-bulletin, https://www.acco.org/18-loop-acco, https://www.acco.org/2025-state-proclamations, https://www.acco.org/24-hour-online-support, https://www.acco.org/30smiles and https://www.acco.org/50th-anniversary-auction and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.acco.org/2025-state-proclamations, https://www.acco.org/24-hour-online-support and https://www.acco.org/50th-anniversary-auction took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Thin social proof

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

  • No opening hours

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

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

    The homepage carries about 932 words of visible text.

5 checks passed
  • 44 calls to action

    The homepage has 44 calls to action, for example “Contact ACCO”, “Start a Division or Group” and “Will you join us?”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • 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
  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 3 of them by other companies (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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 acco.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 Analytics
Hosting
Liquid Web

Company

Founded
1970
Headquarters
Bethesda

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on acco.org, including 24 speed issues, 4 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