msba.org website review

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

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Intercom and Clarity and others), adding 1.1 MB and 641 ms of main-thread time.

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

Cloudflare CDN costs a phone 0 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.

18 KiB could be saved by minifying CSS.

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

13 KiB could be saved by minifying JavaScript.

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

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.

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

Your largest element takes 78.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “2027 Legal Summit Call for Programs is Now Open Submit your…”.

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

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

Scripts block taps and scrolling for 711 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.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 21.3 MB in 179 requests on a phone: images 19.5 MB (109), scripts 1.1 MB (22) and fonts 441 KiB (8). Under 2 MB keeps phones on slow connections fast.

2 images weigh 6.5 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example 20260612-MSBA-Legal-Summit-Annual-Meeting-Franz-991.jpg at 5,504 px wide, shown at 198 px. Resized copies would save about 7.0 MB.

40 images (11.9 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.

3 images further down the page (3.0 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 6.05 g of CO₂e: 725.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

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

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

There are 7 <h1> headlines (“2027 Legal Summit Call for Programs is Now Open”, “For our members. For the profession.” and “Explore the NEW Certificate in Generative AI for …”). One clear main headline is easier for people and search engines.

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 339 pages on msba.org and 21 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://msba.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://msba.org/site/site/content/Members/Legal-Research.aspx, https://msba.org/site/content/Education-and-Events/2027-MSBA-Legal-Summit-Call-for-Programs, https://msba.org/about, https://msba.org/ItemDetail, https://msba.org/site/content/News-and-Publications/Bar-Journal and https://msba.org/site/content/About/Presidents-Corner.aspx and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://msba.org/site/content/Education-and-Events/2027-MSBA-Legal-Summit-Call-for-Programs, whose canonical is https://msba.org/site/site/content/Education-and-Events/2027-MSBA-Legal-Summit-Call-for-Programs.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://msba.org/ItemDetail and https://msba.org/event.aspx have no <h1> headline, so visitors and search engines get no clear main topic.

https://msba.org/ItemDetail 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 17 found) and read each the way a search engine does.

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 “Cannot read properties of null (reading 'getCellByColumnUniqueName')”.

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (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 12 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.