ardms.org website review

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

1 image could be 271 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and ContentSquare and others), adding 1.3 MB and 1.1 s of main-thread time.

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

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

Google CDN costs a phone 519 ms of main-thread work and 733 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.

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

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

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

The page has 1,743 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

24 KiB could be saved by minifying JavaScript.

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

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

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

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.

4 KiB could be saved by minifying CSS.

The first text or image appears after 9.5 s on a phone. Good is under 1.8 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 image “a group of healthcare workers smiling”.

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

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

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

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

Your homepage downloads 2.3 MB in 44 requests on a phone: scripts 1.3 MB (18), other files 352 KiB (8) and images 298 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image (90 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 201 pages on ardms.org and 20 external pages.

Your Organization JSON-LD is missing url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/certification-exam-finder and /area-of-practice/general-sonography-and-mfh have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://myportal.inteleos.org/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

inteleos.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

inteleos.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

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.

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

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 899 words of visible text.

ardms.org has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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.

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