Overall Score
Tawasol AI is a visually polished Arabic AI support assistant with slick design work and decent mobile responsiveness, but it's sabotaging itself with a 9.8s LCP, zero SEO optimization, missing metadata, and a crawler that sees ZERO content—making this gorgeous page essentially invisible to search engines and screen readers.
The Roast
Tawasol AI built a Ferrari with no engine. The design is legitimately beautiful—smooth RTL Arabic layout, smart use of purple/blue branding, clean typography, and responsive mobile work that actually doesn't suck. But then they forgot to tell Google the website exists (literally zero internal/external links detected), left the LCP at a glacial 9.8 seconds, gave up on meta descriptions, and let unused JavaScript bloat the bundle like they're charging per kilobyte. It's the equivalent of having a gorgeous storefront with no door—everyone can see it's pretty, but nobody can actually get in or find 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
Accessibility
Performance
Conversion
Trust Signals
Mobile
Copy & Messaging
Design & UX
SEO
This is a SEO graveyard: missing meta description, zero internal/external links detected, zero ARIA attributes, no structured data, and the crawler extracts 0 words of content—meaning the site is functionally invisible to search engines despite being a public website selling B2B AI services.
Issues Found
- Missing meta description—Google will autogenerate a low-quality snippet, clobbering CTR
- Zero internal links and zero external links detected by crawler—site has no link graph, no navigation signals, and external sites can't reference it
- Crawler reports 0 words extracted—likely JavaScript-heavy rendering without server-side content; Googlebot may not wait 9.8s for render
Recommendations
-
Add meta description (155-160 chars) high
Write: "Tawasol AI: Customer support chatbot for Arabic-speaking teams. Instant responses via chat, email, and chat widgets—24/7 support in Arabic."
-
Implement internal linking structure high
Add contextual links from hero to features, features to pricing/products, and use footer nav to link to main sections; helps Googlebot crawl and distributes authority.
-
Add JSON-LD schema markup high
Implement Organization, SoftwareApplication, and LocalBusiness schema to tell Google who you are, what you sell, and your location.
Accessibility
The site is nearly inaccessible: 0 ARIA attributes, no skip link, zero images with alt text, and a JavaScript-heavy rendering that screen readers likely can't parse until after the 9.8s load completes. This violates WCAG AA standards across the board.
Issues Found
- Zero ARIA landmarks (no navigation, main, contentinfo roles)—screen reader users have no semantic navigation
- No skip link to main content—keyboard users forced to tab through nav before reaching hero
- All images (hero mockup, feature icons, testimonial pictures) detected as missing alt text—blind users see nothing
Recommendations
-
Add ARIA landmarks and semantic HTML high
Wrap nav in <nav>, hero in <header>, features in <main>, footer in <footer>; add role="banner", role="contentinfo" where needed.
-
Add skip-to-main-content link high
Add a visually hidden <a href="#main-content">Skip to main</a> link at top of page; set #main-content on the features section.
-
Alt-text all images and icons high
Hero mockup: "Tawasol AI dashboard showing customer conversations in Arabic"; feature icons: "Inbox icon", "Chat icon", etc.
Performance
The 9.8s LCP is a deal-breaker that overshadows decent CLS (0.034) and TBT (0ms). The PageSpeed score of 63 mobile indicates substantial unused JavaScript—likely a React/Vue app without code-splitting or the CSS-in-JS is blocking render.
Issues Found
- LCP (9.863s) is 4x the Google "good" threshold (<2.5s); page feels frozen on first load
- "Reduce unused JavaScript" warning indicates bloat; likely framework overhead without tree-shaking or lazy code-splitting
- Mobile PageSpeed 63 is below the fold—SEO penalty likely; CWV are at risk for ranking drop
Recommendations
-
Prioritize LCP reduction via code-splitting high
Split bundle by route; load only critical CSS/JS for above-fold hero; defer features/FAQ/testimonials until after LCP.
-
Audit and remove unused JavaScript high
Run webpack-bundle-analyzer or source-map-explorer to find dead code; consider preact or Alpine.js if framework is bloated.
-
Implement server-side rendering (SSR) or static generation high
Pre-render hero + nav on server so HTML arrives with content; Googlebot won't wait 9.8s for JavaScript to render.
Conversion
Conversion funnel is scattered: primary CTA (Try Tawasol) is buried mid-page, secondary CTA (Book a Call) appears only at bottom, and there's no email capture or clear lead magnet—missing the opportunity to build intent early and nurture via email.
Issues Found
- No visible CTA button in hero section—users have to scroll to find action (Try Tawasol button is mid-page below copy)
- Secondary CTA ("كلمنا على واتساب" / Message on WhatsApp) is vague; WhatsApp is good for engagement but not for lead capture/qualification
- No lead magnet (PDF guide, free trial form, demo video) to capture email—page is all awareness, zero email list growth
Recommendations
-
Add hero CTA button above fold high
Place a prominent "Start Free Trial" or "Get Demo" button directly under the hero headline (not mid-page).
-
Build email capture flow high
Add a modal or inline form offering "Free Arabic AI Setup Guide" in exchange for email; nurture via automation.
-
Create clear CTA hierarchy medium
Primary: Try Tawasol (above fold); Secondary: Book Demo (mid-page); Tertiary: WhatsApp (footer)—don't mix them.
Trust Signals
The page shows some credibility markers (Meta Tech Provider badge, segmented feature list, FAQ section) but lacks critical social proof: no customer testimonials visible, no case studies, no logo carousel, no security badges, and no numerical proof ("10k+ companies" type claims) that would build confidence in a B2B AI tool.
Issues Found
- No customer testimonials or case studies visible in captured sections—no proof that real users trust this product
- Meta partnership badge is shown but not amplified; could be bigger/more prominent to borrow Meta's credibility
- No security/compliance badges (SOC 2, GDPR, ISO) visible—important for enterprise B2B sales
Recommendations
-
Add customer testimonials section high
Feature 3-4 rotating testimonials with company name, title, photo, and short quote; use star rating or NPS score if available.
-
Expand security/trust section medium
Add badges for SOC 2 Type II, GDPR compliance, data encryption, and uptime guarantee; place near footer.
-
Add social proof metrics medium
Feature stats: "Trusted by 500+ Arabic-speaking companies", "10M+ conversations processed", "99.9% uptime" to anchor credibility.
Mobile
Mobile layout is responsive and mostly well-structured with readable typography and appropriate touch targets, but the 9.8s LCP on mobile is even more painful than desktop, and the page scrolls forever (~1568px footer region suggests long scroll).
Issues Found
- LCP is still 9.8s on mobile (or worse)—users on 4G will see blank screen for 10+ seconds; mobile-first indexing penalizes this heavily
- Mobile PageSpeed score of 63 is below threshold; CWV mobile performance is degraded vs. desktop
- Long page height (~4679px desktop, proportionally similar mobile)—excessive scrolling; mobile users bounce faster
Recommendations
-
Optimize mobile LCP priority high
Defer all non-critical images/features on mobile; load only hero text + primary CTA; lazy-load features list below fold.
-
Condense mobile hero height medium
Reduce hero to max 60vh on mobile (not taller); move features/testimonials to second section; reduce scroll friction.
-
Test mobile performance on 4G throttle medium
Use Lighthouse throttle = "Slow 4G"; aim for <3s LCP; if unachievable with current bundle, SSR is non-negotiable.
Copy & Messaging
Headlines are punchy and benefit-driven ("Support customers in their language"), and the Arabic copy is well-written with clear pain points addressed. But CTAs are buried under competing messages, and there's no clear single narrative thread—the page tries to sell too many features at once instead of anchoring on one core promise.
Issues Found
- Primary CTA ("جرب Tawasol" / Try Tawasol) appears only mid-page; no above-fold CTA button visible in hero
- Value proposition is diluted across 4 feature sections + products + FAQ—unclear what the #1 use case is
- Copy tone mixes product features with AI hype without grounding in specific business outcomes
Recommendations
-
Lead with one clear headline value prop high
Hero headline should be "Support customers in Arabic instantly with AI"—strip the secondary messaging; move features below.
-
Add visible above-fold CTA button high
Include a prominent "Start Free Trial" or "Book Demo" button in the hero section alongside the existing messaging.
-
Consolidate feature messaging medium
Reduce from 4 feature blocks to 3, and attach specific business outcomes ("Reduce support costs by 40%") to each.
Design & UX
The layout is genuinely well-executed with solid visual hierarchy, thoughtful spacing, and a modern SaaS-style design language that works for the Arabic market. However, the 4679px desktop height suggests some content density issues and the ultra-long LCP undermines the entire visual experience by making the page feel frozen on load.
Issues Found
- Excessively long page load time (9.8s LCP) destroys perceived performance despite nice visuals
- Page is ~4679px tall on desktop—likely over-scrolling and poor content prioritization above the fold
- Hero section relies heavily on imagery/UI mockups but crawler detects zero images with alt text—accessibility and SEO black hole
Recommendations
-
Audit and lazy-load below-the-fold sections high
Split content into viewport chunks; defer non-critical sections (features, testimonials, FAQ) until after LCP fires.
-
Optimize hero image delivery high
Compress and serve hero mockup as WebP with srcset; consider SVG for UI illustrations on the right side of hero.
-
Reduce visual debt above the fold medium
Move secondary features and FAQ lower; consolidate hero + primary value prop into first 800px of content.
Think you can beat 47/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.