Overall Score
FlowControl is a Russian productivity app with a solid foundation but buried under terrible SEO and crippled by a Cloudflare security wall that's actively blocking crawlers and killing search visibility. The design is clean and the mobile experience is decent, but nobody's going to find this thing on Google.
The Roast
FlowControl looks like a respectable productivity app decided to hide behind a Cloudflare challenge gate—which is hilarious because your hero section is on /ru/today and screams 'PLEASE CRAWL ME' while simultaneously waving off every search engine with 'prove you're human.' It's like wearing a neon sign that says 'DON'T INDEX THIS' while hoping to rank organically. The 0 SEO score isn't a bug, it's a feature—a feature of self-sabotage. At least the UI doesn't hurt to look at, which is more than we can say for your discoverability strategy.
🎯 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
Accessibility
Conversion
Copy & Messaging
Design & UX
Performance
Mobile
SEO
SEO is effectively non-existent: the page sits behind a Cloudflare challenge wall (active security verification required to access), killing all crawler visibility, and even if crawlers could pass, there are zero structured headings, no internal links, and no schema markup—it's an SEO funeral.
Issues Found
- Cloudflare Managed Challenge blocking automatic crawler access—requires human interaction to bypass, making the page invisible to Googlebot, Bingbot, and most SEO crawlers
- Zero <h1> or semantic heading structure; content is a mix of unstyled text nodes and React components with no SEO scaffold
- No internal links, no breadcrumbs, no JSON-LD schema (no ProductSchema, no LocalBusinessSchema, no FAQ schema), no Open Graph image (OG image is missing)
Recommendations
-
Disable Cloudflare challenge for crawlers high
Configure Cloudflare to whitelist major search engine bots (Googlebot, Bingbot, Yandex) or disable the challenge entirely on this page; alternatively use a robots.txt exception or allow-list.
-
Add proper semantic HTML structure high
Wrap hero section in <h1> ('FlowControl: Система исполнения для фрилансеров'), add <h2> for form section, use <article> or <section> landmarks with proper hierarchy.
-
Implement ProductSchema and LocalBusinessSchema medium
Add JSON-LD schema markup in <head> describing the product, features, pricing (if applicable), and company info to enable rich snippets.
Trust Signals
Trust signals are virtually absent: no testimonials, no user count or social proof, no security badges (despite mentioning Supabase Auth), no privacy policy or terms link visible, and the 'chatgpt.site' domain is a massive red flag—screams 'demo/test' rather than a legitimate SaaS product.
Issues Found
- Domain 'stealtva.chatgpt.site' is a ChatGPT-generated subdomain (or test domain)—users will question if this is a real product or a sketch/prototype
- No security or privacy indicators (no SSL badge, no GDPR/data protection mention, no visible Privacy Policy link in footer—if footer exists, it's off-screen)
- Supabase Auth is mentioned in small gray text ('Аккаунт защищен Supabase Auth') but buried and unexplained—users don't know if this is good or if they should care
Recommendations
-
Move to a legitimate domain high
Host on flowcontrol.app or similar branded domain—the .chatgpt.site domain kills credibility instantly with privacy-conscious users.
-
Add visible trust markers high
Include a footer section (or sticky footer) with links to Privacy Policy, Terms of Service, and a 'Security' callout highlighting Supabase encryption; add SSL certificate indicator.
-
Surface user/testimonial proof medium
If product is live, add a small user counter ('Trusted by 500+ freelancers') or a single testimonial quote in a sidebar; if pre-launch, note 'Beta: Early Access Available'.
Accessibility
Accessibility is barely present: only 1 ARIA attribute total, no skip link, minimal landmarks (just one <main>), and form fields likely have poor label associations—the page is approaching 'legally risky' territory for WCAG compliance.
Issues Found
- No skip-to-content link (users on keyboard/screen readers must tab through logo and nav before reaching the form)
- Form inputs lack visible <label> associations or aria-label attributes—screen readers will announce bare text above inputs, not linked form labels
- Only 1 ARIA attribute for entire page suggests form fields are not marked as required, inputs lack aria-describedby for error messages or helper text (Supabase Auth note)
Recommendations
-
Add skip-to-main-content link high
Insert a hidden-but-focusable link at page top: '<a href="#main" class="skip-link">Skip to login form</a>' visible on focus.
-
Properly associate form labels high
Wrap each input in a <label> element or use aria-label/aria-labelledby; ensure password field is marked as type='password' and required inputs have aria-required='true'.
-
Add ARIA landmarks and structure medium
Mark the login form area as <section aria-label="Login Form"> and sign-up area as <section aria-label="Create Account">; use heading hierarchy (<h1>, <h2>).
Conversion
Form is present but lacks micro-persuasion: CTA button ('Войти') is good size and color (green, high contrast), but there's no trust signaling, no loading states, no error boundaries, and the dual-path funnel (login vs. create account vs. Google) could confuse users about the fastest path forward.
Issues Found
- Call-to-action text is generic 'Войти' (Login)—no urgency or benefit (e.g., 'Start Free Trial' or 'Open Dashboard' would be stronger)
- Three competing CTAs (Login button, Create Account, Google Login) without clear visual hierarchy; users pause to decide which path is 'right'
- No form-level validation or success states shown; users don't know if submission succeeded until they're redirected or see an error
Recommendations
-
Strengthen primary CTA copy medium
Change 'Войти' to 'Начать работу' (Start Working) or 'Войти в FlowControl' to add context and urgency.
-
Clarify the login vs. sign-up flow medium
Make 'Создать аккаунт' secondary visually (smaller, outline style) so login is clearly the primary path; or combine into a single 'Don't have an account? Sign up' link below the form.
-
Add loading and error states medium
Show a spinner on button during submission (aria-busy='true'), and display inline error messages (aria-describedby) if credentials are invalid.
Copy & Messaging
Value prop is clear ('Finish day with concrete result') and the tone is appropriately direct for Russian B2B, but the supporting copy is vague and the hero headline doesn't explain *what* the product does—just the aspiration.
Issues Found
- Hero headline 'Заканчивайте день с конкретным результатом' (Finish day with concrete result) is motivational but tells you nothing about what FlowControl is or does
- Supporting line 'Собирите реалистичный план...' (Build a realistic plan...) is generic and could describe any to-do app
- Dashboard labels on the right ('Главная цель', 'Текущий блок', 'Ожидаемый результат') are descriptive but not persuasive—no benefit statements
Recommendations
-
Lead with a differentiator, not aspiration high
Change headline to something like 'День спланирован. Работа сделана.' (Day planned. Work done.) or 'Система, которая работает' (A system that works)—show the mechanism, not the dream.
-
Add a one-line benefit beneath the headline high
Insert a 10-word max subheading explaining who it's for and why: 'Для фрилансеров: планируйте часы, достигайте целей' (For freelancers: plan hours, hit targets).
-
Replace generic labels with benefit callouts medium
Change 'Текущий блок' to 'Сосредоточенная работа (120 мин)' or add user benefits underneath each dashboard section.
Design & UX
Clean, modern split-screen layout with reasonable typography and whitespace, but the beige background feels dated and the dark dashboard preview on the right lacks visual hierarchy or engagement; form inputs are nicely styled but there's zero visual feedback on interaction states.
Issues Found
- Flat beige background (looks more '2018 Scandinavian minimalism' than 'modern SaaS') with no visual interest or micro-interactions
- Right-side preview image (dashboard) is too dark and high-contrast against the pale left—creates visual imbalance that reads as 'left side is important, right side is whatever'
- No clear visual progression between form sections; password field looks identical to email field (no affordance suggesting it masks input)
Recommendations
-
Introduce subtle gradient or texture low
Replace flat beige with a soft gradient (beige to soft warm gray) or add a subtle pattern to create depth and reduce the 'static' feel.
-
Improve dashboard preview contrast medium
Lighten the dark preview panel or add a subtle glow/border to make it feel integrated rather than bolted-on.
-
Add input field affordances medium
Style password field differently (e.g., icon indicator, subtle background change, or 'show/hide' toggle) to signal it's password-protected.
Performance
PageSpeed shows a solid 95 performance score on mobile, but that's deceptive—LCP is 2.5s (acceptable but not great for a login page), and the real drag is unused JavaScript clogging the payload; the Cloudflare challenge script alone is adding overhead.
Issues Found
- Reduce unused JavaScript flagged by Lighthouse—you're importing '/cached/assets/index-BFwQ3zCu.js' with full React/Next hydration for a static login form
- Cloudflare challenge script + main.js inject adds latency before user can interact; iframe-based challenge is blocking time-to-interactive
- LCP at 2.551s is acceptable but slow for a login page—users expect <1.5s; likely due to JS parsing and React hydration before DOM is interactive
Recommendations
-
Code-split the login form high
Extract the login form to a minimal no-JS HTML page or use partial hydration so users can interact with the form while dashboard JS loads in the background.
-
Defer non-critical JavaScript medium
Use <script defer> for analytics and Cloudflare challenge scripts; load dashboard preview JS only on interaction (e.g., tab switch).
-
Optimize Cloudflare challenge medium
If challenge is necessary, explore Cloudflare Turnstile (faster and more user-friendly) instead of the legacy challenge-platform script.
Mobile
Mobile layout is responsive and stacks cleanly (form on left, preview hidden on mobile is fine), but touch targets on form buttons are adequate but not generous, and there's no mobile-specific optimization like autofocus on email field or one-tap Google sign-in.
Issues Found
- Form buttons are tall enough (54px+) but lack visible focus/active states for touch—users don't get clear feedback when tapping
- Right-side dashboard preview is entirely hidden on mobile (good for space) but creates a jarring context switch on desktop; inconsistent experience
- Email field shows placeholder 'demo@flowcontrol.app' which is confusing—users may think they need to use that exact address rather than their own email
Recommendations
-
Enhance touch feedback medium
Add :active and :focus-visible states to all buttons with color shift or subtle shadow (e.g., button active state: slightly darker green, slightly inset).
-
Improve placeholder clarity low
Change placeholder from 'demo@flowcontrol.app' to 'yourname@example.com' or remove it entirely; add a <label> instead so users understand they enter their own email.
-
Enable mobile-friendly Google Sign-In low
Ensure Google button is full-width on mobile and uses native 'Sign in with Google' button (not custom text) for better mobile UX.
Think you can beat 52/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.