Website review, no card needed

aspanet.org logo

aspanet.org website review

Visit site (opens in a new tab)Reviewed 19 October 202636 issues · 82 checks

This review found 36 issues worth fixing on aspanet.org, 11 of them high impact, across 82 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

Full-page screenshot of aspanet.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aspanet.org at 0.6 s0.6 s
  2. aspanet.org at 1.3 s1.3 s
  3. aspanet.org at 1.9 s1.9 s
  4. aspanet.org at 2.5 s2.5 s
  5. aspanet.org at 3.1 s3.1 s
  6. aspanet.org at 3.8 s3.8 s
  7. aspanet.org at 4.4 s4.4 s
  8. aspanet.org at 5.0 s5.0 s

Speed

6 to fix68
  • Render-blocking requests

    3.6 s

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

  • Reduce unused JavaScript

    900 ms · 315 KiB

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

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    590 ms · 84 KiB

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

  • Use efficient cache lifetimes

    300 ms · 163 KiB

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

  • Google Tag Manager adds 121 ms

    121 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and azure.com and others), adding 477 KiB and 233 ms of main-thread time.

  • Font display

    200 ms

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

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    35 KiB

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

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix79
  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.6 s).

  • Time to Interactive: 7.3 s

    7.3 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 34 ms

    34 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.30 g

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

4 checks passed
  • Page weight: 1.1 MB in 77 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 77 requests on a phone: scripts 722 KiB (17), images 114 KiB (16) and stylesheets 107 KiB (6). That is a lean page.

  • 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

4 to fixGoogle 8794
  • 4 text elements with low contrast

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

  • 2 images without alt text

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

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

  • 5 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

7 to fixGoogle 7761
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. 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 social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://aspanet.org/sitemap.xml, so Google discovers your pages only by following links.

  • 5 links crawlers can't follow

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

  • 12 internal links, 16 external

    The homepage links to 12 pages on aspanet.org and 16 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.aspanet.org/ASPA/ASPA/Default.aspx.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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://aspanet.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.

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

Other pages

3 to fix85
  • 3 pages without a meta description

    https://aspanet.org/ASPA/Membership/Membership.aspx, https://aspanet.org/takeaways and https://aspanet.org/ASPA/ASPA/About-ASPA/Social-Equity-Center/HGF-Home.aspx have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://aspanet.org/ASPA/Membership/Membership.aspx, whose canonical is https://aspanet.org/ASPA/ASPA/Membership/Membership.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://aspanet.org/ASPA/Membership/Membership.aspx, https://aspanet.org/takeaways, https://aspanet.org/ASPA/Make-Connections/Bridge/Bridge-090926.aspx, https://aspanet.org/ASPA/Make-Connections/Bridge/Bridge-081226.aspx and https://aspanet.org/ASPA/ASPA/About-ASPA/Social-Equity-Center/HGF-Home.aspx have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    6 pages of 8 loaded without an error (the rest turned automated requests away).

  • 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 5 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5069
  • 2 broken images

    2 images failed to load on a phone, for example https://idgraph-pixel.stagwellmarketingcloud.io/img?trid=833&page={{PAGE_NAME}}.

  • 7 small tap targets

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

  • 4 third-party cookies

    4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 139 words

    The homepage has only about 139 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Download Path”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 aspanet.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
jQuery
Analytics
Google Analytics

Company

Founded
1939
Headquarters
Washington, D.C.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on aspanet.org, including 11 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