Poor

Score Report

datart.sk

Scanned on July 27, 2026

Unknown
Last scanned: July 27, 2026
AI verdict

Your site needs urgent improvements in fundamentals. Add meta titles and descriptions to all pages—this is critical for search engines. Good news: your security is strong.

Action plan

Fix these 3 things first

Sorted by score impact — each fix moves your overall grade up.

+21potential gain

Performance

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

What we found: 705ms (optimal: <200ms)

Why it matters: TTFB over 600ms makes it nearly impossible to pass Core Web Vitals. Every page load starts with this delay before anything else can happen.

How to fix: Your server is critically slow. Enable full-page caching (Varnish/Redis), use a CDN (Cloudflare/Fastly), upgrade hosting, or optimize database queries.
Evidence:PSI-lab· Confidence: high
Get Performance Optimization →

What we found: 693ms (good: <200ms)

Why it matters: TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.

How to fix: Critical: audit all JavaScript. 1) Remove unused plugins/modules, 2) Defer analytics and chat widgets, 3) Code-split large bundles, 4) Move heavy computation to web workers.
Evidence:PSI-lab· Confidence: high
Request quote for speed audit

What we found: 3.7 MB, 135 requests — too heavy!

Why it matters: Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is around 2 MB — you're well above that. Even small latency increases measurably reduce sales.

How to fix: Critical: your page is over 3 MB. 1) Convert all images to WebP/AVIF, 2) Lazy load everything below the fold, 3) Remove unused plugins, 4) Combine and minify CSS/JS, 5) Enable brotli compression.
Evidence:PSI-lab· Confidence: high
Get Performance Optimization →

What we found: 764 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 764 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: Only 0% of 2 scripts optimized — most are render-blocking

Why it matters: 2 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.

How to fix: Add defer or async to all <script src='...'> tags. Render-blocking scripts are a leading cause of slow FCP. Defer maintains execution order, async does not.
Evidence:HTML-heuristic· Confidence: high
Get Performance Optimization →

What we found: 5.63s (good: <3.4s)

Why it matters: Speed Index captures the overall visual loading experience. A slow Speed Index means users watch content load piece by piece instead of seeing a complete page.

How to fix: Speed Index measures visual completeness over time. Improve it by: prioritizing above-fold content, preloading critical resources, and minimizing render-blocking assets.
Evidence:PSI-lab· Confidence: high
Request quote for speed audit

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: no-store, no-cache, must-revalidate

Why it matters: no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time.

How to fix: Set appropriate cache headers: static assets should have max-age=31536000 with versioned filenames. HTML pages can use max-age=0 with ETag for revalidation.
Evidence:HTTP-header· Confidence: high
Request quote for speed audit

8 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?

Your store is losing customers every day. The issues above are costing you sales.

Critical score — request an expert audit

Hands-on review by our team: we identify root causes, prioritize fixes, and hand you an action plan. We'll send a tailored quote within 48h.

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
Komplexný audit e-shopu — 50+ kontrol v 7 kategóriách
44/100
Grade F
datart.sk
Dátum auditu: July 27, 2026
Online report: https://score.zulien.sk/r/datart.sk
Vygenerované 29. 7. 2026 11:10:43 · score.zulien.sk · by Zulien

Executive summary

38
Chýb
34
Upozornení
29
OK
114
Spolu kontrol

Skóre po kategóriách

KategóriaSkóreVáhaChybyUpozorneniaOK
Performance58/10025%535
SEO15/10020%1251
Security77/10015%159
Mobile40/10010%251
AI Readiness23/10010%1281
GDPR42/10010%262
Vulnerability83/10010%1110
Accessibility5/100—310

Kritické zistenia

Server Response Time (TTFB)· Performance
TTFB over 600ms makes it nearly impossible to pass Core Web Vitals. Every page load starts with this delay before anything else can happen.
Total Blocking Time (TBT)· Performance
TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.
Total Page Weight· Performance
Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is around 2 MB — you're well above that. Even small latency increases measurably reduce sales.
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.
Script Loading Strategy· Performance
2 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.
Meta Title· SEO
The title tag is a top on-page ranking factor. Google uses it as the main headline in search results — missing it means losing clicks.
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.
H1 Heading· SEO
The H1 is a primary content signal for search engines. Pages without an H1 rank lower for target keywords.
Content Structure (H2 Headings)· SEO
Pages without heading structure are harder to scan and miss long-tail ranking opportunities.
Open Graph Tags· SEO
Without OG tags, social platforms show auto-generated previews. Proper OG tags produce clean, clickable link cards.
Structured Data (JSON-LD)· SEO
Pages with structured data can earn rich snippets in Google — star ratings, prices, availability — which lift click-through.
XML Sitemap· SEO
Sitemaps help Google discover and index pages faster, especially for large stores with deep category structures.

Performance

58/100
Váha: 25% · 5 OK · 3 upozornení · 5 chýb · spolu 14
Server Response Time (TTFB)Zlyhalo
705ms (optimal: <200ms)
Prečo je to dôležité: TTFB over 600ms makes it nearly impossible to pass Core Web Vitals. Every page load starts with this delay before anything else can happen.
Ako opraviť: Your server is critically slow. Enable full-page caching (Varnish/Redis), use a CDN (Cloudflare/Fastly), upgrade hosting, or optimize database queries.
Total Blocking Time (TBT)Zlyhalo
693ms (good: <200ms)
Prečo je to dôležité: TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.
Ako opraviť: Critical: audit all JavaScript. 1) Remove unused plugins/modules, 2) Defer analytics and chat widgets, 3) Code-split large bundles, 4) Move heavy computation to web workers.
Total Page WeightZlyhalo
3.7 MB, 135 requests — too heavy!
Prečo je to dôležité: Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is around 2 MB — you're well above that. Even small latency increases measurably reduce sales.
Ako opraviť: Critical: your page is over 3 MB. 1) Convert all images to WebP/AVIF, 2) Lazy load everything below the fold, 3) Remove unused plugins, 4) Combine and minify CSS/JS, 5) Enable brotli compression.
Unused Code (CSS + JS)Zlyhalo
764 KB wasted on unused code!
Prečo je to dôležité: 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.
Ako opraviť: You're loading 764 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.
Script Loading StrategyZlyhalo
Only 0% of 2 scripts optimized — most are render-blocking
Prečo je to dôležité: 2 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.
Ako opraviť: Add defer or async to all <script src='...'> tags. Render-blocking scripts are a leading cause of slow FCP. Defer maintains execution order, async does not.
Speed IndexUpozornenie
5.63s (good: <3.4s)
Prečo je to dôležité: Speed Index captures the overall visual loading experience. A slow Speed Index means users watch content load piece by piece instead of seeing a complete page.
Ako opraviť: Speed Index measures visual completeness over time. Improve it by: prioritizing above-fold content, preloading critical resources, and minimizing render-blocking assets.
Resource Hints (Preload/Preconnect)Upozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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.
Cache-Control StrategyUpozornenie
no-store, no-cache, must-revalidate
Prečo je to dôležité: no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time.
Ako opraviť: Set appropriate cache headers: static assets should have max-age=31536000 with versioned filenames. HTML pages can use max-age=0 with ETag for revalidation.
First Contentful Paint (FCP)Prešlo
0.91s
Largest Contentful Paint (LCP)Prešlo
0.99s — Core Web Vital ✓
Cumulative Layout Shift (CLS)Prešlo
0.016 — Core Web Vital ✓
Text Compression (gzip/brotli)Prešlo
All text resources properly compressed
CSS File CountPrešlo
1 CSS file(s) — well consolidated
Render-blocking ResourcesInfo
Not measured — PageSpeed did not return the render-blocking audit for this URL
Ako opraviť: Re-run the scan, or test directly at PageSpeed Insights. This metric needs a successful Lighthouse lab run.
Kategória 1 / 8 · datart.sk · Zulien Score

SEO

15/100
Váha: 20% · 1 OK · 5 upozornení · 12 chýb · spolu 18
Meta TitleZlyhalo
Prečo je to dôležité: The title tag is a top on-page ranking factor. Google uses it as the main headline in search results — missing it means losing clicks.
Ako opraviť: Add a unique, descriptive <title> tag. Include your primary keyword near the start, keep it under 60 characters.
Meta DescriptionZlyhalo
Prečo je to dôležité: Without a meta description, Google auto-generates one — often poorly. A custom description gives you control over the SERP snippet and improves click-through.
Ako opraviť: Write a compelling meta description (120-160 chars) with a call-to-action. Include your target keyword naturally.
H1 HeadingZlyhalo
Prečo je to dôležité: The H1 is a primary content signal for search engines. Pages without an H1 rank lower for target keywords.
Ako opraviť: Add exactly one H1 tag containing your primary keyword. It should be the most prominent heading on the page.
Content Structure (H2 Headings)Zlyhalo
Prečo je to dôležité: Pages without heading structure are harder to scan and miss long-tail ranking opportunities.
Ako opraviť: Add H2 subheadings to structure your content. Each major section should have a descriptive H2.
Open Graph TagsZlyhalo
Prečo je to dôležité: Without OG tags, social platforms show auto-generated previews. Proper OG tags produce clean, clickable link cards.
Ako opraviť: Add og:title, og:description, og:image (1200×630px), and og:type meta tags to every page.
Structured Data (JSON-LD)Zlyhalo
Prečo je to dôležité: Pages with structured data can earn rich snippets in Google — star ratings, prices, availability — which lift click-through.
Ako opraviť: Add JSON-LD structured data: Product (with price, availability, reviews), Organization, BreadcrumbList, and WebSite schemas.
XML SitemapZlyhalo
Prečo je to dôležité: Sitemaps help Google discover and index pages faster, especially for large stores with deep category structures.
Ako opraviť: Generate an XML sitemap at /sitemap.xml listing all important pages. Exclude noindex pages, filters, and duplicate URLs. Reference it in robots.txt.
Text-to-HTML RatioZlyhalo
2% — very thin content (13 words)
Prečo je to dôležité: Google's Helpful Content Update specifically targets thin content pages, which hurts your rankings.
Ako opraviť: Your page is almost entirely HTML/CSS/JS with very little actual content. Add substantial product descriptions, content blocks, and informational text.
Semantic HTML StructureZlyhalo
0/6 semantic elements — poor structure
Prečo je to dôležité: Without semantic structure, search engines treat your page as an undifferentiated blob of content. Semantic HTML is essential for featured snippets, voice search, and AI-powered search.
Ako opraviť: Your page lacks semantic HTML5 elements. Replace generic <div> wrappers with <header>, <nav>, <main>, <article>, <aside>, and <footer> to give search engines and screen readers proper content signals.
Content DepthZlyhalo
Only 13 words — very thin content
Prečo je to dôležité: Pages with under 100 words are nearly invisible to search engines. Google can't determine relevance without sufficient text content. This is a critical ranking barrier.
Ako opraviť: This page has almost no text content. Add detailed product descriptions, buying guides, FAQs, or informational content. Search engines need text to understand and rank your page.
Internal LinkingZlyhalo
No internal links found
Prečo je to dôležité: A page with zero internal links is isolated from your site's link graph. Google may treat it as low-priority or not index it at all.
Ako opraviť: Add internal links to other pages on your site. Every page should link to related content, categories, and key landing pages.
Accessibility FundamentalsZlyhalo
No accessibility signals found
Prečo je to dôležité: The European Accessibility Act (EAA) makes web accessibility legally mandatory for EU e-commerce from June 28, 2025. Non-compliance risks fines and market access restrictions.
Ako opraviť: Your site lacks basic accessibility features. Add: 1) lang attribute on <html>, 2) ARIA roles on landmarks, 3) aria-label on buttons/links, 4) Skip navigation link. The EAA requires e-commerce accessibility by June 2025.
Twitter/X CardsUpozornenie
Prečo je to dôležité: Twitter Cards make your links stand out in X/Twitter feeds. Without them, shared links appear as plain text URLs.
Ako opraviť: Add <meta name='twitter:card' content='summary_large_image'>, twitter:title, and twitter:image tags.
Canonical URLUpozornenie
Prečo je to dôležité: Canonical tags prevent search engines from treating URL variants (with/without trailing slash, tracking params) as duplicate pages.
Ako opraviť: Add a <link rel='canonical'> tag pointing to the preferred URL. For a single-page site this is a one-line addition in <head>.
robots.txtUpozornenie
Prečo je to dôležité: robots.txt guides search engine crawling. Without it, crawlers may waste budget on irrelevant pages (admin, cart, checkout).
Ako opraviť: Create a robots.txt file at your domain root. Include a Sitemap directive pointing to your XML sitemap.
HTML Language AttributeUpozornenie
Prečo je to dôležité: The lang attribute helps search engines serve your content to the right language audience and improves accessibility.
Ako opraviť: Add lang attribute to your <html> tag, e.g., <html lang='en'> or <html lang='de'>.
Image Alt AttributesUpozornenie
No images found
Prečo je to dôležité: Images drive a meaningful share of Google searches. Missing images means missing ranking opportunities.
Ako opraviť: Add relevant images with descriptive alt attributes to improve engagement and image search visibility.
FaviconPrešlo
Favicon detected
Kategória 2 / 8 · datart.sk · Zulien Score

Security

77/100
Váha: 15% · 9 OK · 5 upozornení · 1 chýb · spolu 15
Content-Security-Policy (CSP)Zlyhalo
Prečo je to dôležité: CSP is a strong defense against XSS attacks. Without it, any injected script runs with full privileges. CSP blocks inline script injection.
Ako opraviť: Implement a CSP header. Start with: Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: — then gradually tighten.
X-Content-Type-OptionsUpozornenie
Prečo je to dôležité: Without nosniff, browsers may execute uploaded files as scripts. An attacker could upload a .jpg that's actually JavaScript and trick the browser into running it.
Ako opraviť: Add header: X-Content-Type-Options: nosniff
Referrer-PolicyUpozornenie
Prečo je to dôležité: 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.
Ako opraviť: Add header: Referrer-Policy: strict-origin-when-cross-origin — this is the best balance between functionality and privacy.
Cookie Security FlagsUpozornenie
6 cookie(s): 4 missing Secure, 4 missing HttpOnly, 3 missing SameSite
Prečo je to dôležité: Missing Secure flag = cookies sent over HTTP (stealable on WiFi). Missing HttpOnly = cookies readable by XSS. Missing SameSite = vulnerable to CSRF attacks.
Ako opraviť: Set all cookies with: Secure (HTTPS only), HttpOnly (no JS access), SameSite=Lax or Strict (CSRF protection). Session cookies MUST have all three.
security.txt (RFC 9116)Upozornenie
Prečo je to dôležité: security.txt lets ethical hackers report vulnerabilities responsibly. Without it, they may disclose publicly or not report at all.
Ako opraviť: Create /.well-known/security.txt with Contact, Expires, and Preferred-Languages fields. See securitytxt.org for the generator.
CDN / WAF ProtectionUpozornenie
Prečo je to dôležité: Without a CDN/WAF, your origin server is directly exposed to DDoS attacks, bot traffic, and brute-force attempts.
Ako opraviť: Add a CDN/WAF like Cloudflare (free tier), Sucuri, or Fastly. They provide DDoS protection, bot filtering, and SSL management.
SSL/TLS CertificatePrešlo
Valid HTTPS connection established
DNSSECPrešlo
Zone is DNSSEC-signed (DNSKEY published)
Prečo je to dôležité: DNSSEC protects against DNS cache poisoning and on-path attackers redirecting your domain. Required by some sector regulators for NIS2 essential/important entities.
CAA DNS RecordPrešlo
5 CAA records
Prečo je to dôležité: CAA records prevent unauthorized CAs from issuing certs for your domain — a documented attack vector after the DigiNotar and Symantec incidents.
HTTP → HTTPS RedirectPrešlo
HTTP properly redirects to HTTPS
HSTS (Strict-Transport-Security)Prešlo
max-age=31536000, preload, includeSubDomains
Clickjacking ProtectionPrešlo
X-Frame-Options: SAMEORIGIN
Permissions-PolicyPrešlo
unload=()
Technology DisclosurePrešlo
Server identity hidden
Subresource Integrity (SRI)Prešlo
No SRI-eligible third-party scripts loaded
Kategória 3 / 8 · datart.sk · Zulien Score

Mobile

40/100
Váha: 10% · 1 OK · 5 upozornení · 2 chýb · spolu 8
Viewport ConfigurationZlyhalo
Prečo je to dôležité: 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.
Ako opraviť: Add <meta name='viewport' content='width=device-width, initial-scale=1'> to your <head>. This is the absolute minimum for mobile compatibility.
Mobile Performance ScoreZlyhalo
41/100 — critically slow
Prečo je to dôležité: A mobile score below 50 means your store takes several seconds to become usable on a phone. Slow mobile load drives users away before they see the store.
Ako opraviť: Your mobile experience is severely degraded. Priority fixes: 1) Reduce JavaScript, 2) Convert all images to WebP with responsive sizing, 3) Enable aggressive caching, 4) Use a CDN.
Touch Target SizeUpozornenie
Some tappable targets are too small or too close together (Lighthouse tap-targets audit)
Prečo je to dôležité: Small tap targets cause mis-taps on mobile. In e-commerce, a mis-tap on 'Remove from cart' instead of 'Checkout' directly loses revenue.
Ako opraviť: 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 ReadabilityUpozornenie
Some text renders below the 12px legibility threshold (Lighthouse font-size audit)
Prečo je to dôležité: Text smaller than 16px forces mobile users to pinch-zoom. This breaks the responsive layout and creates a frustrating experience.
Ako opraviť: 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 TechniquesUpozornenie
Prečo je to dôležité: Non-responsive sites are automatically penalized by Google in mobile search results. With mobile-first indexing, this is a critical ranking factor.
Ako opraviť: 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 ColorUpozornenie
Prečo je to dôležité: Theme-color creates a polished, branded mobile experience. It makes your site look native and professional.
Ako opraviť: 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.
Mobile Navigation (Semantic)Upozornenie
Prečo je to dôležité: Semantic <nav> elements are essential for mobile accessibility. Screen readers use them to let users jump directly to navigation — critical on small screens where content is long.
Ako opraviť: Wrap your navigation in a <nav> element. This helps mobile screen readers offer 'skip to navigation' and improves voice navigation (e.g., 'Siri, show me the menu').
Content Fits ViewportPrešlo
No horizontal scrolling needed
Kategória 4 / 8 · datart.sk · Zulien Score

AI Readiness

23/100
Váha: 10% · 1 OK · 8 upozornení · 12 chýb · spolu 29
Content Accessibility for AIZlyhalo
Only 13 words visible in HTML — content may be JS-dependent
Prečo je to dôležité: AI crawlers see only raw HTML. Content that only appears after JavaScript runs is invisible to them. Server-rendered content is the primary prerequisite for AI visibility.
Ako opraviť: Your page has very little content in the HTML source. If you're using a JavaScript framework (React, Vue, Angular), implement Server-Side Rendering (SSR) or Static Site Generation (SSG).
Structured Data FoundationZlyhalo
Prečo je to dôležité: Without structured data, your store is invisible to AI commerce. Google AI Overviews, ChatGPT Shopping, Perplexity, and Bing Copilot all rely on schema markup to understand and recommend products.
Ako opraviť: Add JSON-LD structured data immediately. Priority order: 1) Organization, 2) Product (with offers), 3) BreadcrumbList, 4) WebSite+SearchAction, 5) FAQPage. Use JSON-LD format exclusively — not Microdata or RDFa.
Organization Schema + Entity LinkingZlyhalo
Prečo je to dôležité: 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.
Ako opraviť: 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).
Content Depth for AIZlyhalo
Only 13 words — too thin for AI citation
Prečo je to dôležité: Pages with very little content are nearly invisible to AI search. Without substance, AI has nothing to quote, summarize, or recommend.
Ako opraviť: Your page has critically low content. Add: comprehensive product descriptions, feature lists, FAQs, buying guides, comparison tables, and trust signals (reviews, certifications, guarantees).
Answer-First Content FormatZlyhalo
No meaningful opening content for AI to extract
Prečo je to dôležité: Without a clear opening paragraph, AI assistants can't generate a useful summary of your page. They'll skip to competitor pages that provide immediate, quotable content.
Ako opraviť: Add a strong opening paragraph (50-100 words) that summarizes what this page offers. AI assistants use the first paragraph as the primary citation source.
Heading Hierarchy for AIZlyhalo
0 H1, 0 H2, 0 H3 — poor structure
Prečo je to dôležité: AI extracts information based on heading structure. Pages with proper H1→H2→H3 hierarchy are parsed more accurately by ChatGPT, Perplexity, and Google AI Overviews. Without it, AI may misinterpret your content.
Ako opraviť: Use exactly 1 H1 (page title), then organize content with H2 sections and H3 subsections. Each heading should describe the content that follows. Never skip heading levels (H1→H3 without H2).
Semantic HTML StructureZlyhalo
Prečo je to dôležité: Without semantic HTML, AI must guess content boundaries. This leads to navigation text mixed into product descriptions, footer content cited as main content, and overall poor AI understanding of your pages.
Ako opraviť: Replace <div> wrappers with: <header> (site header), <nav> (navigation), <main> (primary content), <article> (self-contained content), <aside> (sidebar), <footer>. This is the foundation of AI-readable HTML.
Content Freshness SignalsZlyhalo
Prečo je to dôležité: With no freshness signals, AI assumes your content is stale. ChatGPT and Perplexity both weight recency in their citation algorithms. Competitors who show recent updates will be cited instead of your static pages.
Ako opraviť: Add dateModified and datePublished to your JSON-LD schema, and display a visible 'Last updated' date on the page. Update content quarterly at minimum. AI heavily favors fresh, maintained content.
Entity Clarity & Brand SignalsZlyhalo
Prečo je to dôležité: AI assistants must be confident about entity identity before making recommendations. Without clear brand signals, AI defaults to better-known competitors.
Ako opraviť: Your brand has weak entity signals. Add: 1) Complete OG meta tags, 2) Organization schema with sameAs linking to all official profiles, 3) Consistent NAP (Name, Address, Phone) across the web.
Extractable Answer BlocksZlyhalo
Too few content paragraphs for AI to extract
Prečo je to dôležité: AI assistants extract individual paragraphs as citations. Without clear, self-contained content blocks, your page can't be quoted in AI-generated answers.
Ako opraviť: Add structured content with clear, focused paragraphs (40-80 words each). Each paragraph should answer one question or make one claim that AI can quote directly.
Canonical Tag for AI DeduplicationZlyhalo
Prečo je to dôležité: 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.
Ako opraviť: 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.
Knowledge Graph ReadinessZlyhalo
Prečo je to dôležité: Without Knowledge Graph signals, AI treats your brand as unverified. You won't get a Google Knowledge Panel, and AI assistants can't confidently attribute information to your brand.
Ako opraviť: Build your Knowledge Graph entity: 1) Add @id to Organization JSON-LD, 2) Use identical brand name in title, schema, and OG, 3) Add sameAs to Wikipedia/Wikidata/LinkedIn, 4) Use multiple corroborating schema types.
FAQ Schema (Direct AI Answers)Upozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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)Upozornenie
No structured content elements found
Prečo je to dôležité: Unstructured paragraph-only content is harder for AI to parse and cite. Pages with lists and tables get cited more often because AI can extract specific facts more reliably.
Ako opraviť: Add bulleted lists for features/benefits, numbered lists for steps/rankings, and tables for comparisons/specifications. These are the content formats AI extracts most reliably.
Author Expertise Signals (E-E-A-T)Upozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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.
Statistics & Data PresenceUpozornenie
No statistical data found in content
Prečo je to dôležité: Content without data is harder to cite. Perplexity and ChatGPT specifically seek pages with quantified claims and verifiable statistics.
Ako opraviť: Add numbers: pricing comparisons, performance metrics, customer statistics, industry benchmarks. Specific data (e.g., '99.9% uptime', '4.8/5 rating from 2,400 reviews') is what AI quotes most.
Q&A Format HeadingsUpozornenie
Prečo je to dôležité: Q&A content format matches how people query AI assistants. Without question-format headings, your content is harder for AI to map to user queries.
Ako opraviť: Add H2/H3 headings phrased as questions your customers ask: 'How much does shipping cost?', 'What sizes are available?', 'How do I return an item?' Follow each with a direct, concise answer.
Expert Quotations & CitationsUpozornenie
Prečo je to dôležité: Content without citations or expert quotes appears unverified to AI. AI assistants prefer content backed by named sources, data references, and expert opinions.
Ako opraviť: 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 ReadinessUpozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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.
Content-to-Boilerplate RatioUpozornenie
No <main> or <article> elements — AI can't isolate content from boilerplate
Prečo je to dôležité: Without semantic containers, AI crawlers must guess where content starts and navigation ends. This leads to poor content extraction and fewer citations.
Ako opraviť: Add <main> around your primary content and <article> around self-contained content blocks. This creates clear boundaries for AI content extraction.
AI Bot Access PolicyPrešlo
No AI bot restrictions (allowed by default)
llms.txt (AI Site Descriptor)Info
Not present — not required for AI visibility
Prečo je to dôležité: 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.
Ako opraviť: 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
Prečo je to dôležité: 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
Prečo je to dôležité: ai.txt is an emerging standard for fine-grained AI permissions beyond robots.txt. It gives you control over how AI uses your content.
Social Proof (Testimonials / Case Studies)Info
None detected. For a non-commercial/informational site, testimonials and case studies are optional
Prečo je to dôležité: Client testimonials and 'trusted by' logos are a B2B sales-cycle lever. A non-profit, club, or informational site isn't selling a service, so their absence isn't a credibility gap — hence informational, not scored.
Ako opraviť: Optional: member stories, event photos/recaps, partner logos, or press mentions build trust and give AI assistants more to cite about your organisation — but they don't gate credibility the way they do for a B2B vendor.
Agent-Commerce ReadinessInfo
33/100 — pre AI agentov nedostupné (Prístup 50 · Porozumenie 0 · Transakcia 50)
Prečo je to dôležité: Či dokáže autonómny nákupný AI agent (ChatGPT operator, Perplexity, budúce agentické asistenty) na vašom obchode: prísť dnu, prečítať a porozumieť produktom, objaviť celý katalóg a konať (kôš, podmienky). Toto meria málokto — a pre SK/CZ shopy nikto. Skóre spája AI-bot prístup, Product schema, produktové feedy (Merchant/Heureka/Zboží), WebMCP a nákupné podmienky do jedného agent-first pohľadu. Nadväzuje na pripravovaný verejný MCP konektor ("naskenuj tento obchod").
Agent: Prístup — dostane sa agent dnuInfo
50/100 (2 signály/-ov)
Agent: Porozumenie — rozumie produktomInfo
0/100 (2 signály/-ov)
Agent: Transakcia — vie konať (kôš/podmienky)Info
50/100 (1 signál)
Kategória 5 / 8 · datart.sk · Zulien Score

GDPR

42/100
Váha: 10% · 2 OK · 6 upozornení · 2 chýb · spolu 11
Cookie Consent Banner (CMP)Zlyhalo
Prečo je to dôležité: Since 2024, EU regulators actively enforce cookie consent. A non-compliant cookie banner is one of the most frequently fined GDPR offences.
Ako opraviť: Install a certified consent management platform: Cookiebot, OneTrust, Usercentrics, or CookieYes. The CMP must block ALL non-essential cookies and scripts until explicit consent is given (opt-in, not opt-out).
GDPR Art. 6(1)(a) · GDPR Art. 7 · SK 18/2018 § 14
Privacy Policy PageZlyhalo
Prečo je to dôležité: A missing privacy policy is one of the most frequently cited GDPR violations. Every EU data protection authority considers it a basic requirement.
Ako opraviť: 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 PolicyUpozornenie
Prečo je to dôležité: The ePrivacy Directive requires transparent cookie disclosure. Vague statements like 'we use cookies for functionality' don't meet the specificity requirement.
Ako opraviť: 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 PageUpozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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).
Right to Erasure (Data Deletion)Upozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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.
Data Protection Officer ContactUpozornenie
Prečo je to dôležité: GDPR Article 37 requires a DPO for organizations processing personal data at scale. Even if not mandatory, having a designated privacy contact builds trust and is expected by regulators.
Ako opraviť: Add DPO contact details (or privacy contact if DPO not required) to your privacy policy and footer. Include: name/title, email (e.g., dpo@yourdomain.com), and postal address.
Withdrawal of Consent MechanismUpozornenie
Prečo je to dôležité: GDPR Article 7(3): 'It shall be as easy to withdraw as to give consent.' If users can subscribe in one click, unsubscribing must be equally simple. Missing this is a common regulatory finding.
Ako opraviť: Provide a clear way to withdraw consent: an 'unsubscribe' link in emails, a 'cookie settings' button in the footer, and a 'revoke consent' section in your privacy policy.
Cookie Lifetime ComplianceUpozornenie
1 cookie(s) with >1 year expiry
Prečo je to dôležité: French CNIL and other EU DPAs recommend a maximum 13-month cookie lifetime. Excessive cookie durations violate data minimization (GDPR Art. 5c).
Ako opraviť: Reduce cookie lifetimes to maximum 13 months (CNIL recommendation) or 6 months for marketing cookies. Session cookies should expire when the browser closes.
Tracking Scripts & ConsentPrešlo
No tracking scripts detected
Data Encryption (No Mixed Content)Prešlo
All resources loaded over HTTPS
Terms & Conditions PageInfo
No Terms & Conditions link found — for a non-commercial/informational site this is optional (no purchase or paid service to govern)
Prečo je to dôležité: 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.
Ako opraviť: 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.
Kategória 6 / 8 · datart.sk · Zulien Score

Vulnerability

83/100
Váha: 10% · 10 OK · 1 upozornení · 1 chýb · spolu 12
Payment Page SecurityZlyhalo
Payment page missing: No CSP, No X-Content-Type-Options
Prečo je to dôležité: Payment pages without proper security headers violate PCI DSS and make card data theft significantly easier. Payment processors can impose monthly fines for non-compliance.
Ako opraviť: CRITICAL: Your payment page is missing security headers: No CSP, No X-Content-Type-Options. PCI DSS Requirement 6.5 mandates protection against common vulnerabilities on pages handling card data.
Cross-Origin IsolationUpozornenie
Prečo je to dôležité: 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.
Ako opraviť: 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 DisclosurePrešlo
No generator tag — CMS identity hidden
Sensitive Files ExposedPrešlo
.env, .git, composer.json — all properly blocked
Install Script ExposedPrešlo
No /install/ or /setup/ paths accessible
Directory ListingPrešlo
Disabled — file structure hidden
Admin Panel at Default URLPrešlo
Not found at common paths (/admin, /wp-admin, /administrator, /backoffice)
Debug Mode / Error ExposurePrešlo
No debug indicators found in page output
SPF Record (Email Security)Prešlo
SPF configured: v=spf1 include:spf.hptronic.cz include:_emailing.heureka.cz include:spf.protecti
DMARC Policy (Email Auth)Prešlo
DMARC enforced: p=reject
DKIM Signing (Email Auth)Prešlo
DKIM configured (selectors: default, selector1, s1)
BIMI Brand IndicatorsPrešlo
BIMI configured — your logo appears in Gmail/Yahoo inboxes
Kategória 7 / 8 · datart.sk · Zulien Score

Accessibility

5/100
Váha: — · 0 OK · 1 upozornení · 3 chýb · spolu 7
Page LanguageZlyhalo
The <html> element has no lang attribute
Prečo je to dôležité: 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).
Ako opraviť: Add a lang attribute to <html>, e.g. <html lang="sk">, matching the primary language.
Heading StructureZlyhalo
The page has no <h1> heading
Prečo je to dôležité: Screen-reader users navigate by headings; a missing outline forces linear reading. EN 301 549 § 9.1.3.1 / 9.2.4.6 (WCAG 1.3.1 / 2.4.6).
Ako opraviť: Add exactly one <h1> describing the page, then use <h2>/<h3> in order without skipping levels.
Landmark RegionsZlyhalo
No <main> landmark region found
Prečo je to dôležité: Landmarks let assistive-tech users jump straight to the main content and skip repeated navigation. EN 301 549 § 9.1.3.1 (WCAG 1.3.1).
Ako opraviť: Wrap the primary content in <main> and use <nav>, <header>, <footer> for regions.
Skip LinkUpozornenie
No skip-to-content link detected
Prečo je to dôležité: 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).
Ako opraviť: Add a visually-hidden "Skip to content" link as the first focusable element, targeting <main id="main">.
Image Alt TextInfo
No <img> elements found on the homepage
Form LabelsInfo
No form inputs found on the homepage
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.
Kategória 8 / 8 · datart.sk · Zulien Score

Ďalšie kroky

  1. Začnite s chybami — každá červená položka má návod Ako opraviť. Zamerajte sa na kategórie Bezpečnosť a GDPR, ktoré majú zákonné dôsledky.
  2. Opakujte audit po oprave — spustite nový sken na score.zulien.sk a porovnajte skóre.
  3. Konzultujte zložitejšie problémy — pre hlboký audit alebo expertné posúdenie navštívte inger.sk.
  4. Sledujte súlad s NIS2 a GDPR — ak váš e-shop spadá pod NIS2 (obrat >10 mil. EUR alebo >50 zamestnancov), potrebujete formálny rámec súladu.

Online report

Plnú interaktívnu verziu s klikateľnými odkazmi a možnosťou opätovného skenu nájdete tu:

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

Upozornenie: Tento report je automaticky vygenerovaný nástrojom Zulien Score. Zistenia vychádzajú z verejne dostupných dát a technickej analýzy. Pre právne záväzné posúdenie (napríklad súladu s GDPR) odporúčame konzultáciu s DPO alebo advokátom špecializujúcim sa na ochranu osobných údajov. Zulien Score nie je licencovaná právna ani auditná spoločnosť.
Zulien Score · score.zulien.sk · by Zulien · Hosted at inger.sk