Website review, no card needed
scytale.ai website review
Visit site (opens in a new tab)Reviewed 21 October 202629 issues · 81 checks
This review found 29 issues worth fixing on scytale.ai, 7 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 161 ms |
| May 9, 2026 | 165 ms |
| May 16, 2026 | 168 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 180 ms |
| Jun 13, 2026 | 188 ms |
| Jun 20, 2026 | 188 ms |
| Jun 27, 2026 | 190 ms |
| Jul 4, 2026 | 176 ms |
| Jul 11, 2026 | 176 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 173 ms |
| Aug 1, 2026 | 188 ms |
| Aug 8, 2026 | 193 ms |
| Aug 15, 2026 | 201 ms |
| Aug 22, 2026 | 211 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 221 ms |
| Sep 12, 2026 | 231 ms |
| Sep 19, 2026 | 236 ms |
| Sep 26, 2026 | 260 ms |
| Oct 3, 2026 | 249 ms |
| Oct 10, 2026 | 263 ms |
| Oct 17, 2026 | 254 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
Speed
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,871 HTML elements
The page has 3,871 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (rocketcdn.me, iubenda and ip-api.com), adding 572 KiB and 1.1 s of main-thread time.
Reduce unused JavaScript
930 ms · 211 KiBAbout 211 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 930 ms faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
rocketcdn.me adds 839 ms
839 msrocketcdn.me costs a phone 839 ms of main-thread work and 450 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.
Use efficient cache lifetimes
350 ms · 91 KiB8 files are served with short cache lifetimes, so returning visitors download them again (91 KiB).
Render-blocking requests
350 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
iubenda adds 295 ms
295 msiubenda costs a phone 295 ms of main-thread work and 122 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.
Improve image delivery
150 ms · 86 KiB8 images could be 86 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
Reduce unused CSS
50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 98 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 27 ms
27 msYour server sent the HTML in 27 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Compliance that never clocks out.”.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 8.4 s
8.4 sThe page becomes fully interactive after 8.4 s. Good is under 3.8 s.
Real-user INP: 230 ms
230 msReal visitors wait 230 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 59% slower for real visitors
+59%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 161 ms to 254 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Total Blocking Time: 187 ms
187 msScripts block the page for only 187 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 33.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1,007 KiB in 60 requests
1,007 KiBYour homepage downloads 1,007 KiB in 60 requests on a phone: scripts 507 KiB (32), images 206 KiB (16) and HTML 150 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 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 (147 elements)
All page content should be contained by landmarks: 147 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 109 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“AI for GRC” and “Dashboard”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: sameAs is an empty list”.
18 links with vague text
18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
213 internal links, 22 external
The homepage links to 213 pages on scytale.ai and 22 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “The only AI GRC platform with human experts driving real compliance outcomes, from getting compliant to staying complia…”.
Title: 59 characters
Your title is a healthy 59 characters: “Leading AI GRC Platform for Continuous Compliance | Scytale”.
Canonical URL set
The canonical URL is https://scytale.ai/.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://scytale.ai/sitemap_index.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,269 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://scytale.ai/llms.txt (195 KiB, 518 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a meta description
https://scytale.ai/third-party-risk-management, https://scytale.ai/user-access-reviews, https://scytale.ai/trust-center, https://scytale.ai/audit-management, https://scytale.ai/all-features and https://scytale.ai/agentic-compliance and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://scytale.ai/lp/frost-sullivan-customer-value-leadership-2026, https://scytale.ai/third-party-risk-management, https://scytale.ai/ai-security-questionnaires, https://scytale.ai/continuous-compliance, https://scytale.ai/user-access-reviews and https://scytale.ai/trust-center and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://scytale.ai/lp/frost-sullivan-customer-value-leadership-2026, https://scytale.ai/ai-security-questionnaires, https://scytale.ai/continuous-compliance, https://scytale.ai/integrations and https://scytale.ai/customers/sundaysky-moves-from-reactive-audits-to-continuous-compliance-with-scytale have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to manifest at 'https://581635a6.delivery.rocketcdn.me/site.webmanifest' from origin 'https://scytale.ai' has be…”.
2 checks passed
Tap targets are thumb-sized
15 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 2,049 words of copy
The homepage carries about 2,049 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo” and “Learn more”.
17 calls to action
The homepage has 17 calls to action, for example “Get a demo”, “Book a Demo” and “Learn more”.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks, 2 customer or partner logos, 30 trust badges and “700+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 scytale.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on scytale.ai, including 18 speed issues and 3 SEO issues. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.