Website review, no card needed

aiim.org logo

aiim.org website review

Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 77 checks

This review found 31 issues worth fixing on aiim.org, 7 of them high impact, across 77 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
3.0 s2.5 sApr 25Oct 102.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.7 s
May 2, 20262.7 s
May 9, 20262.7 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
240 ms87 msApr 25Oct 10151 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026107 ms
May 2, 2026106 ms
May 9, 2026105 ms
May 16, 2026111 ms
May 23, 2026113 ms
May 30, 2026120 ms
Jun 6, 2026128 ms
Jun 13, 2026130 ms
Jun 20, 2026132 ms
Jun 27, 2026137 ms
Jul 4, 2026136 ms
Jul 11, 2026144 ms
Jul 18, 2026137 ms
Jul 25, 2026131 ms
Aug 1, 2026130 ms
Aug 8, 2026128 ms
Aug 15, 2026138 ms
Aug 22, 2026140 ms
Aug 29, 2026139 ms
Sep 5, 2026222 ms
Sep 12, 2026209 ms
Sep 19, 2026203 ms
Sep 26, 2026206 ms
Oct 3, 2026141 ms
Oct 10, 2026151 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 aiim.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix51
  • Render-blocking requests

    3.1 s

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

  • Reduce unused JavaScript

    1.8 s · 342 KiB

    About 342 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Mobile performance score: 51

    51/100

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

  • Use efficient cache lifetimes

    700 ms · 218 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and usemessages.com and others), adding 1.3 MB and 743 ms of main-thread time.

  • Google Tag Manager adds 628 ms

    628 ms

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

  • Improve image delivery

    401 KiB

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

  • Reduce unused CSS

    300 ms · 24 KiB

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

  • 10 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 51. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 13.3 s

    13.3 s

    Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 13.5 s

    13.5 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Tap response (INP) got 37% slower for real visitors

    +37%

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

  • Total Blocking Time: 347 ms

    347 ms

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

  • 14 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

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

    1.9 s

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

  • 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: 1.4 s

    1.4 s

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

  • Real-user TTFB: 583 ms

    583 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix68
  • Page weight: 2.2 MB in 93 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 93 requests on a phone: images 968 KiB (29), scripts 948 KiB (22) and fonts 220 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    72 KiB

    2 images are downloaded at several times the size a phone draws them, for example Virtual Training Workshops (LinkedIn Post) (1)-1.png at 1,200 px wide, shown at 339 px. Resized copies would save about 72 KiB.

  • 5 images below the first screen load straight away

    5 images further down the page (326 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (85 KiB) is 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.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

Accessibility

4 to fixGoogle 9395
  • 50 text elements with low contrast

    50 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 (15 elements)

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9286
  • No structured data

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

  • Meta description is long (195 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • 51 internal links, 31 external

    The homepage links to 51 pages on aiim.org and 31 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Ready to Transform Your Career?”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “AIIM - The Association for Intelligent Information Management”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

Other pages

100
  • 15 internal pages checked

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

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

  • 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 9687
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “sizeHeader is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 1,030 words of copy

    The homepage carries about 1,030 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: “Join AIIM+ Pro Now”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “AIIM Swag Shop”, “Join AIIM” and “Subscribe to AIIM's Blog”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

  • 19 other companies contacted

    Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 aiim.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
HubSpot CMS
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

Company

Founded
1943
Headquarters
Silver Spring

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on aiim.org, including 15 speed issues, 4 SEO issues and 2 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