Website review, no card needed

ahipmedicaretraining.com logo

ahipmedicaretraining.com website review

Visit site (opens in a new tab)Reviewed 12 October 202641 issues · 80 checks

This review found 41 issues worth fixing on ahipmedicaretraining.com, 19 of them high impact, across 80 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.0 s1.7 sApr 18Oct 31.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.9 s
Apr 25, 20261.9 s
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
167 ms122 msApr 18Oct 3146 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026139 ms
Apr 25, 2026128 ms
May 2, 2026135 ms
May 9, 2026128 ms
May 16, 2026136 ms
May 23, 2026145 ms
May 30, 2026137 ms
Jun 6, 2026137 ms
Jun 13, 2026138 ms
Jun 20, 2026127 ms
Jun 27, 2026128 ms
Jul 4, 2026128 ms
Jul 11, 2026127 ms
Aug 1, 2026129 ms
Aug 8, 2026141 ms
Aug 15, 2026147 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026159 ms
Sep 12, 2026155 ms
Sep 19, 2026154 ms
Sep 26, 2026151 ms
Oct 3, 2026146 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 ahipmedicaretraining.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix29
  • Improve image delivery

    49.6 s · 9.6 MB

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

  • Reduce unused JavaScript

    38.7 s · 7.6 MB

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

  • Use efficient cache lifetimes

    21.7 s · 4.3 MB

    18 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).

  • Render-blocking requests

    4.8 s

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

  • Mobile performance score: 29

    29/100

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

  • Legacy JavaScript

    900 ms · 219 KiB

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

  • Reduce unused CSS

    900 ms · 161 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.2 MB and 813 ms of main-thread time.

  • Google Tag Manager adds 570 ms

    570 ms

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

  • 12 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • Font display

    150 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 54 but mobile only 29. 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.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 102.4 s

    102.4 s

    Your largest element takes 102.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AHIP’s one-stop program meets CMS requirements and provides…”.

  • Speed Index: 21.6 s

    21.6 s

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

  • Time to Interactive: 103.9 s

    103.9 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Total Blocking Time: 658 ms

    658 ms

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

  • Real-user CLS: 0.22

    0.22

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

  • Cumulative Layout Shift: 0.212

    0.212

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

  • 3 images without width and height

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

4 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 131 ms

    131 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 718 ms

    718 ms

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

Images and page weight

4 to fix25
  • Page weight: 19.1 MB in 73 requests

    19.1 MB

    Your homepage downloads 19.1 MB in 73 requests on a phone: images 9.6 MB (12), scripts 9.0 MB (31) and fonts 288 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    AHIP-MedicareTraining-01 fade.png weighs 9.4 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    9.2 MB

    2 images are downloaded at several times the size a phone draws them, for example AHIP-MedicareTraining-01 fade.png at 3,917 px wide, shown at 271 px. Resized copies would save about 9.2 MB.

  • 2 images in older formats

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

  • About 5.4 g of CO₂ per visit

    5.42 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9495
  • Positive tabindex

    4 elements have a tabindex above 0, which scrambles the keyboard order.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 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

7 to fixGoogle 9164
  • No meta description

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

  • Title is short (5 characters)

    Your title is only 5 characters: “Login”. 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 canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.ahipmedicaretraining.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ahipmedicaretraining.com/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 15 internal links, 6 external

    The homepage links to 15 pages on ahipmedicaretraining.com and 6 external pages.

1 checks passed
  • One H1 headline

    Your main headline reads: “Login”.

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (411 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix76
  • 1 page without a title

    https://www.ahipmedicaretraining.com/page/view.php has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.ahipmedicaretraining.com/page/view.php has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 internal pages checked

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

4 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 13 small tap targets

    13 of 18 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 “Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 374 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: “Skip Contact Us”.

  • 1 call to action

    The homepage has 1 call to action, for example “Skip Contact Us”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 7 trackers load before any consent

    7

    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 (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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: 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 ahipmedicaretraining.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on ahipmedicaretraining.com, including 20 speed issues, 7 SEO issues and 1 conversion gap. 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