securityscorecard.com website review

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

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

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

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

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (VWO, Google Tag Manager and Cookiebot and others), adding 755 KiB and 752 ms of main-thread time.

VWO costs a phone 558 ms of main-thread work and 272 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.

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

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

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

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

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.

Your largest element takes 27.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalize content and ads, to provide s…”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 96.7 MB in 149 requests on a phone: media 88.7 MB (29), images 7.0 MB (64) and scripts 848 KiB (27). Under 2 MB keeps phones on slow connections fast.

TITANAI_Platform_Oct26_v1-SQUARE.gif weighs 4.4 MB. On a phone connection a single image that size takes seconds.

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

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

2 images are downloaded at several times the size a phone draws them, for example SSC_Web_FooterCTA-AVD.png at 1,460 px wide, shown at 342 px. Resized copies would save about 294 KiB.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

The homepage links to 233 pages on securityscorecard.com and 28 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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /resources/press/securityscorecard-unveils-titan-ai-a-new-era-of-threat-informed-third-party-risk-management, whose canonical is /company/press/securityscorecard-unveils-titan-ai-a-new-era-of-threat-informed-third-party-risk-management. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/request-a-demo has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://securityscorecard.com/aviation/ (404).

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

securityscorecard.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Social proof on the homepage: 71 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 1,303 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies, 1 of them by other companies (measured from a US location before any click).

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