Website review, no card needed
aicpa.org website review
Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 72 checks
This review found 40 issues worth fixing on aicpa.org, 22 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.5 s |
| May 23, 2026 | 5.4 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 6.4 s |
| Jun 13, 2026 | 7.0 s |
| Jun 20, 2026 | 7.1 s |
| Jun 27, 2026 | 7.2 s |
| Jul 4, 2026 | 7.1 s |
| Jul 11, 2026 | 6.4 s |
| Jul 18, 2026 | 6.4 s |
| Jul 25, 2026 | 6.3 s |
| Aug 1, 2026 | 6.2 s |
| Aug 8, 2026 | 6.2 s |
| Aug 15, 2026 | 6.2 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 6.1 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 5.8 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 5.7 s |
| Oct 3, 2026 | 5.8 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.5 s |
| Oct 24, 2026 | 5.5 s |
| Oct 31, 2026 | 5.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 312 ms |
| May 23, 2026 | 313 ms |
| May 30, 2026 | 326 ms |
| Jun 6, 2026 | 386 ms |
| Jun 13, 2026 | 422 ms |
| Jun 20, 2026 | 438 ms |
| Jun 27, 2026 | 448 ms |
| Jul 4, 2026 | 429 ms |
| Jul 11, 2026 | 415 ms |
| Jul 18, 2026 | 421 ms |
| Jul 25, 2026 | 421 ms |
| Aug 1, 2026 | 420 ms |
| Aug 8, 2026 | 414 ms |
| Aug 15, 2026 | 412 ms |
| Aug 22, 2026 | 406 ms |
| Aug 29, 2026 | 405 ms |
| Sep 5, 2026 | 404 ms |
| Sep 12, 2026 | 404 ms |
| Sep 19, 2026 | 413 ms |
| Sep 26, 2026 | 427 ms |
| Oct 3, 2026 | 438 ms |
| Oct 10, 2026 | 409 ms |
| Oct 17, 2026 | 386 ms |
| Oct 24, 2026 | 360 ms |
| Oct 31, 2026 | 326 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.1 s
Speed
Reduce unused JavaScript
26.3 s · 5.6 MBAbout 5.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 26.3 s faster on a phone.
Render-blocking requests
12.5 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 12.5 s.
Google Tag Manager adds 2.0 s
2.0 sGoogle Tag Manager costs a phone 2.0 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 3.6 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 Tag Manager, Optanon and doublethedonation.com and others), adding 2.8 MB and 2.2 s of main-thread time.
Use efficient cache lifetimes
750 ms · 232 KiB8 files are served with short cache lifetimes, so returning visitors download them again (232 KiB).
Reduce unused CSS
720 ms · 144 KiBAbout 144 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 720 ms faster on a phone.
Minify CSS
450 ms · 65 KiB65 KiB could be saved by minifying CSS.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 453 ms. During a long task the page ignores taps.
Duplicated JavaScript
400 ms · 36 KiB36 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 400 ms faster on a phone.
Optanon adds 90 ms
90 msOptanon costs a phone 90 ms of main-thread work and 300 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
110 KiB10 images could be 110 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need.
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: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 9.7 s
9.7 sReal visitors wait 9.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 19.4 s
19.4 sThe first text or image appears after 19.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 41.4 s
41.4 sYour largest element takes 41.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “It’s time to celebrate CGMA® Week”.
Speed Index: 20.6 s
20.6 sVisually, the page fills in at 20.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 41.4 s
41.4 sThe page becomes fully interactive after 41.4 s. Good is under 3.8 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Real-user INP: 325 ms
325 msReal visitors wait 325 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 312 ms to 326 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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 5.5 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 7.3 MB in 100 requests
7.3 MBYour homepage downloads 7.3 MB in 100 requests on a phone: scripts 4.5 MB (23), other files 2.2 MB (47) and images 344 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (54 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 2.1 g of CO₂ per visit
2.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.07 g of CO₂e: 248.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 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.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 (27 characters)
Your title is only 27 characters: “AICPA & CIMA | AICPA & CIMA”. 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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
4 checks passed
Canonical URL set
The canonical URL is https://www.aicpa-cima.com/.
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.aicpa-cima.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 583 words, but the HTML your server sends has only 1. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.aicpa-cima.com/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.
Opted out of AI training for 1 crawler
robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=223006141&Ver=2&mid=bd34652c-53ee-4793-b7e5-1a801b9aaf42&bo=2&sid=ac0f39e0d92711f18ddccb1eade7b490&vid=ac0f44b0d92711f182dcd1e3cda438c5&vids=1&msclkid=N&pi=918639831&l.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=698620361.1793889982>m=45be6b31h1v9168951674za20ozb92376…”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 583 words of copy
The homepage carries about 583 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Register”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 aicpa.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Founded
- 1887
- Headquarters
- Manhattan
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 aicpa.org, including 22 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.