securityhealth.org website review

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

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

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

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

About 424 KiB of JavaScript is downloaded but never used on this page.

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

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

6 third-party services load with your homepage (Google Tag Manager, Amplitude Mobile Analytics and Google CDN and others), adding 626 KiB and 431 ms of main-thread time.

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

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

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

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

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 11.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Senior couple embracing”. Most of its time is resource load delay (5.5 s).

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

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

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

9 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 111 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

fc1bff0d71794d32a61a206004a5bb67.png weighs 614 KiB. On a phone connection a single image that size takes seconds.

4 images (779 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.

1 image is downloaded at several times the size a phone draws it, for example fc1bff0d71794d32a61a206004a5bb67.png at 704 px wide, shown at 200 px. Resized copies would save about 168 KiB.

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

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

Some list items are not inside a list.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

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

There are 2 <h1> headlines (“” and “Whatever your plans, there's a plan for you”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 89 pages on securityhealth.org and 9 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.securityhealth.org/employers, https://www.securityhealth.org/brokers, https://www.securityhealth.org/tpa-partners-portal-landing-page, https://www.securityhealth.org/members/document-library, https://www.securityhealth.org/brokers/products-and-services and https://www.securityhealth.org/brokers/document-library and 3 others took over 3 s to send their HTML from our server.

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

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

Large scripts ship without source maps.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Amplitude, 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 8 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.