akc.org website review

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

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

8 third-party services load with your homepage (Gigya, Infolinks and Rubicon Project and others), adding 2.0 MB and 987 ms of main-thread time.

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

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

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

Gigya costs a phone 378 ms of main-thread work and 940 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 3.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Google/Doubleclick Ads costs a phone 117 ms of main-thread work and 331 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.

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

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

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

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.

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

Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use necessary cookies to make our website function. We’d…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.0 MB in 696 requests on a phone: other files 2.1 MB (340), scripts 2.0 MB (64) and HTML 362 KiB (83). Under 2 MB keeps phones on slow connections fast.

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

5 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 5 elements on the page fail this check, rated critical by axe-core.

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

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

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

Your title is only 20 characters: “American Kennel Club”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (BreadcrumbList, CollectionPage, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

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

The homepage links to 87 pages on akc.org and 32 external pages.

/expert-advice and /products-services/magazines have no meta description, so Google writes the search snippet from whatever text it finds.

/products-services/training-programs, /expert-advice/training/common-behavior-issues, /expert-advice/lifestyle/fun-with-your-dog, /expert-advice/lifestyle/did-you-know, /expert-advice/health/grooming and /dog-breeds/pug have no <h1> headline, so visitors and search engines get no clear main topic.

/products-services/training-programs, /sports, /expert-advice/training/common-behavior-issues, /expert-advice/training/dogs-playing-or-fighting, /expert-advice/lifestyle/fun-with-your-dog and /expert-advice/lifestyle/halloween-safety-tips-for-dog-owners and 7 others 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.

/sports, /expert-advice/training/common-behavior-issues, /expert-advice/training/dogs-playing-or-fighting, /expert-advice/lifestyle/did-you-know, /expert-advice/lifestyle/fun-facts-kerry-blue-terrier and /expert-advice/training/effectively-ignore-dogs-unwanted-behavior and 2 others took over 3 s to send their HTML from our server.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

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

1 image is served at too low a resolution for sharp phone screens.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

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

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.

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

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

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

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 2,532 words of visible text.

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 (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 4 cookies, 2 of them by other companies (measured from a US location before any click).

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