casepoint.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and rudderlabs.com and others), adding 913 KiB and 1.2 s of main-thread time.

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

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

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

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

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

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 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Website Dropdown Banner AI Investigator Agent Desktop”.

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

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

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

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

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

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

4 images further down the page (451 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example -Report-_Modernizing_Defense_Agencies_Feature_Image.svg at 1,200 px wide, shown at 342 px. Resized copies would save about 89 KiB.

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

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “AI-Powered Platform for Government, Legal, and Compliance | Casepoint”.

Your meta description is 253 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 3 (line 3 )”.

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

The homepage links to 137 pages on casepoint.com and 9 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 /solutions/ediscovery-investigations, whose canonical is /products/casepoint-investigator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 58 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=97265956&tm=gtm002&Ver=2&mid=7b1dbe56-1fb7-4397-b468-e36e187bfa49&bo=1&sid=fa3fc6e0d44c11f1846d21d71697795f&vid=fa4009b0d44c11f1bbc7913e749d2497&vids=1&msclkid=N&pi=91.

6 errors were logged to the browser console while the page loaded, for example “This version of the RudderStack JavaScript SDK is deprecated and no longer maintained. While your events are still bein…”.

1 link go through two or more redirects, for example https://platform.casepoint.com/.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

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 1,361 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 Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 23 cookies (measured from a US location before any click).

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