Website review, no card needed

accessfund.org logo

accessfund.org website review

Visit site (opens in a new tab)Reviewed 19 October 202637 issues · 84 checks

This review found 37 issues worth fixing on accessfund.org, 16 of them high impact, across 84 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.9 s2.0 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.5 s
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.5 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
154 ms77 msMay 2Oct 1796 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026109 ms
May 9, 2026128 ms
May 16, 2026145 ms
May 23, 2026123 ms
May 30, 2026130 ms
Jun 6, 2026109 ms
Jun 13, 2026106 ms
Jun 20, 2026109 ms
Jun 27, 202698 ms
Jul 4, 202698 ms
Jul 11, 202687 ms
Jul 18, 202686 ms
Jul 25, 202688 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202688 ms
Aug 22, 202689 ms
Aug 29, 202689 ms
Sep 5, 202693 ms
Sep 12, 202696 ms
Sep 19, 2026104 ms
Sep 26, 2026114 ms
Oct 3, 2026109 ms
Oct 10, 2026104 ms
Oct 17, 202696 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 accessfund.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. accessfund.org at 0.4 s0.4 s
  2. accessfund.org at 0.8 s0.8 s
  3. accessfund.org at 1.2 s1.2 s
  4. accessfund.org at 1.6 s1.6 s
  5. accessfund.org at 2.0 s2.0 s
  6. accessfund.org at 2.4 s2.4 s
  7. accessfund.org at 2.8 s2.8 s
  8. accessfund.org at 3.2 s3.2 s

Speed

12 to fix29
  • Improve image delivery

    16.3 s · 3.9 MB

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

  • Reduce unused JavaScript

    7.7 s · 1.4 MB

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

  • Render-blocking requests

    7.6 s

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

  • Use efficient cache lifetimes

    1.2 s · 217 KiB

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

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 4.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Squarespace and Google Tag Manager and others), adding 3.0 MB and 2.2 s of main-thread time.

  • Google CDN adds 734 ms

    734 ms

    Google CDN costs a phone 734 ms of main-thread work and 1.1 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.

  • Squarespace adds 706 ms

    706 ms

    Squarespace costs a phone 706 ms of main-thread work and 1.2 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.

  • Reduce unused CSS

    610 ms · 82 KiB

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

  • Google Tag Manager adds 350 ms

    350 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 56 KiB

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

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

    50 ms

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

Core Web Vitals

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

  • First Contentful Paint: 11.2 s

    11.2 s

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

  • Largest Contentful Paint: 39.6 s

    39.6 s

    Your largest element takes 39.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are America’s Climbing Advocates”.

  • Time to Interactive: 39.7 s

    39.7 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user TTFB: 862 ms

    862 ms

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

  • 2 images without width and height

    2 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-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 111 ms

    111 ms

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

  • Real-user FCP: 1.8 s

    1.8 s

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

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

    -16%

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

4 to fix38
  • Page weight: 11.3 MB in 131 requests

    11.3 MB

    Your homepage downloads 11.3 MB in 131 requests on a phone: images 7.3 MB (19), scripts 2.8 MB (67) and other files 477 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  • 11 images below the first screen load straight away

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

  • 1 image far larger than shown

    79 KiB

    1 image is downloaded at several times the size a phone draws it, for example Access-Fund-HEX.png at 1,500 px wide, shown at 80 px. Resized copies would save about 79 KiB.

  • About 3.2 g of CO₂ per visit

    3.19 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8893
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

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

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

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

  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (11 characters)

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

  • Meta description is long (205 characters)

    Your meta description is 205 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/638927954320c12d805…”.

  • 137 internal links, 8 external

    The homepage links to 137 pages on accessfund.org and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “We are America’s Climbing Advocates”.

  • Canonical URL set

    The canonical URL is https://www.accessfund.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.accessfund.org/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.accessfund.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 (1,198 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.accessfund.org/donate and https://www.accessfund.org/impact-map have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 751 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join” and “Shop”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Join”, “Shop” and “Register an Adopt a Crag”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 8 cookies set on arrival

    8

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 accessfund.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
Squarespace
Analytics
Google Tag Manager

Company

Founded
1991
Headquarters
Boulder

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on accessfund.org, including 22 speed issues and 3 SEO issues. 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