kdp.org website review

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

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

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

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

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

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

8 third-party services load with your homepage (cloudfront.net, bettybot.ai and Google Tag Manager and others), adding 4.6 MB and 2.3 s of main-thread time.

cloudfront.net costs a phone 828 ms of main-thread work and 2.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.

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

bettybot.ai costs a phone 737 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.

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

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

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

theassociationpartner.net costs a phone 20 ms of main-thread work and 584 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.

17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

9 KiB could be saved by minifying CSS.

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 see the first content after 3.5 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 36.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “National Professional Association and Honor Society for Edu…”.

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

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

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

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

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

11 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-31, real Chrome visitors' tap response (inp) went from 106 ms to 122 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.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 29.1 MB in 228 requests on a phone: images 24.5 MB (76), scripts 2.8 MB (71) and fonts 1.1 MB (7). Under 2 MB keeps phones on slow connections fast.

6 images weigh 15.3 MB together. On a phone connection a single image that size takes seconds.

20 images are downloaded at several times the size a phone draws them, for example Candid_Trans_Since_24_copy.jpg at 5,000 px wide, shown at 158 px. Resized copies would save about 15.2 MB.

18 images (17.3 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.

11 images further down the page (15.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

9 elements hidden from screen readers can still receive keyboard focus.

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

8 frames have no title, so screen-reader users cannot tell what they contain.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 21 characters: “Home - Kappa Delta Pi”. 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 9 <h1> headlines (“National Professional Association and Honor Socie…”, “Member Spotlight: Ms. Carolena Gursky” and “Member Spotlight: Ms. Candice Mundy”). One clear main headline is easier for people and search engines.

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

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

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

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

The homepage links to 151 pages on kdp.org and 18 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 https://www.kdp.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.

https://www.kdp.org/HigherLogic/Security/SAML/localSAMLLoginService.aspx, https://www.kdp.org/about/bylaws and https://www.kdp.org/about/articles-of-incorporation have no <title>, so Google invents the link text in results.

https://www.kdp.org/HigherLogic/Security/SAML/localSAMLLoginService.aspx, https://www.kdp.org/about, https://www.kdp.org/about/kdp-laureates, https://www.kdp.org/about/legacy-members, https://www.kdp.org/about/united-nations-representatives and https://www.kdp.org/about/kdac-advisory-council and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kdp.org/HigherLogic/Security/SAML/localSAMLLoginService.aspx, https://www.kdp.org/about/bylaws and https://www.kdp.org/about/articles-of-incorporation have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.kdp.org/home.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: SimpleLightbox is not defined”.

Chrome logged issues while loading the page (“Content security policy”).

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: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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