shrm.org website review

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

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

Optanon costs a phone 4.6 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 3.3 s of main-thread work and 2.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 22.8 s on main-thread work while loading, 16.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Facebook costs a phone 1.3 s of main-thread work and 484 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Adobe Tag Manager costs a phone 1.1 s of main-thread work and 175 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Optanon, Google Tag Manager and Facebook and others), adding 21.2 MB and 11.9 s of main-thread time.

maglr.com costs a phone 605 ms of main-thread work and 16.7 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.

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

6 images could be 240 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

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

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

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

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

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

Your largest element takes 33.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From compliance to culture, talent to transformation, SHRM …”.

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

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

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

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

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

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

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

Your homepage downloads 22.3 MB in 404 requests on a phone: media 14.7 MB (2), scripts 5.4 MB (147) and images 1.5 MB (92). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

The homepage links to 240 pages on shrm.org and 31 external pages.

There is no https://www.shrm.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.shrm.org/home, https://www.shrm.org/front-door, https://www.shrm.org/in/front-door and https://www.shrm.org/mena/front-door declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.shrm.org/front-door, https://www.shrm.org/in/front-door and https://www.shrm.org/mena/front-door all use the title “Welcome to SHRM | The Voice of All Things Work”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.shrm.org/shop, https://www.shrm.org/membership/hr-professional and https://www.shrm.org/membership/global have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shrm.org/front-door, https://www.shrm.org/in/front-door and https://www.shrm.org/mena/front-door use the same meta description. A description written for each page earns more clicks.

https://www.shrm.org/front-door, https://www.shrm.org/in/front-door and https://www.shrm.org/mena/front-door have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getAttribute')”.

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

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 81 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 5 mores (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 26 cookies (measured from a US location before any click).

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