Website review, no card needed

americanmedtech.org logo

americanmedtech.org website review

Visit site (opens in a new tab)Reviewed 20 October 202647 issues · 91 checks

This review found 47 issues worth fixing on americanmedtech.org, 17 of them high impact, across 91 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
3.2 s2.6 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20262.8 s
Jun 6, 20263.0 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
181 ms145 msMay 2Oct 17175 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026149 ms
May 9, 2026151 ms
May 16, 2026153 ms
May 23, 2026150 ms
May 30, 2026153 ms
Jun 6, 2026156 ms
Jun 13, 2026151 ms
Jun 20, 2026154 ms
Jun 27, 2026154 ms
Jul 4, 2026163 ms
Jul 11, 2026174 ms
Jul 18, 2026176 ms
Jul 25, 2026175 ms
Aug 1, 2026171 ms
Aug 8, 2026171 ms
Aug 15, 2026164 ms
Aug 22, 2026164 ms
Aug 29, 2026166 ms
Sep 5, 2026172 ms
Sep 12, 2026176 ms
Sep 19, 2026177 ms
Sep 26, 2026173 ms
Oct 3, 2026172 ms
Oct 10, 2026174 ms
Oct 17, 2026175 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 americanmedtech.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. americanmedtech.org at 0.6 s0.6 s
  2. americanmedtech.org at 1.1 s1.1 s
  3. americanmedtech.org at 1.7 s1.7 s
  4. americanmedtech.org at 2.3 s2.3 s
  5. americanmedtech.org at 2.9 s2.9 s
  6. americanmedtech.org at 3.4 s3.4 s
  7. americanmedtech.org at 4.0 s4.0 s
  8. americanmedtech.org at 4.6 s4.6 s

Speed

14 to fix31
  • Improve image delivery

    1.1 s · 5.7 MB

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

  • Render-blocking requests

    5.0 s

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

  • Reduce unused JavaScript

    1.4 s · 983 KiB

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

  • Mobile performance score: 31

    31/100

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

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.3 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, Freshchat and Hotjar and others), adding 1.7 MB and 2.8 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 401 KiB

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

  • Google Tag Manager adds 798 ms

    798 ms

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

  • Reduce unused CSS

    600 ms · 212 KiB

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

  • 20 long tasks on the main thread

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

  • Freshchat adds 619 ms

    619 ms

    Freshchat costs a phone 619 ms of main-thread work and 762 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.

  • Hotjar adds 513 ms

    513 ms

    Hotjar costs a phone 513 ms of main-thread work and 64 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.

  • Accessibe Accessibility Overlay adds 301 ms

    301 ms

    Accessibe Accessibility Overlay costs a phone 301 ms of main-thread work and 242 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.

  • fw-cdn.com adds 263 ms

    263 ms

    fw-cdn.com costs a phone 263 ms of main-thread work and 88 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.

  • Font display

    100 ms

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

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 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: 13 ms

    13 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.4 s

    4.4 s

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Real-user TTFB: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 13.2 s

    13.2 s

    Your largest element takes 13.2 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: 23.8 s

    23.8 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • 15 images without width and height

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix33
  • Page weight: 9.0 MB in 128 requests

    9.0 MB

    Your homepage downloads 9.0 MB in 128 requests on a phone: images 6.4 MB (37), scripts 1.9 MB (32) and fonts 424 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    567 KiB

    6 images are downloaded at several times the size a phone draws them, for example logo-cecu.png at 9,322 px wide, shown at 144 px. Resized copies would save about 567 KiB.

  • 12 images in older formats

    12 images (892 KiB) 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.

  • 13 images below the first screen load straight away

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

  • About 2.6 g of CO₂ per visit

    2.55 g

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

Accessibility

5 to fixGoogle 9094
  • 42 text elements with low contrast

    42 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 (4 elements)

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

  • Zoom is disabled

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

  • ARIA role should be appropriate for the element (5 elements)

    ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (5 elements)

    Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

6 to fixGoogle 9280
  • 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.

  • Meta description is long (165 characters)

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

  • No XML sitemap

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

  • 16 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 145 internal links, 11 external

    The homepage links to 145 pages on americanmedtech.org and 11 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Allied Health Certification”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “American Medical Technologists (AMT) Home”.

  • robots.txt in place

    robots.txt is in place.

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://americanmedtech.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 (812 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 5 pages without an H1

    https://americanmedtech.org/resource-library, https://americanmedtech.org/blog, https://americanmedtech.org/amt-store, https://americanmedtech.org/shopping-cart and https://americanmedtech.org/state-societies have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

4 to fixGoogle 7383
  • 5 small tap targets

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

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'init')”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • About 573 words of copy

    The homepage carries about 573 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Signup for Alerts”, “Apply” and “Register Now”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and 15 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 americanmedtech.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 Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on americanmedtech.org, including 24 speed issues, 6 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