cofense.com website review

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

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

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

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 740 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Unpkg and Hubspot and others), adding 1.1 MB and 1.8 s of main-thread time.

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

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

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

3 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 46.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI Built for Phishing Stops Entire Campaigns Automatically …”.

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

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

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

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

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

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

Your homepage downloads 14.0 MB in 106 requests on a phone: images 7.6 MB (32), other files 4.7 MB (30) and scripts 1.5 MB (34). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example metric-header.webp at 2,380 px wide, shown at 350 px. Resized copies would save about 1.6 MB.

1 image further down the page (1.8 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

There are 2 <h1> headlines (“AI Built for Phishing” and “See What AI Built for Phishing Can Do”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

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

The homepage links to 70 pages on cofense.com and 5 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 /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.

/beyond-human-risk-measuring-secure-behavior-with-an-ai-driven-platform has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 26 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=187125267&tm=gtm002&Ver=2&mid=f35ad1e2-c85a-4d98-98fc-2ba0f29f4019&bo=1&sid=a1544d70d89d11f1b74f7d8460ed7534&vid=a1546ca0d89d11f186aebfb5acb3fbc5&vids=1&msclkid=N&gtm_.

5 of 12 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 “Error initializing homeHeroSlider: TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of t…”.

http://cofense.com does not redirect to https, so some visitors land on the insecure version.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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

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

cofense.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The homepage carries about 561 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, Hotjar and HubSpot 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 16 cookies (measured from a US location before any click).

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