Website review, no card needed

tessian.com logo

tessian.com website review

Visit site (opens in a new tab)Reviewed 29 October 202618 issues · 76 checks

This review found 18 issues worth fixing on tessian.com, 5 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.2 s3.6 sMay 9Oct 244.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20264.0 s
Jun 27, 20264.1 s
Jul 4, 20264.2 s
Jul 11, 20264.3 s
Jul 18, 20264.4 s
Jul 25, 20264.5 s
Aug 1, 20264.7 s
Aug 8, 20264.9 s
Aug 15, 20264.9 s
Aug 22, 20264.9 s
Aug 29, 20264.8 s
Sep 5, 20264.9 s
Sep 12, 20264.9 s
Sep 19, 20265.0 s
Sep 26, 20265.0 s
Oct 3, 20264.9 s
Oct 10, 20264.9 s
Oct 17, 20264.7 s
Oct 24, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
186 ms161 msMay 9Oct 24169 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026183 ms
May 16, 2026183 ms
May 23, 2026179 ms
May 30, 2026178 ms
Jun 6, 2026173 ms
Jun 13, 2026171 ms
Jun 20, 2026172 ms
Jun 27, 2026171 ms
Jul 4, 2026172 ms
Jul 11, 2026169 ms
Jul 18, 2026168 ms
Jul 25, 2026166 ms
Aug 1, 2026164 ms
Aug 8, 2026166 ms
Aug 15, 2026168 ms
Aug 22, 2026171 ms
Aug 29, 2026173 ms
Sep 5, 2026178 ms
Sep 12, 2026176 ms
Sep 19, 2026175 ms
Sep 26, 2026176 ms
Oct 3, 2026175 ms
Oct 10, 2026179 ms
Oct 17, 2026169 ms
Oct 24, 2026169 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of tessian.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tessian.com at 0.4 s0.4 s
  2. tessian.com at 0.8 s0.8 s
  3. tessian.com at 1.1 s1.1 s
  4. tessian.com at 1.5 s1.5 s
  5. tessian.com at 1.9 s1.9 s
  6. tessian.com at 2.3 s2.3 s
  7. tessian.com at 2.6 s2.6 s
  8. tessian.com at 3.0 s3.0 s

Speed

1 to fix98
  • Render-blocking requests

    500 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Reduce unused JavaScript

    195 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google/Doubleclick Ads, Marketo and geoip-js.com and others), adding 38 KiB and 27 ms of main-thread time.

  • Legacy JavaScript

    10 KiB

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

  • Use efficient cache lifetimes

    5 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 checks passed
  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 115 ms of it running JavaScript. That is comfortably low.

  • Server response: 182 ms

    182 ms

    Your server sent the HTML in 182 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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-user LCP: 4.6 s

    4.6 s

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

  • Real-user FCP: 4.5 s

    4.5 s

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

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Time to Interactive: 4.5 s

    4.5 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

7 checks passed
  • Real-user INP: 166 ms

    166 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Digital Communications Governance Intelligently capture, re…”.

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 26 ms

    26 ms

    Scripts block the page for only 26 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 2 images far larger than shown

    113 KiB

    2 images are downloaded at several times the size a phone draws them, for example AdaptiveEmailSecurity_RealTimeCoaching.png.webp at 2,078 px wide, shown at 358 px. Resized copies would save about 113 KiB.

  • About 0.1 g of CO₂ per visit

    0.14 g

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

3 checks passed
  • Page weight: 521 KiB in 22 requests

    521 KiB

    Your homepage downloads 521 KiB in 22 requests on a phone: scripts 312 KiB (12), images 165 KiB (4) and HTML 23 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9197
  • Links must have discernible text (4 elements)

    Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

  • 68 tap targets too small

    68 tap targets are too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 124 internal links, 17 external

    The homepage links to 124 pages on tessian.com and 17 external pages.

8 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “TESSIAN IS NOW Proofpoint Core Email Protection API and Adaptive Email DLP Proofpoint and Tessian, a leader in the use …”.

  • One H1 headline

    Your main headline reads: “Proofpoint Core Email Protection API and Adaptive Email DLP”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Tessian is Now Proofpoint | Proofpoint US”.

  • Canonical URL set

    The canonical URL is https://www.proofpoint.com/us/tessian-is-now-proofpoint.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.proofpoint.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.proofpoint.com/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,012 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.proofpoint.com/us/products/email-security-and-protection/secure-email-relay, whose canonical is https://www.proofpoint.com/us/products/secure-email-relay. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 202 words

    The homepage has only about 202 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “How to buy”, “Request a demo” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

  • 7 cookies set on arrival

    7

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

  • No consent tool detected

    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.

  • 10 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tessian.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
Tailwind CSS
Hosting
Imperva

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on tessian.com, including 8 speed issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25