jssa.org website review

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

About 899 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 1.9 MB and 842 ms of main-thread time.

Your mobile performance score is 65 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

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

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

YouTube costs a phone 330 ms of main-thread work and 997 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.

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

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

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

38 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 12 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.

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 page becomes fully interactive after 18.6 s. Good is under 3.8 s.

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “JSSA is a trusted nonprofit community health and social wel…”.

The first text or image appears after 3.9 s on a phone. Good is under 1.8 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 284 ms in total while the page loads. Good is under 200 ms.

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

15 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-24, real Chrome visitors' tap response (inp) went from 98 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Claims-Conference-logo.jpg weighs 599 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.3 MB in 86 requests on a phone: scripts 1.8 MB (26), images 1.1 MB (28) and fonts 172 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

The homepage links to 91 pages on jssa.org and 15 external pages.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211060132&tm=gtm002&Ver=2&mid=0b50d71c-2cd0-4ea4-bcf0-2ce9da6040bd&bo=1&sid=b0c50480d2b811f19c717b177b3b006d&vid=b0c51f40d2b811f1ad0c4f5b29de9d6d&vids=1&msclkid=N&pi=9.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.jssa.org' has been blocked by …”.

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.

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

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