aapc.com website review

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

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

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

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

8 third-party services load with your homepage (Google CDN, Hubspot and Intercom and others), adding 4.5 MB and 1.4 s of main-thread time.

Hubspot costs a phone 340 ms of main-thread work and 2.6 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.

Google CDN costs a phone 437 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.

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

Intercom costs a phone 241 ms of main-thread work and 296 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.

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

1 image could be 43 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 39 KiB of CSS is downloaded but never applied on this page.

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

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Your largest element takes 32.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “50% Off + FREE Unlimited Exam”.

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

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

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

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

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

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

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

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

Your homepage downloads 6.0 MB in 123 requests on a phone: images 3.1 MB (32), scripts 2.2 MB (60) and other files 425 KiB (20). Under 2 MB keeps phones on slow connections fast.

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

3 images (2.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.

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

6 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 166 pages on aapc.com and 15 external pages.

https://www.aapc.com/resources/t/medical-coding and https://www.aapc.com/resources/t/coding all use the title “Medical Coding Resources Help for Healthcare Professionals - AAPC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.aapc.com/resources/t/medical-coding and https://www.aapc.com/resources/t/coding use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.aapc.com/resources/t/coding, whose canonical is https://www.aapc.com/resources/t/medical-coding. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.aapc.com/certifications/cpc, https://www.aapc.com/certifications/cpb, https://www.aapc.com/certifications/cpma, https://www.aapc.com/certifications/cppm, https://www.aapc.com/certifications/cpco and https://www.aapc.com/resources/t/medical-coding and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.aapc.com/resources/t/medical-coding, https://www.aapc.com/resources/t/medical-billing, https://www.aapc.com/resources/t/medical-auditing, https://www.aapc.com/resources/t/healthcare-compliance, https://www.aapc.com/resources/t/practice-management and https://www.aapc.com/resources/t/coding have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=26024652&tm=gtm002&Ver=2&mid=2e6f164d-08e7-4b5d-805b-cf6a811c681c&bo=2&sid=9d38ab80c5cf11f1ba5fb764aacbaa3b&vid=9d38dcd0c5cf11f1891eb139a46c2be2&vids=1&msclkid=N&pi=91.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: “Over 300,000 Members”. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 9 fields (5 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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