Average

Score Report

www.liveagent.sk

Scanned on October 7, 2026

Unknown
Splide
AmazonS3
Last scanned: October 7, 2026
AI verdict

Your site performs well overall, but needs refinement in key areas. Priority: add meta descriptions to pages for better search visibility. Strength: your security standards are excellent.

Action plan

Action plan by impact and effort

Every problem found, sorted by how much fixing it helps and how much work the fix takes. Start with the quick wins.

How we rank →

Quick wins

4

High impact, little work. Do these first.

Bigger projects

6

High impact, but the fix needs planning.

+1 more

Small fixes

18

Lower impact, quick to do.

+13 more

Later

28

Lower impact and more work. Plan them once the rest is done.

+23 more

Performance

Weight: 25% · 11 passed · 5 warnings · 1 failed · 2 SPA (verify manually)

What we found: 285 KB wasted on unused code!

Why it matters: Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.

Note: This check uses heuristic detection and may produce false positives. Manual verification recommended.

How to fix: You're loading 285 KB of code that isn't used on this page. 1) Audit plugins and remove unused ones, 2) Use code-splitting for page-specific JS, 3) Run PurgeCSS on your stylesheets.
Evidence:PSI-lab· Confidence: low

What we found: 2.0 MB, 105 requests (optimal: <1.5 MB, <50 req)

Why it matters: A 3 MB page takes 6+ seconds on 3G mobile. Most e-commerce traffic is mobile — heavy pages lose customers on poor connections.

How to fix: Reduce page weight: compress images to WebP (saves 30-50%), enable text compression (gzip/brotli), lazy load below-fold images, remove unused CSS/JS.
Evidence:PSI-lab· Confidence: high
Request quote for speed audit

What we found: 1014 KB — over the 600 KB budget, but below the 1270 KB median of the award-winning shops we benchmarked

Why it matters: Measured on a first load with no interaction, so scripts gated behind cookie consent don't count against you here. The 600 KB bar is best practice, not the cohort average: the shops we benchmarked have a median of 1 270 KB, and the best of them (a category winner that won on mobile) ships 410 KB.

How to fix: Split the bundle so a product page doesn't load checkout and account code. Defer third-party scripts until interaction. Drop unused plugin bundles — on most shops these outweigh your own code.
Evidence:PSI-lab1014 KB JavaScript· Confidence: high

What we found: 105 requests — over the budget of 80, but at or below the median of the award-winning shops we benchmarked (140)

Why it matters: The 80-request bar is best practice; the benchmarked cohort median is 140 and the best shop manages 37. Being under the median is not the same as being fast.

How to fix: Bundle CSS/JS that always loads together, serve icons as a sprite or font rather than individual files, and lazy-load below-fold images so they aren't requested on load.
Evidence:PSI-lab105 requests· Confidence: high

Why it matters: Preconnect saves 100-500ms per third-party origin by establishing connections early. Preload starts downloading critical resources before the browser discovers them in CSS/JS.

How to fix: Add resource hints: <link rel='preconnect' href='https://fonts.googleapis.com'> for third-party origins, <link rel='preload' as='image' href='hero.webp'> for critical resources.
Evidence:HTML-heuristic· Confidence: high
Request quote for speed audit

What we found: Custom fonts detected without preload hints

Why it matters: Fonts are discovered late in the render pipeline (after CSS is parsed). Preloading tells the browser to download them immediately, reducing Flash of Invisible Text (FOIT) by 200-500ms.

How to fix: Preload your primary font: <link rel='preload' href='/fonts/main.woff2' as='font' type='font/woff2' crossorigin>. For Google Fonts: preconnect to fonts.gstatic.com.
Evidence:HTML-heuristic· Confidence: high
Request quote for speed audit

6 issues found in Performance. Room for improvement.

Your store doesn't qualify for the Zulien Score Badge yet. Score 80+ to earn it!

📧 Re-scan reminders

We'll email you monthly when it's time to re-scan and track your improvements.

🚀 Improve your score

Our PrestaShop modules can fix most of these issues automatically.

Free 15-min consultation · No commitment

Share & Export

Ready to improve your score?

Fix it yourself

Browse our modules to fix these issues in 2 clicks.

Browse Zulien Modules

Let us fix it for you

Describe your goal and we'll send a quote within 48h — no call needed.

Get a written quote

Reply within 48h · No sales call

This is an automated heuristic estimate, not a professional audit. Findings reflect publicly observable signals at scan time and may include false positives.Learn about our methodologyReport inaccuracyRemove this report
Full e-commerce audit — 50+ checks across 7 categories
78/100
Grade C
www.liveagent.sk
Audit date: October 7, 2026
Online report: https://score.zulien.sk/r/liveagent.sk
Generated · score.zulien.sk · by Zulien

Executive summary

10
Failures
46
Warnings
72
OK
138
Checks total

Scores by category

CategoryScoreWeightFailuresWarningsOK
Performance91/10025%1511
SEO85/10020%1417
Security84/10015%089
Mobile62/10010%274
AI Readiness71/10010%21412
Legal & Compliance70/10010%147
Vulnerability90/10010%129
Accessibility / EAA41/10010%223

Critical findings

Unused Code (CSS + JS)· Performance
Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.
Meta Description· SEO
Without a meta description, Google auto-generates one — often poorly. A custom description gives you control over the SERP snippet and improves click-through.
Viewport Configuration· Mobile
Without the viewport tag, mobile browsers render at 980px width and zoom out — making text unreadable and buttons untappable. Google uses mobile-first indexing, so this directly kills rankings.
Form Input Labels (WCAG 3.3.2)· Mobile
The European Accessibility Act applies from 28 June 2025. Shops above 10 employees or €2M turnover must meet WCAG 2.1 AA — missing labels are among the most commonly actionable failures.
Organization Schema + Entity Linking· AI Readiness
Organization schema is the foundation of your AI identity. Without it, AI assistants can't confidently attribute information to your brand, verify your legitimacy, or show your Knowledge Panel.
Canonical Tag for AI Deduplication· AI Readiness
Without a canonical tag, AI models may index multiple versions of the same page (with/without trailing slash, with parameters, etc.), diluting your AI visibility across duplicate URLs.
Privacy Policy Page· Legal & Compliance
A missing privacy policy is one of the most frequently cited GDPR violations. Every EU data protection authority considers it a basic requirement.
Form CSRF Protection· Vulnerability
CSRF is in the OWASP Top 10. Without tokens, attackers can craft pages that automatically submit forms on your site as the victim's browser session.
Page Language· Accessibility / EAA
Screen readers use lang to pick the right pronunciation; without it Slovak may be read with English phonetics. Required by EN 301 549 § 9.3.1.1 (WCAG 3.1.1).
Form Labels· Accessibility / EAA
Unlabelled fields leave screen-reader users guessing — search, newsletter and checkout forms become unusable. EN 301 549 § 9.1.3.1 / 9.4.1.2 (WCAG 1.3.1 / 4.1.2).

Action plan by impact and effort

Every problem found, sorted by how much fixing it helps and how much work the fix takes. Start with the quick wins.

Quick wins (4)

High impact, little work. Do these first.

FindingCategoryEffort
Meta DescriptionSEOquick fix
Viewport ConfigurationMobilequick fix
Canonical Tag for AI DeduplicationAI Readinessquick fix
Page LanguageAccessibility / EAAquick fix

Bigger projects (6)

High impact, but the fix needs planning.

FindingCategoryEffort
Privacy Policy PageLegal & Complianceabout a day
Form Input Labels (WCAG 3.3.2)Mobileabout a day
Organization Schema + Entity LinkingAI Readinessabout a day
Form CSRF ProtectionVulnerabilityabout a day
Form LabelsAccessibility / EAAabout a day
Unused Code (CSS + JS)Performanceproject

Small fixes (18)

Lower impact, quick to do.

FindingCategoryEffort
Twitter/X CardsSEOquick fix
Canonical URLSEOquick fix
HTML Language AttributeSEOquick fix
DNSSECSecurityquick fix
Referrer-PolicySecurityquick fix
Permissions-PolicySecurityquick fix
Technology DisclosureSecurityquick fix
Subresource Integrity (SRI)Securityquick fix
security.txt (RFC 9116)Securityquick fix
Iframe SandboxingSecurityquick fix
Theme ColorMobilequick fix
Form Input TypesMobilequick fix

+6 more

Later (28)

Lower impact and more work. Plan them once the rest is done.

FindingCategoryEffort
Accessibility FundamentalsSEOabout a day
CDN / WAF ProtectionSecurityabout a day
Touch Target SizeMobileabout a day
Font Size ReadabilityMobileabout a day
Link Text Quality (WCAG 2.4.4)Mobileabout a day
Structured Data FoundationAI Readinessabout a day
FAQ Schema (Direct AI Answers)AI Readinessabout a day
Image Alt Text Quality for AIAI Readinessabout a day
Cookie PolicyLegal & Complianceabout a day
Forms Without Privacy NoticeLegal & Complianceabout a day
Right to Erasure (Data Deletion)Legal & Complianceabout a day
Image Alt TextAccessibility / EAAabout a day

+16 more

Performance

91/100
Weight: 25% · 11 OK · 5 warnings · 1 failures · 19 total
Unused Code (CSS + JS)Failed
285 KB wasted on unused code!
Why it matters: Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.
How to fix: You're loading 285 KB of code that isn't used on this page. 1) Audit plugins and remove unused ones, 2) Use code-splitting for page-specific JS, 3) Run PurgeCSS on your stylesheets.
Total Page WeightWarning
2.0 MB, 105 requests (optimal: <1.5 MB, <50 req)
Why it matters: A 3 MB page takes 6+ seconds on 3G mobile. Most e-commerce traffic is mobile — heavy pages lose customers on poor connections.
How to fix: Reduce page weight: compress images to WebP (saves 30-50%), enable text compression (gzip/brotli), lazy load below-fold images, remove unused CSS/JS.
JavaScript BudgetWarning
1014 KB — over the 600 KB budget, but below the 1270 KB median of the award-winning shops we benchmarked
Why it matters: Measured on a first load with no interaction, so scripts gated behind cookie consent don't count against you here. The 600 KB bar is best practice, not the cohort average: the shops we benchmarked have a median of 1 270 KB, and the best of them (a category winner that won on mobile) ships 410 KB.
How to fix: Split the bundle so a product page doesn't load checkout and account code. Defer third-party scripts until interaction. Drop unused plugin bundles — on most shops these outweigh your own code.
Request BudgetWarning
105 requests — over the budget of 80, but at or below the median of the award-winning shops we benchmarked (140)
Why it matters: The 80-request bar is best practice; the benchmarked cohort median is 140 and the best shop manages 37. Being under the median is not the same as being fast.
How to fix: Bundle CSS/JS that always loads together, serve icons as a sprite or font rather than individual files, and lazy-load below-fold images so they aren't requested on load.
Resource Hints (Preload/Preconnect)Warning
Why it matters: Preconnect saves 100-500ms per third-party origin by establishing connections early. Preload starts downloading critical resources before the browser discovers them in CSS/JS.
How to fix: Add resource hints: <link rel='preconnect' href='https://fonts.googleapis.com'> for third-party origins, <link rel='preload' as='image' href='hero.webp'> for critical resources.
Font PreloadingWarning
Custom fonts detected without preload hints
Why it matters: Fonts are discovered late in the render pipeline (after CSS is parsed). Preloading tells the browser to download them immediately, reducing Flash of Invisible Text (FOIT) by 200-500ms.
How to fix: Preload your primary font: <link rel='preload' href='/fonts/main.woff2' as='font' type='font/woff2' crossorigin>. For Google Fonts: preconnect to fonts.gstatic.com.
Server Response Time (TTFB)Passed
8ms
First Contentful Paint (FCP)Passed
0.30s
Largest Contentful Paint (LCP)Passed
0.98s — Core Web Vital ✓
Total Blocking Time (TBT)Passed
168ms
Cumulative Layout Shift (CLS)Passed
0.000 — Core Web Vital ✓
Speed IndexPassed
1.29s
Text Compression (gzip/brotli)Passed
All text resources properly compressed
Lazy LoadingPassed
53% of images use native lazy loading (109/207)
HTTP/3 (QUIC) SupportPassed
HTTP/3 enabled via Alt-Svc header
Script Loading StrategyPassed
100% of scripts use async/defer/module (0 async, 13 defer, 0 module)
CSS File CountPassed
6 CSS file(s) — well consolidated
Third-party ServicesInfo
Not measured — PageSpeed did not return the third-party audit for this URL
Why it matters: We report this as unmeasured rather than as zero third parties, because those are very different findings.
How to fix: Re-run the scan, or check the third-party summary directly at PageSpeed Insights.
Render-blocking ResourcesInfo
Not measured — PageSpeed did not return the render-blocking audit for this URL
How to fix: Re-run the scan, or test directly at PageSpeed Insights. This metric needs a successful Lighthouse lab run.
Category 1 / 8 · www.liveagent.sk · Zulien Score

SEO

85/100
Weight: 20% · 17 OK · 4 warnings · 1 failures · 23 total
Meta DescriptionFailed
Why it matters: Without a meta description, Google auto-generates one — often poorly. A custom description gives you control over the SERP snippet and improves click-through.
How to fix: Write a compelling meta description (120-160 chars) with a call-to-action. Include your target keyword naturally.
Twitter/X CardsWarning
Why it matters: Twitter Cards make your links stand out in X/Twitter feeds. Without them, shared links appear as plain text URLs.
How to fix: Add <meta name='twitter:card' content='summary_large_image'>, twitter:title, and twitter:image tags.
Canonical URLWarning
og:url present (https://www.liveagent.sk/) but <link rel=canonical> missing
Why it matters: og:url helps social platforms but Google ranks the canonical tag higher. With both present, you avoid any duplicate-content ambiguity.
How to fix: Add <link rel='canonical' href='https://www.liveagent.sk/'> to <head>. og:url covers social sharing; canonical covers Google + AI crawlers explicitly.
HTML Language AttributeWarning
Why it matters: The lang attribute helps search engines serve your content to the right language audience and improves accessibility.
How to fix: Add lang attribute to your <html> tag, e.g., <html lang='en'> or <html lang='de'>.
Accessibility FundamentalsWarning
2/4 a11y signals — missing: skip navigation link, lang attribute
Why it matters: The European Accessibility Act (EAA) takes effect June 2025 for e-commerce. Non-compliant sites face fines. Accessibility also improves SEO, as Google treats it as a ranking signal.
How to fix: Add: ARIA landmark roles (role='navigation', role='main'), aria-label on interactive elements, a 'Skip to content' link, and lang attribute on <html>.
Meta TitlePassed
40 chars — "LiveAgent - Helpdesk Softvér a Live Chat"
H1 HeadingPassed
"Poskytujte bezproblémovú podporu s AI helpdeskom"
Content Structure (H2 Headings)Passed
9 H2 subheadings found
Open Graph TagsPassed
og:title, og:description, og:image, og:type
Open Graph Image FormatPassed
image/jpeg
Structured Data (JSON-LD)Passed
1 block(s): Review, Person, SoftwareApplication
JSON-LD ValidityPassed
1 block(s) parse cleanly
robots.txtPassed
Present, references sitemap
XML SitemapPassed
Found with 1347 URLs
Image Alt AttributesPassed
99% of 207 images have alt text
FaviconPassed
Favicon detected
Image Format OptimizationPassed
74% next-gen formats (88 WebP, 0 AVIF)
Semantic HTML StructurePassed
5/6 semantic elements: <article>, <nav>, <main>, <header>, <footer>
Content DepthPassed
1876 words — sufficient content
Deep Heading HierarchyPassed
H2: 9, H3: 32 — well-structured content
Internal LinkingPassed
29 internal links — strong site navigation
Sitemap FreshnessPassed
Newest <lastmod> 14 day(s) ago
Text-to-HTML RatioInfo
4% ratio but 1876 words — content is substantial; the low ratio is markup/inline-JS bloat, not thin content
Why it matters: Text-to-HTML ratio is only a thin-content signal when actual word count is also low. With 500+ words, search engines have plenty to rank on.
How to fix: Your text content is sufficient. To raise the ratio, move inline <script>/<style> to external files and trim template bloat — this is a performance/cleanliness win, not a content gap.
Category 2 / 8 · www.liveagent.sk · Zulien Score

Security

84/100
Weight: 15% · 9 OK · 8 warnings · 0 failures · 17 total
DNSSECWarning
No DNSKEY records — zone is unsigned
Why it matters: Without DNSSEC, attackers controlling intermediate resolvers can forge responses for your domain — sending users to phishing sites with valid HTTPS that match your name. EU national CSIRTs (SK-CERT, NÚKIB) recommend DNSSEC for all in-scope entities.
How to fix: Enable DNSSEC at your DNS host (most modern registrars offer 1-click activation: Cloudflare, Route 53, Google Cloud DNS, web.sk, websupport.sk). Verify via dnsviz.net afterwards.
Referrer-PolicyWarning
Why it matters: Without a referrer policy, browsers send the full URL to third parties. This can leak sensitive data like session tokens in URLs or internal page paths.
How to fix: Add header: Referrer-Policy: strict-origin-when-cross-origin — this is the best balance between functionality and privacy.
Permissions-PolicyWarning
Why it matters: Without Permissions-Policy, any third-party script (ads, analytics, chat widgets) can access camera, microphone, and geolocation without your knowledge.
How to fix: Add: Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=() — disable APIs your site doesn't need.
Technology DisclosureWarning
Server: AmazonS3
Why it matters: Exposing exact server/PHP versions lets attackers search CVE databases for specific exploits. This is the first step in most automated attacks.
How to fix: Hide server version: set ServerTokens Prod (Apache) or server_tokens off (Nginx). Remove X-Powered-By header completely.
Subresource Integrity (SRI)Warning
Only 0/3 SRI-eligible third-party scripts have integrity hashes
Why it matters: Without SRI, if a version-pinned third-party CDN is compromised, attackers can inject malicious code into your site — the same vector as the British Airways Magecart breach.
How to fix: Add integrity='sha384-...' and crossorigin='anonymous' to version-pinned third-party <script> tags (use srihash.org). Auto-updating provider scripts (analytics, payment SDKs, consent tools) are correctly excluded — they can't use SRI.
security.txt (RFC 9116)Warning
Why it matters: security.txt lets ethical hackers report vulnerabilities responsibly. Without it, they may disclose publicly or not report at all.
How to fix: Create /.well-known/security.txt with Contact, Expires, and Preferred-Languages fields. See securitytxt.org for the generator.
CDN / WAF ProtectionWarning
Why it matters: Without a CDN/WAF, your origin server is directly exposed to DDoS attacks, bot traffic, and brute-force attempts.
How to fix: Add a CDN/WAF like Cloudflare (free tier), Sucuri, or Fastly. They provide DDoS protection, bot filtering, and SSL management.
Iframe SandboxingWarning
1/1 unknown iframe(s) without sandbox attribute
Why it matters: Unsandboxed iframes from unknown sources can access your DOM, run scripts, and navigate the top window. They should be sandboxed to prevent clickjacking and XSS.
How to fix: Add a sandbox attribute to non-provider <iframe> elements. Use sandbox='allow-scripts allow-same-origin' for third-party embeds. Trusted media/payment embeds (YouTube, Maps, Stripe, reCAPTCHA) are correctly excluded — they need full privileges to work.
SSL/TLS CertificatePassed
Valid HTTPS connection established
CAA DNS RecordPassed
2 CAA records (issuers: amazon.com, letsencrypt.org)
Why it matters: CAA records prevent unauthorized CAs from issuing certs for your domain — a documented attack vector after the DigiNotar and Symantec incidents.
HTTP → HTTPS RedirectPassed
HTTP properly redirects to HTTPS
HSTS (Strict-Transport-Security)Passed
max-age=31536000, preload, includeSubDomains
Content-Security-Policy (CSP)Passed
Present and reasonably configured
Clickjacking ProtectionPassed
X-Frame-Options: SAMEORIGIN
X-Content-Type-OptionsPassed
nosniff
Cookie Security FlagsPassed
No cookies set on initial response
Server Version DisclosurePassed
AmazonS3 — version hidden
Category 3 / 8 · www.liveagent.sk · Zulien Score

Mobile

62/100
Weight: 10% · 4 OK · 7 warnings · 2 failures · 13 total
Viewport ConfigurationFailed
Why it matters: Without the viewport tag, mobile browsers render at 980px width and zoom out — making text unreadable and buttons untappable. Google uses mobile-first indexing, so this directly kills rankings.
How to fix: Add <meta name='viewport' content='width=device-width, initial-scale=1'> to your <head>. This is the absolute minimum for mobile compatibility.
Form Input Labels (WCAG 3.3.2)Failed
Only 0/8 inputs have a label (0%)
Why it matters: The European Accessibility Act applies from 28 June 2025. Shops above 10 employees or €2M turnover must meet WCAG 2.1 AA — missing labels are among the most commonly actionable failures.
How to fix: 8 input elements have no label. Every input needs a matching <label for="id">Text</label> or an aria-label. A placeholder is NOT a label (WCAG 3.3.2). On a checkout or registration form this costs conversion and breaches EN 301 549 (EAA 2026).
Mobile Performance ScoreWarning
68/100 (target: 90+)
Why it matters: Most e-commerce traffic is mobile. Google ranks based on mobile performance, not desktop.
How to fix: Optimize for mobile: compress images to WebP, defer non-critical JS, reduce CSS file size. Mobile CPUs are several times slower than desktop — what's fast on desktop is slow on mobile.
Touch Target SizeWarning
Some tappable targets are too small or too close together (Lighthouse tap-targets audit)
Why it matters: Small tap targets cause mis-taps on mobile. In e-commerce, a mis-tap on 'Remove from cart' instead of 'Checkout' directly loses revenue.
How to fix: Ensure ALL interactive elements (buttons, links, form fields) are at least 48×48px with 8px minimum spacing between them. Pay special attention to: navigation menus, filter buttons, product variant selectors, and footer links.
Font Size ReadabilityWarning
Some text renders below the 12px legibility threshold (Lighthouse font-size audit)
Why it matters: Text smaller than 16px forces mobile users to pinch-zoom. This breaks the responsive layout and creates a frustrating experience.
How to fix: Set minimum 16px font size for body text. Use relative units (rem/em) instead of px for scalability. Product titles: 18px+, prices: 20px+, CTAs: 16px+ with bold.
Responsive Design TechniquesWarning
Why it matters: Non-responsive sites are automatically penalized by Google in mobile search results. With mobile-first indexing, this is a critical ranking factor.
How to fix: Implement responsive CSS with @media queries for key breakpoints: 480px (small mobile), 768px (tablet), 1024px (laptop). Use Flexbox and CSS Grid for fluid layouts.
Theme ColorWarning
Why it matters: Theme-color creates a polished, branded mobile experience. It makes your site look native and professional.
How to fix: Add <meta name='theme-color' content='#your-brand-color'> to match your brand. Browsers use this to color the address bar, task switcher, and PWA chrome.
Form Input TypesWarning
email fields use type='text' instead of type='email'
Why it matters: Correct input types show specialized mobile keyboards — email keyboard with @, phone with number pad. This reduces input errors and speeds up form completion.
How to fix: Use semantic input types: type='email' for email (shows @ keyboard), type='tel' for phone (shows number pad), type='search' for search (shows search button). These trigger optimized mobile keyboards.
Link Text Quality (WCAG 2.4.4)Warning
1 links have generic text ("click here", "more", "here"...)
Why it matters: WCAG 2.4.4: the purpose of a link must be clear from its text. Vague links hurt usability, conversion and SEO (Google reads anchor text for relevance).
How to fix: Replace 'Click here' and 'Read more' with descriptive text: 'Read more about GDPR', 'See module pricing'. Screen readers read links out of context, so a bare 'more' carries no meaning.
Content Fits ViewportPassed
No horizontal scrolling needed
Mobile Navigation (Semantic)Passed
<nav> element present — proper navigation landmark
Responsive Images (srcset)Passed
182 image(s) use srcset for responsive sizing
Heading Hierarchy (WCAG 1.3.1)Passed
No skipped heading levels
Category 4 / 8 · www.liveagent.sk · Zulien Score

AI Readiness

71/100
Weight: 10% · 12 OK · 14 warnings · 2 failures · 31 total
Organization Schema + Entity LinkingFailed
Why it matters: Organization schema is the foundation of your AI identity. Without it, AI assistants can't confidently attribute information to your brand, verify your legitimacy, or show your Knowledge Panel.
How to fix: Add Organization (or LocalBusiness for physical stores) schema with: name, logo, url, description, contactPoint, address, and sameAs linking to all your official profiles (LinkedIn, Facebook, Wikipedia if available).
Canonical Tag for AI DeduplicationFailed
Why it matters: Without a canonical tag, AI models may index multiple versions of the same page (with/without trailing slash, with parameters, etc.), diluting your AI visibility across duplicate URLs.
How to fix: Add <link rel='canonical' href='https://your-absolute-url'> to every page. This tells AI engines which URL is the authoritative version of this content.
Structured Data FoundationWarning
Only 1 distinct schema type (Review) — insufficient for AI visibility
Why it matters: Single-schema sites get minimal AI coverage. AI models need multiple data signals to confidently recommend your store.
How to fix: One schema type is not enough. Add at minimum: Organization (identity), Product (commerce), BreadcrumbList (navigation), WebSite+SearchAction (discoverability), FAQPage (Q&A answering).
FAQ Schema (Direct AI Answers)Warning
Why it matters: ChatGPT, Perplexity, and Google AI Overviews pull FAQ answers verbatim. FAQ schema is one of the fastest ways to get your content cited by AI.
How to fix: Add FAQPage schema to every product page and category page. Include 3-5 Q&As per page covering: product specifications, shipping, returns, usage instructions. Format: question (full sentence) + answer (75-150 words).
Structured Content (Lists & Tables)Warning
21 lists found — consider adding comparison tables
Why it matters: AI models are biased toward extracting data from HTML lists and tables. Perplexity and ChatGPT pull bullet points and table data with higher accuracy than paragraph text.
How to fix: Add comparison tables to your content. Use <ul>/<ol> for feature lists, specifications, and benefits. Use <table> for product comparisons, pricing tiers, and specifications. AI extracts structured content much faster than paragraphs.
Content Freshness SignalsWarning
Visible date found but not in structured data
Why it matters: AI models weight recency in their citation algorithms. Freshness signals tell AI your content is current and reliable.
How to fix: Add both: 1) dateModified and datePublished in your Article/Product JSON-LD schema, 2) A visible 'Last updated: [date]' on the page. Both signals reinforce content freshness for AI.
Entity Clarity & Brand SignalsWarning
OG tags complete but no sameAs entity links
Why it matters: AI needs to confidently identify your brand entity. Open Graph and sameAs together create a cross-platform identity that AI models recognize.
How to fix: For full entity clarity: 1) Complete Open Graph tags (og:title, og:description, og:image, og:type), 2) Add sameAs in Organization schema linking to Wikipedia, LinkedIn, Facebook, and other profiles.
Author Expertise Signals (E-E-A-T)Warning
Why it matters: AI models weight author expertise heavily. Pages from identified experts get cited more than anonymous content. This is especially important for product guides, reviews, and advice content.
How to fix: For content pages (blog, guides, about): add Article/BlogPosting schema with author property linking to Person schema. Include the author's jobTitle, credentials, and social profiles.
Extractable Answer BlocksWarning
89 paragraphs, avg 24 words — too short for citation
Why it matters: AI extracts individual paragraphs as answer snippets — dense walls of text get skipped. Focused 40-80 word paragraphs are the most citable.
How to fix: Optimal paragraphs for AI citation are 40-80 words. Break long paragraphs into focused, self-contained answer blocks. Each should make one clear point that AI can extract and quote.
Section Length OptimizationWarning
Avg section: 69 words — only 7% in 80-200 word optimal range
Why it matters: For Google AI Overviews, 100-150 words per section is the sweet spot — long sections get skipped and very short ones lack substance.
How to fix: Restructure content into sections of 120-180 words between H2/H3 headings. Each section should cover one topic completely. Split sections over 300 words, expand sections under 80 words.
Q&A Format HeadingsWarning
2 question heading(s) — add more
Why it matters: AI search engines like Perplexity and ChatGPT match user questions to heading-answer pairs. Q&A format headings are directly extractable by AI and trigger FAQ-style rich results.
How to fix: Phrase H2/H3 headings as questions: 'How does...?', 'What is...?', 'Why should...?' followed by a direct 1-2 sentence answer. This is a leading format AI assistants use to generate responses.
Knowledge Graph ReadinessWarning
2/4 signals — missing: sameAs links (Wikipedia, LinkedIn), Organization schema
Why it matters: @id creates a persistent entity identifier that connects your schema across pages and platforms, which is how AI builds a verified brand entity.
How to fix: Add: sameAs links (Wikipedia, LinkedIn), Organization schema. Use @id in JSON-LD to create a unique node identifier. Ensure your brand name is identical in title, schema, and OG tags. Link to Wikipedia/Wikidata via sameAs.
Content Readability for AIWarning
Grade 20 — too complex for broad AI citation (technical threshold: 14)
Why it matters: Content above grade 12 readability is harder for AI to extract as clear, concise answers. Pages using clear headers and approachable language are cited more often.
How to fix: Simplify sentences (target 15-20 words average), use common words, break complex ideas into shorter paragraphs. AI extracts content for general audiences — if it's too academic, AI skips it.
Image Alt Text Quality for AIWarning
76% good, 20 poor, 3 missing
Why it matters: AI uses alt text to understand images for visual search (Google Lens, Bing Visual Search), product recommendations, and accessibility. Quality alt text opens more discovery channels.
How to fix: Improve alt text: use 3-15 descriptive words per image. Include product name, key feature, and context. Bad: 'image1' or 'photo'. Good: 'Red leather wallet with RFID protection — front view'.
Expert Quotations & CitationsWarning
Why it matters: Content without citations or expert quotes appears unverified to AI. AI assistants prefer content backed by named sources, data references, and expert opinions.
How to fix: Add 2-3 expert quotes or data citations per major page. Use <blockquote> for quotes and link to authoritative sources (.gov, .edu, Wikipedia, industry reports).
WebMCP Agentic ReadinessWarning
Why it matters: WebMCP is how AI agents will interact with your store (search products, add to cart, check availability). Google and Microsoft are co-developing this standard.
How to fix: WebMCP (W3C Community Group standard, Chrome 146+) lets pages declare structured tools for AI agents. Add toolname and tooldescription attributes to <form> elements, or include a <script type='application/webmcp+json'> manifest.
AI Bot Access PolicyPassed
No AI bot restrictions (allowed by default)
AI agent access (live)Passed
ChatGPT-User and PerplexityBot get the same page as a browser
Content Accessibility for AIPassed
1876 words in raw HTML (3.9% text ratio) — readable by AI crawlers without executing JS
Content Depth for AIPassed
1876 words — rich content for AI analysis and citation
Answer-First Content FormatPassed
First paragraph: 45 words — good content density above the fold
Heading Hierarchy for AIPassed
Proper structure: 1 H1 → 9 H2s → 32 H3s — clear content outline
Semantic HTML StructurePassed
5/6 semantic elements: <article>, <nav>, <main>, <header>, <footer>
Reviews & Ratings SchemaPassed
AggregateRating/Review data found — social proof for AI
Statistics & Data PresencePassed
13 data points found — strong citation magnet
Internal Link DensityPassed
15 contextual internal links per 1,000 words — strong knowledge graph signal
Content-to-Boilerplate RatioPassed
68% of text in <main>/<article> — clean content signal
Social Proof (Testimonials / Case Studies)Passed
Strong social proof: testimonials, case studies / portfolio
llms.txt (AI Site Descriptor)Info
Not present — not required for AI visibility
Why it matters: llms.txt is the emerging standard for AI-readable site descriptions — like robots.txt was for search engines. Without it, AI assistants have no guided overview of your store.
How to fix: Create /llms.txt in Markdown format: # Your Store Name > One-line summary of your business and key offerings. Detailed description paragraph. ## Products - [Product Category](URL): Description ## About - [About Us](URL): Company history and values See llmstxt.org for the full specification.
llms-full.txt (Complete AI Content)Info
Not present — not required for AI visibility
Why it matters: llms-full.txt provides AI models with your entire site content in one parseable file. It's the difference between an AI having a brief overview vs. deep knowledge of your products and services.
ai.txt (AI Permissions)Info
Not present — optional; AI-bot permissions are enforced via robots.txt, not ai.txt
Why it matters: ai.txt is an emerging standard for fine-grained AI permissions beyond robots.txt. It gives you control over how AI uses your content.
Category 5 / 8 · www.liveagent.sk · Zulien Score

Legal & Compliance

70/100
Weight: 10% · 7 OK · 4 warnings · 1 failures · 14 total
Privacy Policy PageFailed
Why it matters: A missing privacy policy is one of the most frequently cited GDPR violations. Every EU data protection authority considers it a basic requirement.
How to fix: Create a comprehensive privacy policy covering: what data you collect, why (legal basis), how long you store it, who you share it with, and how users can exercise their GDPR rights (access, deletion, portability).
GDPR Art. 12 · GDPR Art. 13 · GDPR Art. 14 · SK 18/2018 § 19 · SK 18/2018 § 20
Cookie PolicyWarning
Why it matters: The ePrivacy Directive requires transparent cookie disclosure. Vague statements like 'we use cookies for functionality' don't meet the specificity requirement.
How to fix: Create a separate cookie policy page listing every cookie by: name, provider, purpose, category (necessary/analytics/marketing), and expiration. Most CMPs auto-generate this.
Legal Contact / Imprint PageWarning
Why it matters: In DACH countries, a missing Impressum can trigger fines and competitor cease-and-desist letters. For all EU stores, identifying the data controller is a GDPR Article 13 requirement.
How to fix: Add an imprint/about-us page with: company name, registered address, contact email, VAT number, and trade register info. In Germany/Austria/Switzerland this is legally required (Impressumspflicht).
Forms Without Privacy NoticeWarning
1 form(s) on page with no privacy policy link
Why it matters: GDPR Article 13 requires informing users about data processing at the point of collection. Forms without privacy notices violate the transparency principle.
How to fix: Add a link to your privacy policy next to or below every form that collects personal data (contact, registration, newsletter). Include a checkbox for consent where required.
Right to Erasure (Data Deletion)Warning
Why it matters: GDPR Article 17 gives users the 'right to be forgotten.' EU regulators expect a clear, accessible process, and obstructing erasure requests is a documented enforcement finding.
How to fix: Provide a clear mechanism for users to request data deletion — either a dedicated page, a form, or explicit instructions in your privacy policy. Include a 'Delete my account' option in user settings.
Cookie Consent Banner (CMP)Passed
TrustArc detected
Tracking Scripts & ConsentPassed
No tracking scripts detected
Data Encryption (No Mixed Content)Passed
All resources loaded over HTTPS
Third-party Data SharingPassed
3 third-party domain(s)
Newsletter ConsentPassed
Newsletter form with consent mechanism detected
Data Protection Officer ContactPassed
DPO / data protection contact found
Withdrawal of Consent MechanismPassed
Consent withdrawal / opt-out mechanism found
Terms & Conditions PageInfo
No Terms & Conditions link found — for a non-commercial/informational site this is optional (no purchase or paid service to govern)
Why it matters: Consumer T&C (AGB/VOP) obligations attach to selling goods or services. A purely informational or non-profit site has no transaction to govern, so missing T&C isn't a compliance gap.
How to fix: If you accept memberships, donations, sign-ups, or run events with paid tickets, publish simple Terms of Use / participation rules and link them in the footer.
AI chatbot disclosureInfo
Chat widget detected: LiveAgent. If it answers with AI (e.g. an AI agent or auto-replies), visitors must be told they are talking to an AI.
Why it matters: AI Act Article 50(1) (Regulation (EU) 2024/1689, applies from 2 August 2026) requires AI systems that interact with people to inform them they are interacting with an AI, unless it is obvious from the context.
How to fix: If the chat uses AI (Tidio Lyro, Intercom Fin, Smartsupp AI, Chatbase…), show a clear notice at the start of the conversation, e.g. 'You are chatting with an AI assistant', and offer a way to reach a human. If only people answer, nothing to do.
Category 6 / 8 · www.liveagent.sk · Zulien Score

Vulnerability

90/100
Weight: 10% · 9 OK · 2 warnings · 1 failures · 13 total
Form CSRF ProtectionFailed
1 form(s) without CSRF tokens
Why it matters: CSRF is in the OWASP Top 10. Without tokens, attackers can craft pages that automatically submit forms on your site as the victim's browser session.
How to fix: Add CSRF token validation to every form. Most CMS frameworks have built-in CSRF protection — make sure it's enabled on all forms, including search and newsletter signup.
CORS ConfigurationWarning
Access-Control-Allow-Origin: * (allows any domain)
Why it matters: A wildcard CORS policy allows any website to make requests to your API/pages. Combined with Access-Control-Allow-Credentials, this enables cross-origin data theft.
How to fix: Replace the wildcard CORS header with specific allowed origins. Avoid Access-Control-Allow-Origin: * on pages with authentication or sensitive data.
Cross-Origin IsolationWarning
Why it matters: Without cross-origin isolation headers, your site is vulnerable to Spectre attacks that can leak sensitive data across browser tabs. These headers are required for SharedArrayBuffer and high-resolution timers.
How to fix: Add Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Resource-Policy: same-origin headers. These protect against Spectre-type side-channel attacks.
CMS Version DisclosurePassed
No generator tag — CMS identity hidden
Sensitive Files ExposedPassed
.env, .git, composer.json — all properly blocked
Install Script ExposedPassed
No /install/ or /setup/ paths accessible
Directory ListingPassed
Disabled — file structure hidden
Admin Panel at Default URLPassed
Not found at common paths (/admin, /wp-admin, /administrator, /backoffice)
Debug Mode / Error ExposurePassed
No debug indicators found in page output
SPF Record (Email Security)Passed
SPF configured: v=spf1 -all
DMARC Policy (Email Auth)Passed
DMARC enforced: p=reject
Payment Page SecurityPassed
All essential security headers present on payment page
Email InfrastructureInfo
No MX records — domain does not receive email
Category 7 / 8 · www.liveagent.sk · Zulien Score

Accessibility / EAA

41/100
Weight: 10% · 3 OK · 2 warnings · 2 failures · 8 total
Page LanguageFailed
The <html> element has no lang attribute
Why it matters: Screen readers use lang to pick the right pronunciation; without it Slovak may be read with English phonetics. Required by EN 301 549 § 9.3.1.1 (WCAG 3.1.1).
How to fix: Add a lang attribute to <html>, e.g. <html lang="sk">, matching the primary language.
Form LabelsFailed
8 of 8 form inputs have no associated label
Why it matters: Unlabelled fields leave screen-reader users guessing — search, newsletter and checkout forms become unusable. EN 301 549 § 9.1.3.1 / 9.4.1.2 (WCAG 1.3.1 / 4.1.2).
How to fix: Associate every input with a <label for> (or aria-label / aria-labelledby). Placeholders are not labels.
Image Alt TextWarning
3 of 207 images missing alt text
Why it matters: Every image missing alt text is content a screen-reader user cannot access (WCAG 1.1.1 / EN 301 549 § 9.1.1.1).
How to fix: Add alt text to the remaining images (alt="" for decorative ones).
Skip LinkWarning
No skip-to-content link detected
Why it matters: Keyboard and screen-reader users otherwise tab through the whole menu on every page. EN 301 549 § 9.2.4.1 (WCAG 2.4.1).
How to fix: Add a visually-hidden "Skip to content" link as the first focusable element, targeting <main id="main">.
Heading StructurePassed
Single <h1> with a consistent heading outline
Link TextPassed
Links use descriptive text
Landmark RegionsPassed
Semantic landmarks present (<main>, <nav>/<header>)
EAA Legal BasisInfo
In scope for the European Accessibility Act (in force 28.6.2025): SK zákon 351/2022 Z. z., CZ zákon 424/2023 Sb., Dir. (EU) 2019/882 — assessed against EN 301 549. Inger provides EAA remediation audits.
Category 8 / 8 · www.liveagent.sk · Zulien Score

Next steps

  1. Start with the failures — every red item carries a How to fix note. Prioritise Security and Legal & Compliance, which carry statutory consequences.
  2. Re-run the audit after fixing — run a fresh scan at score.zulien.sk and compare the score.
  3. Get help with the harder ones — for a deep audit or an expert assessment, see inger.sk.
  4. Track NIS2 and GDPR compliance — if your shop falls under NIS2 (turnover over €10M or more than 50 staff), you need a formal compliance framework.

Online report

The full interactive version, with clickable links and the option to re-scan, is here:

https://score.zulien.sk/r/liveagent.sk

Disclaimer: This report is generated automatically by Zulien Score. Its findings come from publicly available data and technical analysis. For a legally binding assessment (of GDPR compliance, for instance) we recommend consulting a DPO or a lawyer specialising in data protection. Zulien Score is not a licensed legal or audit firm.
Zulien Score · score.zulien.sk · by Zulien · Hosted at inger.sk