{ "data": { "slug": "3eeaf62c", "url": "https://nay.sk", "domain": "nay.sk", "overall_score": 43, "scores_json": { "seo": { "score": 15, "checks": [ { "i18n": { "key": "seo.meta-title.fail" }, "name": "Meta Title", "status": "fail", "fixLink": { "url": "https://zulien.sk", "label": "Fix with SEO module →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add a unique, descriptive tag. Include your primary keyword near the start, keep it under 60 characters.", "whyMatters": "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." }, { "i18n": { "key": "seo.meta-desc.fail-missing" }, "name": "Meta Description", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Write a compelling meta description (120-160 chars) with a call-to-action. Include your target keyword naturally.", "whyMatters": "Without a meta description, Google auto-generates one — often poorly. A custom description gives you control over the SERP snippet and improves click-through." }, { "i18n": { "key": "seo.h1.fail" }, "name": "H1 Heading", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add exactly one H1 tag containing your primary keyword. It should be the most prominent heading on the page.", "whyMatters": "The H1 is a primary content signal for search engines. Pages without an H1 rank lower for target keywords." }, { "i18n": { "key": "seo.h2.fail" }, "name": "Content Structure (H2 Headings)", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add H2 subheadings to structure your content. Each major section should have a descriptive H2.", "whyMatters": "Pages without heading structure are harder to scan and miss long-tail ranking opportunities." }, { "i18n": { "key": "seo.og.fail" }, "name": "Open Graph Tags", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add og:title, og:description, og:image (1200×630px), and og:type meta tags to every page.", "whyMatters": "Without OG tags, social platforms show auto-generated previews. Proper OG tags produce clean, clickable link cards." }, { "i18n": { "key": "seo.twitter.warning" }, "name": "Twitter/X Cards", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add <meta name='twitter:card' content='summary_large_image'>, twitter:title, and twitter:image tags.", "whyMatters": "Twitter Cards make your links stand out in X/Twitter feeds. Without them, shared links appear as plain text URLs." }, { "i18n": { "key": "seo.canonical.warning-generic" }, "name": "Canonical URL", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add a <link rel='canonical'> tag pointing to the preferred URL. For a single-page site this is a one-line addition in <head>.", "whyMatters": "Canonical tags prevent search engines from treating URL variants (with/without trailing slash, tracking params) as duplicate pages." }, { "i18n": { "key": "seo.jsonld.fail" }, "name": "Structured Data (JSON-LD)", "status": "fail", "fixLink": { "url": "https://zulien.sk", "label": "Add with Schema module →" }, "evidence": { "source": "schema" }, "howToFix": "Add JSON-LD structured data: Product (with price, availability, reviews), Organization, BreadcrumbList, and WebSite schemas.", "whyMatters": "Pages with structured data can earn rich snippets in Google — star ratings, prices, availability — which lift click-through." }, { "i18n": { "key": "seo.robots.warning" }, "name": "robots.txt", "status": "warning", "evidence": { "source": "file-probe" }, "howToFix": "Create a robots.txt file at your domain root. Include a Sitemap directive pointing to your XML sitemap.", "whyMatters": "robots.txt guides search engine crawling. Without it, crawlers may waste budget on irrelevant pages (admin, cart, checkout)." }, { "i18n": { "key": "seo.sitemap.fail" }, "name": "XML Sitemap", "status": "fail", "evidence": { "source": "file-probe" }, "howToFix": "Generate an XML sitemap at /sitemap.xml listing all important pages. Exclude noindex pages, filters, and duplicate URLs. Reference it in robots.txt.", "whyMatters": "Sitemaps help Google discover and index pages faster, especially for large stores with deep category structures." }, { "i18n": { "key": "seo.html-lang.warning" }, "name": "HTML Language Attribute", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add lang attribute to your <html> tag, e.g., <html lang='en'> or <html lang='de'>.", "whyMatters": "The lang attribute helps search engines serve your content to the right language audience and improves accessibility." }, { "i18n": { "key": "seo.img-alt.warning-none" }, "name": "Image Alt Attributes", "value": "No images found", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add relevant images with descriptive alt attributes to improve engagement and image search visibility.", "whyMatters": "Images drive a meaningful share of Google searches. Missing images means missing ranking opportunities." }, { "i18n": { "key": "seo.text-ratio.fail", "params": { "ratio": 1, "words": 13 } }, "name": "Text-to-HTML Ratio", "value": "1% — very thin content (13 words)", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Your page is almost entirely HTML/CSS/JS with very little actual content. Add substantial product descriptions, content blocks, and informational text.", "whyMatters": "Google's Helpful Content Update specifically targets thin content pages, which hurts your rankings." }, { "i18n": { "key": "seo.favicon.pass" }, "name": "Favicon", "value": "Favicon detected", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "seo.semantic.fail", "params": { "count": 0 } }, "name": "Semantic HTML Structure", "value": "0/6 semantic elements — poor structure", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "seo.content-depth.fail", "params": { "words": 13 } }, "name": "Content Depth", "value": "Only 13 words — very thin content", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "seo.internal-links.fail-none" }, "name": "Internal Linking", "value": "No internal links found", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add internal links to other pages on your site. Every page should link to related content, categories, and key landing pages.", "whyMatters": "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." }, { "i18n": { "key": "seo.a11y.fail" }, "name": "Accessibility Fundamentals", "value": "No accessibility signals found", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get Accessibility Audit →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." } ] }, "gdpr": { "score": 42, "checks": [ { "i18n": { "key": "gdpr.cmp.fail" }, "name": "Cookie Consent Banner (CMP)", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get GDPR Compliance →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "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).", "legalRefs": { "gdpr": [ "Art. 6(1)(a)", "Art. 7" ], "skLaw": [ "§ 14" ], "verified": [ { "title": "Zákonnosť spracúvania", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 6 — Zákonnosť spracúvania 1. Spracúvanie je zákonné iba vtedy a iba v tom rozsahu, keď je splnená aspoň jedna z týchto podmienok: Písmeno f) prvého pododseku sa nevzťahuje na spracúvanie vykonávané orgánmi verejnej moci pri výkone i", "citation": "čl. 6 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Podmienky vyjadrenia súhlasu", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 7 — Podmienky vyjadrenia súhlasu 1. Ak je spracúvanie založené na súhlase, prevádzkovateľ musí vedieť preukázať, že dotknutá osoba vyjadrila súhlas so spracúvaním svojich osobných údajov. 2. Ak dá dotknutá osoba súhlas v rámci písom", "citation": "čl. 7 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Podmienky poskytnutia súhlasu so spracúvaním osobných údajov", "excerpt": "§ 14 Podmienky poskytnutia súhlasu so spracúvaním osobných údajov (1) Ak je spracúvanie osobných údajov založené na súhlase dotknutej osoby, prevádzkovateľ je povinný kedykoľvek vedieť preukázať, že dotknutá osoba poskytla súhlas so spracúv", "citation": "§14 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] }, "whyMatters": "Since 2024, EU regulators actively enforce cookie consent. A non-compliant cookie banner is one of the most frequently fined GDPR offences." }, { "i18n": { "key": "gdpr.tracking.pass-none" }, "name": "Tracking Scripts & Consent", "value": "No tracking scripts detected", "status": "pass", "evidence": { "source": "HTML-heuristic" }, "legalRefs": { "gdpr": [ "Art. 6(1)(a)", "Art. 7", "EDPB Opinion 5/2019" ], "skLaw": [ "§ 14" ], "verified": [ { "title": "Zákonnosť spracúvania", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 6 — Zákonnosť spracúvania 1. Spracúvanie je zákonné iba vtedy a iba v tom rozsahu, keď je splnená aspoň jedna z týchto podmienok: Písmeno f) prvého pododseku sa nevzťahuje na spracúvanie vykonávané orgánmi verejnej moci pri výkone i", "citation": "čl. 6 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Podmienky vyjadrenia súhlasu", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 7 — Podmienky vyjadrenia súhlasu 1. Ak je spracúvanie založené na súhlase, prevádzkovateľ musí vedieť preukázať, že dotknutá osoba vyjadrila súhlas so spracúvaním svojich osobných údajov. 2. Ak dá dotknutá osoba súhlas v rámci písom", "citation": "čl. 7 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Podmienky poskytnutia súhlasu so spracúvaním osobných údajov", "excerpt": "§ 14 Podmienky poskytnutia súhlasu so spracúvaním osobných údajov (1) Ak je spracúvanie osobných údajov založené na súhlase dotknutej osoby, prevádzkovateľ je povinný kedykoľvek vedieť preukázať, že dotknutá osoba poskytla súhlas so spracúv", "citation": "§14 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] } }, { "i18n": { "key": "gdpr.privacy-policy.fail" }, "name": "Privacy Policy Page", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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).", "legalRefs": { "gdpr": [ "Art. 12", "Art. 13", "Art. 14" ], "skLaw": [ "§ 19", "§ 20" ], "verified": [ { "title": "Transparentnosť informácií, oznámenia a postupy výkonu práv dotknutej osoby", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 12 — Transparentnosť informácií, oznámenia a postupy výkonu práv dotknutej osoby 3. Prevádzkovateľ poskytne dotknutej osobe informácie o opatreniach, ktoré sa prijali na základe žiadosti podľa článkov 15 až 22, bez zbytočného odklad", "citation": "čl. 12 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Informácie, ktoré sa majú poskytovať pri získavaní osobných údajov od dotknutej osoby", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 13 — Informácie, ktoré sa majú poskytovať pri získavaní osobných údajov od dotknutej osoby 2. Okrem informácií, ktoré sa uvádzajú v odseku 1, prevádzkovateľ poskytne dotknutej osobe pri získavaní osobných údajov tieto ďalšie informá", "citation": "čl. 13 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Informácie, ktoré sa majú poskytnúť, ak osobné údaje neboli získané od dotknutej osoby", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 14 — Informácie, ktoré sa majú poskytnúť, ak osobné údaje neboli získané od dotknutej osoby 2. Okrem informácií uvedených v odseku 1 prevádzkovateľ poskytne dotknutej osobe tieto ďalšie informácie potrebné na zabezpečenie spravodliv", "citation": "čl. 14 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Poskytované informácie, ak osobné údaje sú získané od dotknutej osoby", "excerpt": "§ 19 Poskytované informácie, ak osobné údaje sú získané od dotknutej osoby (4) Odseky 1 až 3 sa neuplatňujú v rozsahu, v akom boli informácie dotknutej osobe poskytnuté pred spracúvaním osobných údajov.", "citation": "§19 ods. 4 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" }, { "title": "Poskytované informácie, ak osobné údaje nie sú získané od dotknutej osoby", "excerpt": "§ 20 Poskytované informácie, ak osobné údaje nie sú získané od dotknutej osoby (5) d) ak osobné údaje musia zostať dôverné na základe povinnosti mlčanlivosti podľa osobitného predpisu. 15 )", "citation": "§20 ods. 5 písm. d) zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] }, "whyMatters": "A missing privacy policy is one of the most frequently cited GDPR violations. Every EU data protection authority considers it a basic requirement." }, { "i18n": { "key": "gdpr.cookie-policy.warning" }, "name": "Cookie Policy", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Create a separate cookie policy page listing every cookie by: name, provider, purpose, category (necessary/analytics/marketing), and expiration. Most CMPs auto-generate this.", "legalRefs": { "gdpr": [ "Art. 12", "Art. 13(1)(c)-(e)" ], "skLaw": [ "§ 19" ], "verified": [ { "title": "Transparentnosť informácií, oznámenia a postupy výkonu práv dotknutej osoby", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 12 — Transparentnosť informácií, oznámenia a postupy výkonu práv dotknutej osoby 3. Prevádzkovateľ poskytne dotknutej osobe informácie o opatreniach, ktoré sa prijali na základe žiadosti podľa článkov 15 až 22, bez zbytočného odklad", "citation": "čl. 12 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Informácie, ktoré sa majú poskytovať pri získavaní osobných údajov od dotknutej osoby", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 13 — Informácie, ktoré sa majú poskytovať pri získavaní osobných údajov od dotknutej osoby 2. Okrem informácií, ktoré sa uvádzajú v odseku 1, prevádzkovateľ poskytne dotknutej osobe pri získavaní osobných údajov tieto ďalšie informá", "citation": "čl. 13 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Poskytované informácie, ak osobné údaje sú získané od dotknutej osoby", "excerpt": "§ 19 Poskytované informácie, ak osobné údaje sú získané od dotknutej osoby (4) Odseky 1 až 3 sa neuplatňujú v rozsahu, v akom boli informácie dotknutej osobe poskytnuté pred spracúvaním osobných údajov.", "citation": "§19 ods. 4 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] }, "whyMatters": "The ePrivacy Directive requires transparent cookie disclosure. Vague statements like 'we use cookies for functionality' don't meet the specificity requirement." }, { "i18n": { "key": "gdpr.imprint.warning" }, "name": "Legal Contact / Imprint Page", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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).", "whyMatters": "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." }, { "i18n": { "key": "gdpr.terms.info-noncommercial" }, "name": "Terms & Conditions Page", "value": "No Terms & Conditions link found — for a non-commercial/informational site this is optional (no purchase or paid service to govern)", "status": "info", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "confidence": "low", "whyMatters": "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." }, { "i18n": { "key": "gdpr.mixed-content.pass" }, "name": "Data Encryption (No Mixed Content)", "value": "All resources loaded over HTTPS", "status": "pass", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "gdpr.erasure.warning" }, "name": "Right to Erasure (Data Deletion)", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "legalRefs": { "gdpr": [ "Art. 17" ], "skLaw": [ "§ 23" ], "verified": [ { "title": "Právo na vymazanie (právo „na zabudnutie“)", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 17 — Právo na vymazanie (právo „na zabudnutie“) 1. Dotknutá osoba má tiež právo dosiahnuť u prevádzkovateľa bez zbytočného odkladu vymazanie osobných údajov, ktoré sa jej týkajú, a prevádzkovateľ je povinný bez zbytočného odkladu vy", "citation": "čl. 17 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Právo na výmaz osobných údajov", "excerpt": "§ 23 Právo na výmaz osobných údajov (1) Dotknutá osoba má právo na to, aby prevádzkovateľ bez zbytočného odkladu vymazal osobné údaje, ktoré sa jej týkajú.", "citation": "§23 ods. 1 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] }, "whyMatters": "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." }, { "i18n": { "key": "gdpr.dpo.warning" }, "name": "Data Protection Officer Contact", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "gdpr.withdrawal.warning" }, "name": "Withdrawal of Consent Mechanism", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "legalRefs": { "gdpr": [ "Art. 7(3)" ], "skLaw": [ "§ 14(4)" ], "verified": [ { "title": "Podmienky vyjadrenia súhlasu", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 7 — Podmienky vyjadrenia súhlasu 1. Ak je spracúvanie založené na súhlase, prevádzkovateľ musí vedieť preukázať, že dotknutá osoba vyjadrila súhlas so spracúvaním svojich osobných údajov. 2. Ak dá dotknutá osoba súhlas v rámci písom", "citation": "čl. 7 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Podmienky poskytnutia súhlasu so spracúvaním osobných údajov", "excerpt": "§ 14 Podmienky poskytnutia súhlasu so spracúvaním osobných údajov (1) Ak je spracúvanie osobných údajov založené na súhlase dotknutej osoby, prevádzkovateľ je povinný kedykoľvek vedieť preukázať, že dotknutá osoba poskytla súhlas so spracúv", "citation": "§14 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] }, "whyMatters": "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." }, { "i18n": { "key": "gdpr.cookie-lifetime.warning", "params": { "count": 1 } }, "name": "Cookie Lifetime Compliance", "value": "1 cookie(s) with >1 year expiry", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "Reduce cookie lifetimes to maximum 13 months (CNIL recommendation) or 6 months for marketing cookies. Session cookies should expire when the browser closes.", "legalRefs": { "gdpr": [ "Art. 5(1)(c)", "Art. 5(1)(e)" ], "skLaw": [ "§ 8", "§ 10" ], "verified": [ { "title": "Zásady spracúvania osobných údajov", "source": "Zdroj: EUR-Lex (eur-lex.europa.eu), © Európska únia, 1998–2026. Autentické je iba znenie publikované v elektronickom Úradnom vestníku Európskej únie.", "excerpt": "Article 5 — Zásady spracúvania osobných údajov 1. Osobné údaje musia byť: (a) spracúvané zákonným spôsobom, spravodlivo a transparentne vo vzťahu k dotknutej osobe („zákonnosť, spravodlivosť a transparentnosť“); (b) získavané na konkrétne u", "citation": "čl. 5 nariadenia (EÚ) 2016/679", "jurisdiction": "eu" }, { "title": "Zásada minimalizácie osobných údajov", "excerpt": "§ 8 Zásada minimalizácie osobných údajov Spracúvané osobné údaje musia byť primerané, relevantné a obmedzené na nevyhnutný rozsah daný účelom, na ktorý sa spracúvajú.", "citation": "§8 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" }, { "title": "Zásada minimalizácie uchovávania", "excerpt": "§ 10 Zásada minimalizácie uchovávania Osobné údaje musia byť uchovávané vo forme, ktorá umožňuje identifikáciu dotknutej osoby najneskôr dovtedy, kým je to potrebné na účel, na ktorý sa osobné údaje spracúvajú; osobné údaje sa môžu uchováva", "citation": "§10 zákona č. 18/2018 Z.z.", "jurisdiction": "sk" } ] }, "whyMatters": "French CNIL and other EU DPAs recommend a maximum 13-month cookie lifetime. Excessive cookie durations violate data minimization (GDPR Art. 5c)." } ] }, "nis2": { "score": -1, "checks": [ { "i18n": { "key": "nis2.scope.none" }, "name": "NIS2 Compliance", "value": "Not in scope — your business is below NIS2 thresholds (Annex I/II sector + 50+ employees / €10M+ turnover).", "status": "info", "howToFix": "", "whyMatters": "" } ] }, "mobile": { "score": 39, "checks": [ { "i18n": { "key": "mob.viewport.fail" }, "name": "Viewport Configuration", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add <meta name='viewport' content='width=device-width, initial-scale=1'> to your <head>. This is the absolute minimum for mobile compatibility.", "whyMatters": "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." }, { "i18n": { "key": "mob.perf.fail", "params": { "score": 40 } }, "name": "Mobile Performance Score", "value": "40/100 — critically slow", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get Mobile Optimization →" }, "evidence": { "source": "PSI-lab" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "mob.taptarget.warning", "params": { "detail": "Some tappable targets are too small or too close together (Lighthouse tap-targets audit)" } }, "name": "Touch Target Size", "value": "Some tappable targets are too small or too close together (Lighthouse tap-targets audit)", "status": "warning", "evidence": { "source": "PSI-lab", "measured": "Some tappable targets are too small or too close together (Lighthouse tap-targets audit)" }, "howToFix": "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.", "whyMatters": "Small tap targets cause mis-taps on mobile. In e-commerce, a mis-tap on 'Remove from cart' instead of 'Checkout' directly loses revenue." }, { "i18n": { "key": "mob.fontsize.warning", "params": { "detail": "Some text renders below the 12px legibility threshold (Lighthouse font-size audit)" } }, "name": "Font Size Readability", "value": "Some text renders below the 12px legibility threshold (Lighthouse font-size audit)", "status": "warning", "evidence": { "source": "PSI-lab", "measured": "Some text renders below the 12px legibility threshold (Lighthouse font-size audit)" }, "howToFix": "Google's font-size audit flags text under 12px. Find the small text (often footer fine-print, captions, or cookie notices) and raise it; aim for a 16px+ body base with relative units (rem/em) so all text scales legibly on mobile.", "whyMatters": "Text below the legibility threshold forces mobile users to pinch-zoom. This measures the actual rendered page (Lighthouse), so it catches sub-12px nodes even when the base font looks fine." }, { "i18n": { "key": "mob.contentwidth.pass" }, "name": "Content Fits Viewport", "value": "No horizontal scrolling needed", "status": "pass", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "mob.responsive.warning" }, "name": "Responsive Design Techniques", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Implement responsive CSS with @media queries for key breakpoints: 480px (small mobile), 768px (tablet), 1024px (laptop). Use Flexbox and CSS Grid for fluid layouts.", "whyMatters": "Non-responsive sites are automatically penalized by Google in mobile search results. With mobile-first indexing, this is a critical ranking factor." }, { "i18n": { "key": "mob.themecolor.warning" }, "name": "Theme Color", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "Theme-color creates a polished, branded mobile experience. It makes your site look native and professional." }, { "i18n": { "key": "mob.nav.warning" }, "name": "Mobile Navigation (Semantic)", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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').", "whyMatters": "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." } ] }, "company": { "nis2": { "annex": null, "sector": null, "category": "none", "in_scope": false, "priority_tier": null, "priority_score": null }, "financials": { "year": 2025, "equity": 34877806, "profit": -1301335, "turnover": 410806866 }, "percentile": { "metrics": { "equity": 40, "turnover": 32, "net_profit": 0, "credit_limit": 0, "credit_score": 18, "total_assets": 40, "debt_to_equity": 6, "employee_count": 100 }, "nace_section": "G", "peer_group_size": 116447 }, "in_insolvency": false, "credit_grade_full": "C" }, "modules": [], "security": { "score": 70, "checks": [ { "i18n": { "key": "sec.ssl.pass" }, "name": "SSL/TLS Certificate", "value": "Valid HTTPS connection established", "status": "pass", "evidence": { "source": "SSL" } }, { "i18n": { "key": "sec.dnssec.warning" }, "name": "DNSSEC", "value": "No DNSKEY records — zone is unsigned", "status": "warning", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "DNSSEC setup help →" }, "evidence": { "source": "DNS" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "sec.caa.warning" }, "name": "CAA DNS Record", "value": "No CAA records — any CA can issue certificates for this domain", "status": "warning", "evidence": { "source": "DNS" }, "howToFix": "Publish CAA TXT records pinning your CA. For Let's Encrypt: `0 issue \"letsencrypt.org\"`. For multiple CAs add additional `0 issue \"...\"` records. Add `0 iodef \"mailto:security@yourdomain.tld\"` for misissuance reports.", "whyMatters": "CAA records limit which Certificate Authorities can issue certificates for your domain. Without CAA, a compromised or rogue CA can issue valid certs that browsers will trust — a documented breach pattern (DigiNotar 2011, Symantec 2017)." }, { "i18n": { "key": "sec.https-redirect.pass" }, "name": "HTTP → HTTPS Redirect", "value": "HTTP properly redirects to HTTPS", "status": "pass", "evidence": { "source": "HTTP-header" } }, { "i18n": { "key": "sec.hsts.pass", "params": { "detail": "max-age=31536000, preload, includeSubDomains" } }, "name": "HSTS (Strict-Transport-Security)", "value": "max-age=31536000, preload, includeSubDomains", "status": "pass", "evidence": { "source": "HTTP-header" } }, { "i18n": { "key": "sec.csp.fail" }, "name": "Content-Security-Policy (CSP)", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get Security Hardening →" }, "evidence": { "source": "HTTP-header" }, "howToFix": "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.", "whyMatters": "CSP is a strong defense against XSS attacks. Without it, any injected script runs with full privileges. CSP blocks inline script injection." }, { "i18n": { "key": "sec.clickjacking.pass", "params": { "detail": "SAMEORIGIN" } }, "name": "Clickjacking Protection", "value": "X-Frame-Options: SAMEORIGIN", "status": "pass", "evidence": { "source": "HTTP-header" } }, { "i18n": { "key": "sec.x-content-type.warning" }, "name": "X-Content-Type-Options", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "Add header: X-Content-Type-Options: nosniff", "whyMatters": "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." }, { "i18n": { "key": "sec.referrer-policy.warning" }, "name": "Referrer-Policy", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "Add header: Referrer-Policy: strict-origin-when-cross-origin — this is the best balance between functionality and privacy.", "whyMatters": "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." }, { "i18n": { "key": "sec.permissions-policy.pass", "params": { "detail": "unload=()" } }, "name": "Permissions-Policy", "value": "unload=()", "status": "pass", "evidence": { "source": "HTTP-header" } }, { "i18n": { "key": "sec.cookie-flags.warning", "params": { "count": 7, "missing": "4 missing Secure, 4 missing HttpOnly, 4 missing SameSite" } }, "name": "Cookie Security Flags", "value": "7 cookie(s): 4 missing Secure, 4 missing HttpOnly, 4 missing SameSite", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "Set all cookies with: Secure (HTTPS only), HttpOnly (no JS access), SameSite=Lax or Strict (CSRF protection). Session cookies MUST have all three.", "whyMatters": "Missing Secure flag = cookies sent over HTTP (stealable on WiFi). Missing HttpOnly = cookies readable by XSS. Missing SameSite = vulnerable to CSRF attacks." }, { "i18n": { "key": "sec.tech-disclosure.pass-hidden" }, "name": "Technology Disclosure", "value": "Server identity hidden", "status": "pass", "evidence": { "source": "HTTP-header" } }, { "i18n": { "key": "sec.sri.pass-none" }, "name": "Subresource Integrity (SRI)", "value": "No SRI-eligible third-party scripts loaded", "status": "pass", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "sec.security-txt.warning" }, "name": "security.txt (RFC 9116)", "status": "warning", "evidence": { "source": "file-probe" }, "howToFix": "Create /.well-known/security.txt with Contact, Expires, and Preferred-Languages fields. See securitytxt.org for the generator.", "whyMatters": "security.txt lets ethical hackers report vulnerabilities responsibly. Without it, they may disclose publicly or not report at all." }, { "i18n": { "key": "sec.cdn.warning" }, "name": "CDN / WAF Protection", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "Add a CDN/WAF like Cloudflare (free tier), Sucuri, or Fastly. They provide DDoS protection, bot filtering, and SSL management.", "whyMatters": "Without a CDN/WAF, your origin server is directly exposed to DDoS attacks, bot traffic, and brute-force attempts." } ] }, "tech_stack": [], "performance": { "score": 57, "checks": [ { "i18n": { "key": "perf.ttfb.fail", "params": { "ms": 897 } }, "name": "Server Response Time (TTFB)", "value": "897ms (optimal: <200ms)", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get Performance Optimization →" }, "evidence": { "source": "PSI-lab" }, "howToFix": "Your server is critically slow. Enable full-page caching (Varnish/Redis), use a CDN (Cloudflare/Fastly), upgrade hosting, or optimize database queries.", "whyMatters": "TTFB over 600ms makes it nearly impossible to pass Core Web Vitals. Every page load starts with this delay before anything else can happen." }, { "i18n": { "key": "perf.fcp.pass", "params": { "s": "0.91" } }, "name": "First Contentful Paint (FCP)", "value": "0.91s", "status": "pass", "evidence": { "source": "PSI-lab" } }, { "i18n": { "key": "perf.lcp.pass", "params": { "s": "0.99" } }, "name": "Largest Contentful Paint (LCP)", "value": "0.99s — Core Web Vital ✓", "status": "pass", "evidence": { "source": "PSI-lab" } }, { "i18n": { "key": "perf.tbt.fail", "params": { "ms": 819 } }, "name": "Total Blocking Time (TBT)", "value": "819ms (good: <200ms)", "status": "fail", "evidence": { "source": "PSI-lab" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "perf.cls.pass", "params": { "cls": "0.002" } }, "name": "Cumulative Layout Shift (CLS)", "value": "0.002 — Core Web Vital ✓", "status": "pass", "evidence": { "source": "PSI-lab" } }, { "i18n": { "key": "perf.speed-index.warning", "params": { "s": "5.45" } }, "name": "Speed Index", "value": "5.45s (good: <3.4s)", "status": "warning", "evidence": { "source": "PSI-lab" }, "howToFix": "Speed Index measures visual completeness over time. Improve it by: prioritizing above-fold content, preloading critical resources, and minimizing render-blocking assets.", "whyMatters": "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." }, { "i18n": { "key": "perf.page-weight.fail", "params": { "mb": "3.6", "requests": 136 } }, "name": "Total Page Weight", "value": "3.6 MB, 136 requests — too heavy!", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get Performance Optimization →" }, "evidence": { "source": "PSI-lab" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "perf.render-blocking.info" }, "name": "Render-blocking Resources", "value": "Not measured — PageSpeed did not return the render-blocking audit for this URL", "status": "info", "evidence": { "source": "PSI-lab" }, "howToFix": "Re-run the scan, or test directly at PageSpeed Insights. This metric needs a successful Lighthouse lab run." }, { "i18n": { "key": "perf.unused-code.fail", "params": { "kb": 745 } }, "name": "Unused Code (CSS + JS)", "value": "745 KB wasted on unused code!", "status": "fail", "evidence": { "source": "PSI-lab" }, "howToFix": "You're loading 745 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.", "whyMatters": "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." }, { "i18n": { "key": "perf.text-compression.pass" }, "name": "Text Compression (gzip/brotli)", "value": "All text resources properly compressed", "status": "pass", "evidence": { "source": "HTTP-header" } }, { "i18n": { "key": "perf.resource-hints.warning" }, "name": "Resource Hints (Preload/Preconnect)", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "perf.cache-control.warning", "params": { "header": "no-store, no-cache, must-revalidate" } }, "name": "Cache-Control Strategy", "value": "no-store, no-cache, must-revalidate", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "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.", "whyMatters": "no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time." }, { "i18n": { "key": "perf.script-strategy.fail", "params": { "rate": 0, "total": 2, "blocking": 2 } }, "name": "Script Loading Strategy", "value": "Only 0% of 2 scripts optimized — most are render-blocking", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get Performance Optimization →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "2 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain." }, { "i18n": { "key": "perf.css-count.pass", "params": { "count": 1 } }, "name": "CSS File Count", "value": "1 CSS file(s) — well consolidated", "status": "pass", "evidence": { "source": "HTML-heuristic" } } ] }, "ai_readiness": { "score": 23, "checks": [ { "i18n": { "key": "air.bot-access.pass", "params": { "detail": "No AI bot restrictions (allowed by default)" } }, "name": "AI Bot Access Policy", "value": "No AI bot restrictions (allowed by default)", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "air.llms-txt.fail" }, "name": "llms.txt (AI Site Descriptor)", "value": "Not present — not required for AI visibility", "status": "info", "fixLink": { "url": "https://llmstxt.org", "label": "About llms.txt →" }, "evidence": { "source": "file-probe" }, "howToFix": "Optional: /llms.txt (a Markdown site descriptor per llmstxt.org) is future-proofing, mainly consumed by coding/IDE agents. It does NOT affect whether ChatGPT/Perplexity/Gemini cite your store. Prioritize AI-crawler access, server-rendered content, statistics and cited sources instead.", "whyMatters": "No answer engine consumes llms.txt for AI-search citation today (2026) — adoption is ~8.7% and Google declined to support it. It's optional future-proofing, mainly read by coding/IDE agents. Prioritize AI-crawler access, server-rendered content, statistics and cited sources instead. See /ai-readiness-methodology.md." }, { "i18n": { "key": "air.llms-full.warning" }, "name": "llms-full.txt (Complete AI Content)", "value": "Not present — not required for AI visibility", "status": "info", "evidence": { "source": "file-probe" }, "whyMatters": "No answer engine consumes llms.txt for AI-search citation today (2026) — adoption is ~8.7% and Google declined to support it. It's optional future-proofing, mainly read by coding/IDE agents. Prioritize AI-crawler access, server-rendered content, statistics and cited sources instead. See /ai-readiness-methodology.md." }, { "i18n": { "key": "air.content-access.fail", "params": { "words": 13 } }, "name": "Content Accessibility for AI", "value": "Only 13 words visible in HTML — content may be JS-dependent", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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).", "whyMatters": "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." }, { "i18n": { "key": "air.schema-foundation.fail" }, "name": "Structured Data Foundation", "status": "fail", "fixLink": { "url": "https://zulien.sk", "label": "Add structured data →" }, "evidence": { "source": "schema" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.org-schema.fail" }, "name": "Organization Schema + Entity Linking", "status": "fail", "evidence": { "source": "schema" }, "howToFix": "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).", "whyMatters": "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." }, { "i18n": { "key": "air.faq-schema.warning" }, "name": "FAQ Schema (Direct AI Answers)", "status": "warning", "evidence": { "source": "schema" }, "howToFix": "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).", "whyMatters": "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." }, { "i18n": { "key": "air.content-depth.fail", "params": { "words": 13 } }, "name": "Content Depth for AI", "value": "Only 13 words — too thin for AI citation", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Your page has critically low content. Add: comprehensive product descriptions, feature lists, FAQs, buying guides, comparison tables, and trust signals (reviews, certifications, guarantees).", "whyMatters": "Pages with very little content are nearly invisible to AI search. Without substance, AI has nothing to quote, summarize, or recommend." }, { "i18n": { "key": "air.answer-first.fail" }, "name": "Answer-First Content Format", "value": "No meaningful opening content for AI to extract", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.headings.fail", "params": { "h1": 0, "h2": 0, "h3": 0 } }, "name": "Heading Hierarchy for AI", "value": "0 H1, 0 H2, 0 H3 — poor structure", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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).", "whyMatters": "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." }, { "i18n": { "key": "air.semantic-html.fail" }, "name": "Semantic HTML Structure", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.structured-content.warning-none" }, "name": "Structured Content (Lists & Tables)", "value": "No structured content elements found", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.freshness.fail" }, "name": "Content Freshness Signals", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.entity-clarity.fail" }, "name": "Entity Clarity & Brand Signals", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "AI assistants must be confident about entity identity before making recommendations. Without clear brand signals, AI defaults to better-known competitors." }, { "i18n": { "key": "air.eeat.warning-noarticle" }, "name": "Author Expertise Signals (E-E-A-T)", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.extractable.fail" }, "name": "Extractable Answer Blocks", "value": "Too few content paragraphs for AI to extract", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "AI assistants extract individual paragraphs as citations. Without clear, self-contained content blocks, your page can't be quoted in AI-generated answers." }, { "i18n": { "key": "air.statistics.warning-none" }, "name": "Statistics & Data Presence", "value": "No statistical data found in content", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "Content without data is harder to cite. Perplexity and ChatGPT specifically seek pages with quantified claims and verifiable statistics." }, { "i18n": { "key": "air.qa-headings.warning-none" }, "name": "Q&A Format Headings", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.canonical.fail" }, "name": "Canonical Tag for AI Deduplication", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.kg-readiness.fail" }, "name": "Knowledge Graph Readiness", "status": "fail", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.expert-quotes.warning-none" }, "name": "Expert Quotations & Citations", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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).", "whyMatters": "Content without citations or expert quotes appears unverified to AI. AI assistants prefer content backed by named sources, data references, and expert opinions." }, { "i18n": { "key": "air.ai-txt.warning" }, "name": "ai.txt (AI Permissions)", "value": "Not present — optional; AI-bot permissions are enforced via robots.txt, not ai.txt", "status": "info", "evidence": { "source": "file-probe" }, "whyMatters": "ai.txt is an emerging fine-grained AI-permissions proposal not yet honored by the major engines. The robots.txt AI-bot rules are the signal that actually gates crawler access." }, { "i18n": { "key": "air.webmcp.warning" }, "name": "WebMCP Agentic Readiness", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "whyMatters": "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." }, { "i18n": { "key": "air.boilerplate.warning-nomain" }, "name": "Content-to-Boilerplate Ratio", "value": "No <main> or <article> elements — AI can't isolate content from boilerplate", "status": "warning", "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add <main> around your primary content and <article> around self-contained content blocks. This creates clear boundaries for AI content extraction.", "whyMatters": "Without semantic containers, AI crawlers must guess where content starts and navigation ends. This leads to poor content extraction and fewer citations." }, { "i18n": { "key": "air.social-proof.info-noncommercial", "params": { "detected": "None detected." } }, "name": "Social Proof (Testimonials / Case Studies)", "value": "None detected. For a non-commercial/informational site, testimonials and case studies are optional", "status": "info", "evidence": { "source": "HTML-heuristic" }, "howToFix": "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.", "confidence": "low", "whyMatters": "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." }, { "name": "Agent-Commerce Readiness", "value": "33/100 — pre AI agentov nedostupné (Prístup 50 · Porozumenie 0 · Transakcia 50)", "status": "info", "whyMatters": "Č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\")." }, { "name": "Agent: Prístup — dostane sa agent dnu", "value": "50/100 (2 signály/-ov)", "status": "info" }, { "name": "Agent: Porozumenie — rozumie produktom", "value": "0/100 (2 signály/-ov)", "status": "info" }, { "name": "Agent: Transakcia — vie konať (kôš/podmienky)", "value": "50/100 (1 signál)", "status": "info" } ] }, "phaseTimings": { "tail": 176, "total": 4106, "phase1": 1956, "preflight": 1749, "phase1.dns": 1937, "phase1.html": 900, "phase1.files": 1953, "phase1.zbozi": 891, "phase1.headers": 895, "phase1.heureka": 894, "phase1.merchant": 889 }, "accessibility": { "score": 5, "checks": [ { "i18n": { "key": "a11y.lang.fail" }, "name": "Page Language", "value": "The <html> element has no lang attribute", "status": "fail", "weight": 2, "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Accessibility audit — Inger →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add a lang attribute to <html>, e.g. <html lang=\"sk\"> — matching the page's primary language.", "whyMatters": "Screen readers use the lang attribute to pick the right pronunciation engine. Without it, Slovak content may be read with English phonetics — unintelligible. Required by EN 301 549 § 9.3.1.1 (WCAG 3.1.1)." }, { "i18n": { "key": "a11y.alt.none" }, "name": "Image Alt Text", "value": "No <img> elements found on the homepage", "status": "info", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "a11y.forms.none" }, "name": "Form Labels", "value": "No form inputs found on the homepage", "status": "info", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "a11y.headings.no-h1" }, "name": "Heading Structure", "value": "The page has no <h1> heading", "status": "fail", "weight": 2, "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Accessibility audit — Inger →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add exactly one <h1> describing the page, then use <h2>/<h3> in order without skipping levels.", "whyMatters": "Screen-reader users navigate by headings; a missing or broken heading outline forces them to read linearly. EN 301 549 § 9.1.3.1 / 9.2.4.6 (WCAG 1.3.1 / 2.4.6)." }, { "i18n": { "key": "a11y.landmarks.no-main" }, "name": "Landmark Regions", "value": "No <main> landmark region found", "status": "fail", "weight": 1, "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Accessibility audit — Inger →" }, "evidence": { "source": "HTML-heuristic" }, "howToFix": "Wrap the primary content in <main> and use <nav>, <header>, <footer> for the page regions.", "whyMatters": "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)." }, { "i18n": { "key": "a11y.skiplink.missing" }, "name": "Skip Link", "value": "No skip-to-content link detected", "status": "warning", "weight": 1, "evidence": { "source": "HTML-heuristic" }, "howToFix": "Add a visually-hidden \"Skip to content\" link as the first focusable element, targeting <main id=\"main\">.", "confidence": "low", "whyMatters": "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)." }, { "i18n": { "key": "a11y.legal-basis" }, "name": "EAA Legal Basis", "value": "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.", "status": "info", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Accessibility audit — Inger →" }, "howToFix": "", "isUpsell": true, "whyMatters": "" } ] }, "vulnerability": { "score": 82, "checks": [ { "i18n": { "key": "vuln.cms-version.pass" }, "name": "CMS Version Disclosure", "value": "No generator tag — CMS identity hidden", "status": "pass", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "vuln.sensitive-files.pass" }, "name": "Sensitive Files Exposed", "value": ".env, .git, composer.json — all properly blocked", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "vuln.install-script.pass" }, "name": "Install Script Exposed", "value": "No /install/ or /setup/ paths accessible", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "vuln.directory-listing.pass" }, "name": "Directory Listing", "value": "Disabled — file structure hidden", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "vuln.admin-url.pass" }, "name": "Admin Panel at Default URL", "value": "Not found at common paths (/admin, /wp-admin, /administrator, /backoffice)", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "vuln.debug-mode.pass" }, "name": "Debug Mode / Error Exposure", "value": "No debug indicators found in page output", "status": "pass", "evidence": { "source": "HTML-heuristic" } }, { "i18n": { "key": "vuln.spf.pass", "params": { "record": "v=spf1 ip4:86.110.232.8/29 ip4:82.99.177.0/25 include:spf.protection.outlook.co" } }, "name": "SPF Record (Email Security)", "value": "SPF configured: v=spf1 ip4:86.110.232.8/29 ip4:82.99.177.0/25 include:spf.protection.outlook.co", "status": "pass", "evidence": { "source": "DNS" } }, { "i18n": { "key": "vuln.dmarc.pass", "params": { "policy": "reject" } }, "name": "DMARC Policy (Email Auth)", "value": "DMARC enforced: p=reject", "status": "pass", "evidence": { "source": "DNS" } }, { "i18n": { "key": "vuln.dkim.pass", "params": { "selectors": "selector1, selector2" } }, "name": "DKIM Signing (Email Auth)", "value": "DKIM configured (selectors: selector1, selector2)", "status": "pass", "evidence": { "source": "file-probe" } }, { "i18n": { "key": "vuln.bimi.info" }, "name": "BIMI Brand Indicators", "status": "info", "evidence": { "source": "file-probe" }, "howToFix": "Once DMARC is set to p=quarantine or p=reject with 100% enforcement, publish a BIMI record: v=BIMI1; l=https://yourdomain.com/logo.svg — adds your brand logo to recipient inboxes in Gmail and Yahoo.", "whyMatters": "BIMI requires a VMC (Verified Mark Certificate) but adds your brand logo to recipient inboxes as a trust signal. Optional but high-impact for brand-focused shops." }, { "i18n": { "key": "vuln.cross-origin.warning" }, "name": "Cross-Origin Isolation", "status": "warning", "evidence": { "source": "HTTP-header" }, "howToFix": "Add Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Resource-Policy: same-origin headers. These protect against Spectre-type side-channel attacks.", "whyMatters": "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." }, { "i18n": { "key": "vuln.payment-page.fail", "params": { "issues": "No CSP, No X-Content-Type-Options" } }, "name": "Payment Page Security", "value": "Payment page missing: No CSP, No X-Content-Type-Options", "status": "fail", "fixLink": { "url": "https://www.inger.sk/#contact", "label": "Get PCI Compliance Audit →" }, "evidence": { "source": "file-probe" }, "howToFix": "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.", "whyMatters": "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." } ] }, "executive_summary": { "en": "Your site needs urgent attention – customers can't find you. Add meta titles and descriptions to every page immediately so Google can index you properly. Your security setup is solid, which is good.", "sk": "Váš web potrebuje rýchlu obnovu – zákazníci vás jednoducho nenájdu. Okamžite pridajte meta titulky a popis pre každú stránku, aby ste sa objavili v Googlovi. Chvályhodne máte bezpečnosť na vysokej úrovni." }, "opendata_security": { "ico": "35739487", "name": "NAY a.s.", "counts": { "low": 3, "high": 1, "info": 0, "total": 7, "medium": 3 }, "summary": { "spf": false, "ssl": { "valid": true, "issuer": "Let's Encrypt", "daysUntilExpiry": 65 }, "dmarc": null, "dnssec": false, "cveHigh": 0, "cveCount": 0, "mxProvider": null, "cveCritical": 0, "ctDomainsCount": 0, "httpSecurityScore": 20 }, "website": "https://nay.com", "findings": [ { "code": "LOW_SECURITY_SCORE", "title": "HTTP security score je nízke: 20/100", "detail": "Implementuj HSTS, CSP, X-Frame-Options a ďalšie security headers.", "category": "http", "severity": "high" }, { "code": "NO_SPF", "title": "Chýba SPF záznam (email spoofing risk)", "detail": null, "category": "dns", "severity": "medium" }, { "code": "NO_DMARC", "title": "Chýba DMARC záznam", "detail": null, "category": "dns", "severity": "medium" }, { "code": "NO_CSP", "title": "Chýba Content-Security-Policy", "detail": "CSP znižuje XSS riziko.", "category": "http", "severity": "medium" }, { "code": "NO_DNSSEC", "title": "Doména nemá DNSSEC", "detail": null, "category": "dns", "severity": "low" }, { "code": "NO_X_FRAME_OPTIONS", "title": "Chýba X-Frame-Options (clickjacking risk)", "detail": null, "category": "http", "severity": "low" }, { "code": "SERVER_HEADER_LEAKS_VERSION", "title": "Server hlavička odhaľuje verziu: \"openresty/1.27.1.2\"", "detail": "Uprav ServerTokens (Apache) alebo server_tokens off (nginx).", "category": "http", "severity": "low" } ], "cyberScore": { "band": "B", "score": 72, "buckets": { "ct": 100, "cve": 100, "ssl": 100, "http": 5 }, "computedAt": "2026-07-13T14:36:36.651Z" }, "overallScore": 36 } }, "created_at": "2026-07-27T06:46:09.154516+00:00", "status": "complete", "platform_detected": null, "company_ico": "35739487", "company_name": "NAY a.s.", "company_country": "SK", "company_nace": "4754", "company_size": "large", "nis2_scope": "none", "nis2_sector": null, "company_risk_score": 50, "company_risk_level": "medium" } }