sisense.com website review

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

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

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

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

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

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

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

Your homepage downloads 2.0 MB in 45 requests on a phone: media 1.3 MB (1), other files 291 KiB (7) and fonts 205 KiB (5). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

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

No image is downloaded at more than three times the size it is drawn on a phone.

All 22 images in the HTML carry an alt attribute.

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

Your meta description is 144 characters: “Sisense delivers AI-powered embedded analytics to unlock insights and convert data into revenue with pro-code, low-code…”.

Your main headline reads: “The embedded AI analytics platform”.

Your title is a healthy 48 characters: “AI-Powered Embedded Analytics Platform - Sisense”.

The canonical URL is https://www.sisense.com/.

Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

robots.txt is in place and points crawlers to your sitemap.

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

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

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

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

The site publishes /llms.txt (4 KiB, 14 links), a plain-text guide to the site for AI tools.

14 pages of 15 loaded without an error (the rest turned automated requests away).

No page we checked hands its ranking to a different URL.

All 14 pages that loaded have a meta description.

Every page we checked has its own title.

Each page we checked has a main headline.

None of the pages we checked carries a noindex tag.

All 14 pages that loaded have a <title>.

The page declares a mobile viewport.

The homepage is served over HTTPS (sisense.com).

The certificate from Google Trust Services · WE1 verifies for sisense.com and is valid for another 41 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

A Content-Security-Policy is set, the main browser-side defence against injected scripts.

Strict-Transport-Security is set, so browsers always use https.

http://sisense.com redirects to the secure version.

The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

All 59 links checked from your homepage (40 internal, 19 external) answered without errors.

sisense.com was registered in Oct 2004 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

CAA records allow only pki.goog, ssl.com, amazon.com and amazonaws.com to issue certificates for sisense.com, so a mis-issued certificate from anyone else is refused.

sisense.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

sisense.com is registered until Oct 2027.

On a phone, the first screen shows a clear next step: “Book a demo”.

The homepage has 7 calls to action, for example “Free trial”, “Demo” and “Book a demo”.

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

Social proof on the homepage: 7 testimonial or review blocks, 8 customer or partner logos and 3 trust badges.

Analytics detected: Google Tag Manager.

DMARC tells receivers to reject mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 a mx include:_spf.google.com include:mktomail.com include:spf.salesforce.com include:mail-spf.devrev.ai ip4:82.8…”.

A DKIM key is published (selector “google”, “k2” and “s1”), so receivers can verify mail really came from you.

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).