Overall Score
KAST is a visually striking crypto fintech site with a dark, modern aesthetic and solid UX foundation, but it's bleeding performance (59 mobile perf score) and missing critical SEO fundamentals—all while asking users to trust it with their money.
The Roast
KAST looks absolutely gorgeous—like it was designed by someone who's never heard of Core Web Vitals. You've got 50 unoptimized images, obfuscated JavaScript that would make a security auditor weep, and a mobile performance score that makes dialup internet look snappy. It's the financial equivalent of showing up to a bank meeting in a Gucci suit with a dead phone battery. Stunning? Yes. Trustworthy at scale? Ask your server.
🎯 Start Here
Google PageSpeed Insights
(Real metrics from Google)These scores come directly from Google's PageSpeed API. The AI scores above evaluate broader aspects like copy, trust signals, and conversion.
Core Web Vitals
Performance
SEO
Mobile
Trust Signals
Conversion
Accessibility
Design & UX
Copy & Messaging
Performance
A mobile PageSpeed score of 59 is unacceptable for a fintech app—LCP of 2.8s, TTFB of 1.2s, and 215ms INP signal a bloated, unoptimized site that's alienating users before they even see your value prop.
Issues Found
- Largest Contentful Paint (LCP) of 2.8s violates Google's 'good' threshold (<2.5s); hero image or initial content is likely unoptimized or not lazy-loaded
- Time to First Byte (TTFB) of 1.2s suggests server-side bottleneck (slow API, poor CDN strategy, or unoptimized backend); this is killing perceived page speed
- 50 images with zero alt text imply zero image optimization; missing WebP conversion, responsive sizing, and lazy-loading; bloated CSS (unused selectors) and JavaScript (likely from tracking, analytics, or heavy frameworks)
Recommendations
-
Implement aggressive image optimization and lazy-loading high
Convert all images to WebP, add srcset for responsive sizes, use native lazy-loading, and consider a CDN like Cloudflare or Fastly to serve images from edge locations.
-
Fix TTFB via server and caching optimization high
Enable HTTP/2, implement server-side caching, optimize database queries, and use a global CDN to serve HTML; target TTFB <600ms.
-
Audit and tree-shake JavaScript and CSS high
Identify unused CSS and JavaScript (Webpack/Rollup analysis), remove the obfuscation overhead, defer non-critical scripts, and consider moving to a lighter framework if current one is bloated.
SEO
SEO score of 0 on mobile PageSpeed Insights is a disaster—schema.org markup is solid, but the site is crushed by performance and there's zero evidence of keyword targeting, content depth, or structured data for financial services.
Issues Found
- PageSpeed SEO score: 0/100 on mobile—Core Web Vitals failures (LCP 2.8s, TTFB 1.2s) will destroy organic ranking potential; Google's algorithm penalizes slow pages hard
- No visible content depth for target keywords (e.g., 'stablecoin card', 'crypto debit card', 'global money app')—meta descriptions and headings are generic; h1/h2/h3 structure exists but doesn't target high-intent queries
- Obfuscated JavaScript and minified CSS make on-page content harder for crawlers to parse; the heavy reliance on client-side rendering may delay indexation of key features
Recommendations
-
De-obfuscate critical JavaScript and reduce bundle size high
Remove the encoded JavaScript snippet (the _0x199a3a / _0x263f obfuscation), audit for unnecessary code, and aim for TTFB <800ms to unlock SEO gains.
-
Create content clusters around target keywords high
Develop dedicated landing pages or sections for high-intent queries ('best crypto debit card', 'stablecoin spending app', 'global remittance card') with supporting blog content.
-
Expand schema markup for financial products medium
Add schema.org types for FinancialProduct, Card, and BankAccount to help Google understand offerings; include pricing, features, and reviews in structured data.
Mobile
Mobile layout stacks cleanly and nav is hamburger-friendly, but touch targets are hard to assess, and the reliance on large imagery makes mobile load times abysmal—your mobile-first narrative doesn't match the mobile-last performance reality.
Issues Found
- Mobile PageSpeed (59) is significantly worse than desktop, suggesting unoptimized images and unminified code aren't being addressed for smaller screens; viewport meta tag may be present but images aren't responsive
- Hero text on mobile is readable but the phone mockup (showing app) is still a large image asset; no mobile-specific content reduction or progressive disclosure visible
- Touch target sizes for nav, CTA buttons ('GET KAST'), and footer links cannot be fully assessed from screenshots, but spacing looks adequate; form inputs (7 total) size is unclear
Recommendations
-
Optimize images for mobile-first rendering high
Serve smaller image sizes on mobile, use srcset with breakpoints, and consider mobile-specific imagery (e.g., portrait app mockups instead of landscape).
-
Test touch target sizes across devices medium
Ensure all clickable elements (buttons, nav links, form inputs) are at least 44×44px; use Chrome DevTools device emulation to verify.
-
Implement mobile-specific navigation and content layout medium
Consider sticky nav or side drawer for menu; collapse feature sections (STORE, EARN, MOVE, SPEND) into tabs or accordions to reduce mobile scroll depth.
Trust Signals
Stats are strong ('170+ countries', '150M merchants', '7% APY'), but they're buried in a metrics bar and lack third-party validation—no press logos, security badges, regulatory mentions, or customer testimonials to anchor credibility for a financial product.
Issues Found
- Claims like '150M merchants' and 'Up to 7% APY' are impressive but unverified—no source citations, press releases, or third-party validation visible; for fintech, this feels risky
- No visible security indicators: no SOC 2 badge, no 'FDIC insured' messaging, no compliance certifications (in footer text mentions 'licensed partners' but it's buried in tiny font and hard to find)
- Social proof missing from landing: no customer testimonials, case studies, or user reviews; only stats and flashy mockups—nothing human-facing to reduce psychological friction
Recommendations
-
Add third-party trust badges and compliance messaging high
Include visible SOC 2 / ISO 27001 badges, partner bank logos, and regulatory status ('Licensed & Regulated' or 'Partner with [Bank Name]') in hero or dedicated trust section.
-
Create a social proof section with testimonials or case studies high
Add 3–5 short customer testimonials (with name, photo, role) or a press section with news logos (TechCrunch, Forbes, etc.) to anchor credibility.
-
Source and cite financial claims medium
Add footnotes or links for '150M merchants', 'Up to 7% APY', and other bold claims; reference Visa/Mastercard network or yield calculations to prove legitimacy.
Conversion
CTAs are present and visible ('GET KAST' button), but they're generic, under-scoped, and buried in an above-the-fold section that's more flash than funnel—no clear path from landing to sign-up or download.
Issues Found
- 'GET KAST' button in nav is static and lacks urgency; no contextual CTAs (e.g., 'Download iOS', 'Start Free Account', 'Get Founder Card') to guide user intent
- Form elements (7 inputs) are mentioned but not visible in screenshots; unclear if there's an email signup, contact form, or waitlist conversion mechanism on the landing page
- Social proof and conversion catalysts are missing from hero: no user count, funding badge, app store rating, or press logos to reduce friction for first-time visitors
Recommendations
-
Create context-aware, action-specific CTAs high
Replace generic 'GET KAST' with tiered CTAs: 'Download App' (iOS/Android badges), 'Get Founder Card' (premium tier), 'Explore Features' (for on-page users).
-
Add trust signals above the fold high
Include app store badges with rating (e.g., '4.8★ on App Store'), user count ('500K+ users'), or funding announcement ('$80M Series A') to reduce friction.
-
Create a multi-step funnel with micro-conversions medium
Add a secondary CTA for email signup or waitlist; use progressive profiling (ask 1–2 questions per step) to qualify leads before full form submission.
Accessibility
122 ARIA attributes suggest effort, but the number alone is a red flag—over-reliance on ARIA often masks missing semantic HTML; missing skip links and the dark theme with light text may have contrast issues for some users.
Issues Found
- No skip-to-content link identified; users with keyboard navigation will have to tab through entire nav before reaching main content
- 50 images with zero alt text = zero accessibility for screen reader users; every image (app mockups, product cards, background images) is invisible to assistive tech
- Dark background with light text on images (e.g., hero section, 'ONE ACCOUNT FOR EVERY MOVE') may fail WCAG AA contrast requirements; no mention of color-contrast testing
Recommendations
-
Add skip navigation link and audit ARIA usage high
Implement a visible-on-focus skip link; audit all ARIA labels to ensure they're semantic (not redundant); prefer native HTML elements (buttons, landmarks) over div+ARIA where possible.
-
Write descriptive alt text for all 50 images high
Each image needs concise, purpose-driven alt text (e.g., 'KAST mobile app showing $9,269 balance and earn/send/scan options'); test with screen readers.
-
Validate color contrast and test with assistive tech medium
Run text overlaid on images through WCAG contrast checkers (WebAIM, aXe); aim for AA compliance (4.5:1 for body text); test with NVDA/JAWS.
Design & UX
The dark theme is cohesive and modern with sharp typography hierarchy, but the design relies heavily on visual spectacle (animated cards, gradient overlays) that's driving performance into the ground—you're creating a beautiful car while dragging an anchor.
Issues Found
- Excessive reliance on high-resolution imagery without optimization (50 images, zero alt text); hero sections use full-bleed background images that bloat load time
- Layout hierarchy is strong on desktop but mobile cramming (see hero section stacking) makes the primary value prop harder to scan on first view
- Interactive card elements and hover states add visual delight but likely contribute to INP issues (215ms is rough)
Recommendations
-
Lazy-load and compress all images aggressively high
Use modern formats (WebP), implement responsive images with srcset, and lazy-load below-fold content to reduce LCP from 2.8s to <1.8s.
-
Simplify animation and interaction patterns high
Audit CSS animations and JavaScript interactions causing the 215ms INP; replace JS-heavy card transitions with CSS-only or web animations where possible.
-
Create a true mobile-first layout version medium
Current mobile hero text is large but unforgiving; consider progressive disclosure (collapse less critical features on mobile) to reduce scroll depth.
Copy & Messaging
The tagline 'It's a wild world. Keep it stable' is clever and memorable, and the feature copy is clear and benefit-driven, but CTAs are oddly soft and the value prop could punch harder for skeptical first-time visitors.
Issues Found
- 'GET KAST' button appears in nav but lacks urgency or a secondary explanation—novice users won't immediately know if this downloads an app or opens a web wallet
- Hero subheader ('The financial platform to store, earn, move, and spend stablecoins') is accurate but generic; doesn't differentiate from Coinbase, Kraken, or other platforms
- Feature descriptions (STORE, EARN, MOVE, SPEND) are scannable but lack social proof anchors ('Join 500K+' or 'Trusted by X') to reinforce credibility alongside messaging
Recommendations
-
Rewrite hero CTA with clarity and urgency high
Change 'GET KAST' to 'Download App Free' or 'Start Your Account' to remove ambiguity and add micro-commitment language.
-
Add trust-layer messaging to hero and feature sections medium
Include user count, funding amount ($80M Series A!), or security badges ('SOC 2 certified', 'Regulated') to build confidence alongside benefit messaging.
-
Strengthen value prop differentiation medium
Highlight 1–2 unique advantages (e.g., '150M merchants globally' is already strong; lead with 'Spend crypto like fiat' vs. generic 'store/earn/move').
Think you can beat 60/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.