Overall Score
Rol Krysalis is a Spanish-language tabletop RPG character sheet application with a functional dark-fantasy aesthetic, but it's being murdered by SEO negligence, performance bloat, and a complete absence of discoverability—it's basically a beautiful ghost town that nobody can find.
The Roast
This website looks like it was designed by someone who watched a lot of fantasy movies but skipped the entire 'how to build a website' tutorial. Sure, the login form is aesthetically pleasing with its moody brown-and-gold color scheme—very 'Dark Ages nobility'—but SEO score of 0? That's not a strategy, that's a cry for help. You've got zero meta description, duplicate H1 tags (why?!), and a 4.4-second LCP that'll have users bouncing faster than a critical fail on a d20. It's like showing up to a fantasy convention in an amazing costume that nobody knows is you.
🎯 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
SEO
Trust Signals
Copy & Messaging
Conversion
Performance
Mobile
Design & UX
Accessibility
SEO
The SEO is catastrophically non-existent—zero meta description, duplicate H1s, no structured data, and the crawl data shows only 86 words of indexable content, meaning Google literally has nothing to work with.
Issues Found
- Missing meta description (canonical SEO disaster)—Google will auto-generate a terrible snippet or none at all
- Duplicate H1 tags ('ROL KRYSALIS' x2) violate heading best practices and confuse search engines about page topic
- Only 86 words of indexable text visible to crawlers—this is a bare-minimum login page masquerading as the full application
Recommendations
-
Add meta description (50-160 chars) high
Write: 'Rol Krysalis: Gestor de fichas de rol en línea. Crea personajes, lanza dados, coordina combates y gestiona tus campañas D&D 5e.' Target Spanish keywords.
-
Fix heading structure high
Use single H1 for page title, remove duplicate, and structure as H1 (Title) → H2 (Login section) or equivalent, ensuring each heading is unique.
-
Add structured data (Schema.org) medium
Implement WebApplication or SoftwareApplication schema markup with name, description, image, and URL to help Google understand this is a playable app.
Trust Signals
Trust signals are virtually non-existent—no testimonials, user counts, reviews, security badges, privacy policy, or any proof this isn't a scam site harvesting emails. The version number ('v1.4.6.0') is the only indicator of maturity, and it's barely visible.
Issues Found
- Zero security indicators—no HTTPS badge, privacy policy, or terms of service visible (though HTTPS is implied by the domain)
- No social proof whatsoever—no user testimonials, community size, Discord/community links, or credibility markers
- Version number is buried in tiny text; there's no 'About' section, developer info, or history to build trust
Recommendations
-
Add security and privacy links high
Include footer links to 'Política de privacidad', 'Términos de servicio', and 'Seguridad' (even if they're simple one-pagers initially) to build legal trust.
-
Add social proof section high
Below or beside the login form, add stats like '2,400+ jugadores activos' or 'Creado por comunidad de D&D España' with Discord/social links.
-
Feature developer/creator info medium
Add a small 'About' section or footer credit: 'Mantenido por [creator/team]' with links to GitHub, Twitter, or portfolio to establish credibility.
Copy & Messaging
The copy is minimalist to the point of being cryptic—'Entra con tu cuenta para jugar' is functional but totally uninspiring, and there's literally nothing explaining what this product is or why anyone should sign up.
Issues Found
- 'Entra con tu cuenta para jugar' (Login to play) gives zero context about what you're logging into or what makes it worth your time
- No value proposition or unique selling points visible—this could be any RPG platform, any game site, any authentication portal
- 'Crear cuenta' (Create account) link is passive and underdeveloped, missing persuasive copy about the benefits of joining
Recommendations
-
Write a compelling headline high
Replace or supplement 'ROL KRYSALIS' with a tagline like 'El gestor de fichas de rol más poderoso' or 'Crónicas de Krysalis: Tu mesa de juego en línea' to communicate value instantly.
-
Add subheading with benefits high
Below the title, add 1-2 sentences: 'Gestiona tus personajes, coordina combates y controla tu campaña todo en un lugar' or similar to show what users get.
-
Enhance 'Crear cuenta' CTA medium
Change text from passive 'Crear cuenta' to active, benefit-driven copy like 'Comienza tu aventura gratis' with a slightly bolder visual treatment.
Conversion
The form layout is clean and focused, but conversion is hobbled by zero value communication, no trust signals, and a completely underdeveloped signup flow—you're asking people to join a mystery club with no explanation of membership benefits.
Issues Found
- Primary CTA ('Entrar') lacks context—users don't know what they're entering or what to expect after login
- No secondary or tertiary conversion paths visible—'Crear cuenta' is understyled and de-emphasized relative to login
- 'Partida' dropdown (campaign selection) is unclear in purpose and suggests complexity before onboarding
Recommendations
-
Clarify the primary CTA high
Add supporting copy above the form: 'Ya tienes cuenta? Accede ahora' and add expectation-setting like '(sin anuncios, privado, sincronizado en tiempo real)'.
-
Emphasize signup for new users high
Style 'Crear cuenta' as a secondary button (lighter background, similar prominence to 'Entrar') and move it above the login form or make it more prominent.
-
Move 'Partida' dropdown to post-login medium
Remove or hide the campaign selector on login form; show it after authentication to reduce cognitive load for new users.
Performance
Mobile Performance: 73/100 sounds okay until you realize SEO is 0/100 and Best Practices is 0/100—the page loads eventually but wastes resources with unminified CSS/JS and a 4.4-second LCP that's borderline unacceptable for a login form.
Issues Found
- LCP (Largest Contentful Paint) is 4.409s—should be under 2.5s; this is likely Konva.js library or unoptimized images causing sluggish renders
- CSS and JavaScript are not minified, wasting bandwidth and download time (explicit audit recommendation)
- Konva library (canvas drawing) is loaded via CDN without async/defer flags, blocking page rendering unnecessarily
Recommendations
-
Minify CSS and JavaScript high
Run all assets through minifiers (Terser for JS, CSSNano for CSS) and defer non-critical JS to reduce initial load payload.
-
Optimize Konva.js loading high
Load Konva asynchronously with async/defer attribute, or lazy-load it only on the post-login page (not needed for login form).
-
Remove unused CSS medium
Use PurgeCSS or similar tooling to strip unused styles; audit recommends this explicitly—likely 20-40% bloat lurking.
Mobile
Mobile design is reasonably responsive with the form centering and scaling appropriately for 375px viewport, but form input touch targets appear to be borderline small, and there's no mobile-specific navigation or hamburger menu visible.
Issues Found
- Form input height appears borderline for touch interaction (looks ~44-48px from screenshot); should be minimum 48-56px for comfortable mobile tapping
- Email/password fields may have auto-zoom issues on iOS if font size is below 16px (cannot confirm without inspecting, but common pitfall)
- No indication of mobile menu or navigation—if there's header content above the fold, it's not adapted for small screens
Recommendations
-
Increase input touch targets high
Ensure all form inputs and buttons are minimum 48-56px height with adequate padding (32px horizontal) to meet mobile usability standards.
-
Set font size to 16px+ for inputs medium
Use 16px+ font size on email/password inputs to prevent iOS auto-zoom and ensure readability on small screens.
-
Test and optimize mobile spacing medium
Audit vertical spacing between form fields on mobile; ensure 16-24px gaps for comfortable thumb navigation.
Design & UX
The dark-fantasy aesthetic is cohesive and thematic with nice form styling and centered layout, but the design is purely functional with zero personality, visual hierarchy, or any indication of what happens after login—it's all form, no substance.
Issues Found
- Duplicate H1 tags ('ROL KRYSALIS' appears twice) creates structural confusion and wastes heading hierarchy
- Zero visual feedback or onboarding—users have no idea what the app does or why they should care beyond 'play a game'
- Form labels are tiny and low-contrast against the dark background, making them harder to read than necessary
Recommendations
-
Consolidate heading hierarchy high
Remove the duplicate H1 and use a single H1 for the title, then use H2 for 'Login' and H3 for form sections to create proper semantic structure.
-
Add value proposition copy above the form high
Include 2-3 sentences explaining what Rol Krysalis is, who should use it, and what makes it special—mystery is not a marketing strategy.
-
Improve form label contrast medium
Use a lighter color or add background contrast for labels ('Partida', 'Email', 'Contraseña') to meet WCAG AA standards.
Accessibility
Accessibility is surprisingly decent with 11 ARIA attributes and proper input labels (14 inputs, 0 missing labels), but there's no skip link, and form inputs likely have insufficient color contrast against the dark background.
Issues Found
- No skip-to-main-content link—users with screen readers must navigate through header/nav before reaching the login form
- Form input placeholder text ('tu-correo@gmail.com', '•••••••') appears to be low-contrast against dark brown/black backgrounds, failing WCAG AA
- No visible focus indicators on form fields (not confirmed from screenshots but likely given the dark aesthetic)
Recommendations
-
Add skip-to-main link high
Insert a hidden skip link at the top: '<a href="#main" class="skip-link">Saltar al contenido principal</a>' and ensure it's keyboard-accessible.
-
Increase input contrast high
Make form labels and placeholder text lighter (e.g., #ccc or #ddd) so they contrast at least 4.5:1 against dark inputs per WCAG AA.
-
Add visible focus indicators medium
Apply outline or border styles to form inputs on :focus with sufficient contrast (e.g., gold or light color matching your accent theme).
Think you can beat 43/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.