adea.org website review

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

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and FontAwesome CDN and others), adding 1.8 MB and 824 ms of main-thread time.

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

YouTube costs a phone 533 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.

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

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

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

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

13 KiB could be saved by minifying CSS.

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

12 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 44.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

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

Your homepage downloads 15.1 MB in 127 requests on a phone: images 11.9 MB (22), scripts 2.3 MB (59) and stylesheets 460 KiB (15). Under 2 MB keeps phones on slow connections fast.

5 images (825 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.

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

1 image is downloaded at several times the size a phone draws it, for example adea-cdf-thumbnail.png at 1,200 px wide, shown at 342 px. Resized copies would save about 120 KiB.

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

aria-hidden="true" must not be present on the document body: 1 element on the page fails this check, rated critical by axe-core.

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 element hidden from screen readers can still receive keyboard focus.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h3, h3 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.

Your title is only 11 characters: “Home | ADEA”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“2026 ADEA CAAPID Virtual Fair”, “New Data!” and “Now Open”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

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

The homepage links to 176 pages on adea.org and 10 external pages.

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.

There is no /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.

Your homepage links to /header-utility-items/adea-connect, which answers with an error. Visitors hit a dead end and search engines drop it.

/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /home all use the title “Home | ADEA”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/header-utility-items/join-renew, /header-utility-items/data-portal, /home/application-services, /home/application-services/become-a-dentist, /home/application-services/become-a-dentist/adea-aadsas-applicants and /home/application-services/become-a-dentist/adea-aadsas-admissions-officers and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/home/application-services/become-a-dental-hygienist/program-finder has 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 158 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

3 errors were logged to the browser console while the page loaded, for example “Loading the image 'https://www.googletagmanager.com/td?id=GTM-NJ9PLN&v=3&t=t&pid=1396717018&gtm=45He6ae1v6611346za200zd…”.

Chrome logged issues while loading the page (“Cookie”).

2 links from your homepage to your own site are broken, for example https://www.adea.org/adea-external/myadea (404).

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

4 links go through two or more redirects, for example https://www.adea.org/home/SignOut/.

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.

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

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

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 505 words of visible text.

DMARC is set to p=none, so mail pretending to be adea.org is still delivered. Reports are on, so moving to quarantine is the next step.

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 5 cookies, 1 of them by other companies (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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.