SEO audit for lokker.com
Privacy Intelligence Platform for Web Properties | Lokker
Health 83/100 (good) · 50 pages crawled · generated 2026-08-26
Download Markdown report (feed to ChatGPT / Claude / Cursor)Precision control over consumer data collection and sharing, built for privacy-first organizations.
| Category | Score | Errors | Warnings | Notices |
|---|---|---|---|---|
| Structured Data | 98 | 1 | 0 | 13 |
| Performance | 96 | 0 | 7 | 23 |
| Titles | 96 | 0 | 7 | 1 |
| Duplicate | 98 | 0 | 4 | 5 |
| Agent Readiness | 99 | 0 | 2 | 8 |
| Budget | 99 | 0 | 1 | 0 |
| Content | 100 | 0 | 0 | 119 |
| Crawlability | 100 | 0 | 0 | 1 |
| Images | 100 | 0 | 0 | 14 |
| Links | 100 | 0 | 0 | 1 |
Errors (1 rules)
error JSON-LD block missing @context or @type
Rule schema.no_context_type · Structured Data · 1 occurrence(s)
- https://lokker.com/events/iapp-europe-data-protection-congress — a JSON-LD block is missing @context or @type — Google can't parse it, so no rich result is possible. Add both fields (@context="https://schema.org" and a valid @type).
Warnings (6 rules)
warning Control has no accessible name
Rule agent.control_no_name · Agent Readiness · 2 occurrence(s)
- https://lokker.com/resources/quarterly-reports/quarterly-risk-report-q1-2026 — 1 button/link(s) with no text or aria-label — an agent can't target them
- https://lokker.com/terms-of-use — 1 button/link(s) with no text or aria-label — an agent can't target them
warning robots.txt-disallowed URL receives internal links (crawl-budget leak)
Rule budget.disallow_linked · Budget · 1 occurrence(s)
- https://lokker.com/api/directus-assets/18d56911-f46c-4de0-9284-514afa03771d — internal links point to https://lokker.com/api/directus-assets/18d56911-f46c-4de0-9284-514afa03771d, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://lokker.com/resources/2022-holiday-shopping-data-privacy-report.
warning Duplicate page content
Rule duplicate.content · Duplicate · 2 occurrence(s)
- https://lokker.com/bitsight-support — content shared by 2 pages: https://lokker.com/lokker-support
- https://lokker.com/lokker-support — content shared by 2 pages: https://lokker.com/bitsight-support
warning Duplicate <title> across pages
Rule duplicate.title · Duplicate · 2 occurrence(s)
- https://lokker.com/bitsight-support — title shared by 2 pages: https://lokker.com/lokker-support
- https://lokker.com/lokker-support — title shared by 2 pages: https://lokker.com/bitsight-support
warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)
Rule images.no_lazy_lcp_candidate · Performance · 7 occurrence(s)
- https://lokker.com/ — the likely hero/LCP image (adweek.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
- https://lokker.com/de — the likely hero/LCP image (adweek.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
- https://lokker.com/events/iapp-europe-data-protection-congress — the likely hero/LCP image (favicon) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
- https://lokker.com/fr — the likely hero/LCP image (adweek.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
- https://lokker.com/press — the likely hero/LCP image (what-the-hack-podcast.jpg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
- https://lokker.com/privacy-policy-guide — the likely hero/LCP image (favicon) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
- https://lokker.com/topics — the likely hero/LCP image (favicon) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
warning Title likely truncated in SERP (too wide)
Rule title.too_long · Titles · 7 occurrence(s)
- https://lokker.com/compare/ab-testing-tools — 84 chars, ~658px (limit ~580px)
- https://lokker.com/events — 84 chars, ~647px (limit ~580px)
- https://lokker.com/events/iapp-europe-data-protection-congress — 74 chars, ~603px (limit ~580px)
- https://lokker.com/fr — 88 chars, ~644px (limit ~580px)
- https://lokker.com/privacy-law — 81 chars, ~651px (limit ~580px)
- https://lokker.com/privacy-law/bipa — 84 chars, ~612px (limit ~580px)
- https://lokker.com/topics/adobe-experience-platform-data-collection — 75 chars, ~586px (limit ~580px)
Notices (19 rules)
notice Heading levels skip a level
Rule agent.heading_skip · Agent Readiness · 8 occurrence(s)
- https://lokker.com/about — h3 follows h1 — skips h2
- https://lokker.com/de/about — h3 follows h1 — skips h2
- https://lokker.com/fr/about — h3 follows h1 — skips h2
- https://lokker.com/privacy-policy — h3 follows h1 — skips h2
- https://lokker.com/products/consent-validator — h4 follows h2 — skips h3
- https://lokker.com/resources/quarterly-reports/quarterly-risk-report-q1-2026 — h4 follows h2 — skips h3
- https://lokker.com/security — h3 follows h1 — skips h2
- https://lokker.com/terms-of-use — h3 follows h1 — skips h2
notice Low text-to-HTML ratio
Rule content.low_ratio · Content · 31 occurrence(s)
- https://lokker.com/ — 3.6%
- https://lokker.com/blog/apples-got-it-exactly-right — 2.8%
- https://lokker.com/careers — 4.3%
- https://lokker.com/careers/openings — 3.4%
- https://lokker.com/compare — 4.9%
- https://lokker.com/contact — 4.5%
- https://lokker.com/demo — 4.2%
- https://lokker.com/docs — 3.3%
- https://lokker.com/events — 4.9%
- https://lokker.com/events/iapp-europe-data-protection-congress — 4.4%
- https://lokker.com/fingerprinting-demo — 4.3%
- https://lokker.com/press — 4.8%
- https://lokker.com/press/2023-in-review-the-rise-of-healthcare-data-privacy-regulations — 3.8%
- https://lokker.com/privacy-law — 4.6%
- https://lokker.com/products — 3.6%
- https://lokker.com/products/consent-validator — 4.4%
- https://lokker.com/resources/2022-holiday-shopping-data-privacy-report — 3.3%
- https://lokker.com/resources?type=quarterly_reports — 3.3%
- https://lokker.com/security — 3.2%
- https://lokker.com/services — 3.2%
- https://lokker.com/solutions — 3.5%
- https://lokker.com/solutions/board-risk-reporting — 3.4%
- https://lokker.com/training — 4.1%
- https://lokker.com/training/advanced-privacy — 3.4%
- https://lokker.com/who-we-help — 4.3%
notice Main text is hard to read (low Flesch Reading Ease)
Rule content.readability_poor · Content · 36 occurrence(s)
- https://lokker.com/ — this page reads as very difficult (Flesch Reading Ease 16, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/about — this page reads as very difficult (Flesch Reading Ease 23, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/bitsight-support — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/blog — this page reads as very difficult (Flesch Reading Ease 19, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/blog/apples-got-it-exactly-right — this page reads as very difficult (Flesch Reading Ease 17, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/careers — this page reads as difficult (Flesch Reading Ease 30, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/careers/openings — this page reads as very difficult (Flesch Reading Ease 14, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/compare — this page reads as very difficult (Flesch Reading Ease 11, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/contact — this page reads as difficult (Flesch Reading Ease 39, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/demo — this page reads as difficult (Flesch Reading Ease 32, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/docs — this page reads as very difficult (Flesch Reading Ease 8, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/events — this page reads as very difficult (Flesch Reading Ease 17, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/fingerprinting-demo — this page reads as very difficult (Flesch Reading Ease 23, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/glossary — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/lokker-support — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/press — this page reads as very difficult (Flesch Reading Ease 23, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/products — this page reads as very difficult (Flesch Reading Ease 4, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/resources — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/resources?type=quarterly_reports — this page reads as very difficult (Flesch Reading Ease 9, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/security — this page reads as very difficult (Flesch Reading Ease 9, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/services — this page reads as very difficult (Flesch Reading Ease 10, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/solutions — this page reads as very difficult (Flesch Reading Ease 16, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/topics — this page reads as very difficult (Flesch Reading Ease 23, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/training — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
- https://lokker.com/who-we-help — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
notice Duplicate meta description across pages
Rule duplicate.meta_desc · Duplicate · 5 occurrence(s)
- https://lokker.com/ — meta description shared by 3 pages: https://lokker.com/de, https://lokker.com/fr
- https://lokker.com/bitsight-support — meta description shared by 2 pages: https://lokker.com/lokker-support
- https://lokker.com/de — meta description shared by 3 pages: https://lokker.com/, https://lokker.com/fr
- https://lokker.com/fr — meta description shared by 3 pages: https://lokker.com/, https://lokker.com/de
- https://lokker.com/lokker-support — meta description shared by 2 pages: https://lokker.com/bitsight-support
notice Article page has no author attribution (E-E-A-T)
Rule eeat.no_author · Content · 3 occurrence(s)
- https://lokker.com/press/2023-in-review-the-rise-of-healthcare-data-privacy-regulations — this page is marked up as an article but its JSON-LD has no author and no visible byline — add an author to strengthen the E-E-A-T Trust signal
- https://lokker.com/resources/2022-holiday-shopping-data-privacy-report — this page is marked up as an article but its JSON-LD has no author and no visible byline — add an author to strengthen the E-E-A-T Trust signal
- https://lokker.com/resources/quarterly-reports/quarterly-risk-report-q1-2026 — this page is marked up as an article but its JSON-LD has no author and no visible byline — add an author to strengthen the E-E-A-T Trust signal
notice Article page has no publication date (freshness / E-E-A-T)
Rule eeat.no_date · Content · 1 occurrence(s)
- https://lokker.com/privacy-law/bipa — this page is marked up as an article but has no publication date — no datePublished in its JSON-LD and no visible date — add a visible published date and an Article.datePublished so Google can assess freshness
notice Image alt text is very long (possible keyword stuffing)
Rule images.alt_too_long · Images · 1 occurrence(s)
- https://lokker.com/resources — 18 image(s) with alt text over 100 chars — shorten it to a concise description
notice Image filename is generic/auto-generated (missed image-search signal)
Rule images.generic_filename · Images · 8 occurrence(s)
- https://lokker.com/bitsight-support — 5 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/blog — 22 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/blog/apples-got-it-exactly-right — 6 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/lokker-support — 5 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/press — 12 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/press/2023-in-review-the-rise-of-healthcare-data-privacy-regulations — 6 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/resources — 105 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
- https://lokker.com/resources/2022-holiday-shopping-data-privacy-report — 5 image(s) use a generic/auto-generated filename (e.g. IMG_1234.jpg, photo1.png, a bare UUID). Google reads the filename as a signal of image content, so rename files descriptively (hyphen-separated words) before upload.
notice Likely hero image lacks fetchpriority=high
Rule images.hero_no_fetchpriority · Performance · 9 occurrence(s)
- https://lokker.com/about — the likely hero/LCP image (ian-cohen.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/bitsight-support — the likely hero/LCP image (img-1.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/compare/ab-testing-tools — the likely hero/LCP image (favicon) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/de/about — the likely hero/LCP image (ian-cohen.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/fr/about — the likely hero/LCP image (ian-cohen.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/lokker-support — the likely hero/LCP image (img-1.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/privacy-policy-guide/cookiebot — the likely hero/LCP image (favicon) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/products/consent-validator — the likely hero/LCP image (favicon) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
- https://lokker.com/topics/adobe-experience-platform-data-collection — the likely hero/LCP image (favicon) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
notice Images without width/height (layout shift / CLS)
Rule images.missing_dimensions · Images · 5 occurrence(s)
- https://lokker.com/about — 8 of 14 images without width/height
- https://lokker.com/bitsight-support — 5 of 10 images without width/height
- https://lokker.com/de/about — 8 of 14 images without width/height
- https://lokker.com/fr/about — 8 of 14 images without width/height
- https://lokker.com/lokker-support — 5 of 10 images without width/height
notice Internal link has no anchor text / accessible name
Rule links.no_anchor_text · Links · 1 occurrence(s)
- https://lokker.com/terms-of-use — 1 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
notice Legacy <meta name=keywords> tag present (Google ignores it)
Rule meta.keywords_present · Content · 48 occurrence(s)
- https://lokker.com/ — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/about — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/bitsight-support — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/blog — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/careers — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/compare — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/contact — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/demo — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/docs — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/events — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/fingerprinting-demo — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/glossary — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/lokker-support — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/press — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/privacy-law — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/privacy-policy — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/privacy-policy-guide — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/products — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/resources — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/resources?type=quarterly_reports — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/security — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/services — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/solutions — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/terms-of-use — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- https://lokker.com/topics — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
notice Large DOM (over 1500 elements) slows rendering & interaction
Rule perf.dom_size_large · Performance · 5 occurrence(s)
- https://lokker.com/bitsight-support — the page has 1868 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
- https://lokker.com/compare/ab-testing-tools — the page has 2057 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
- https://lokker.com/glossary — the page has 2713 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
- https://lokker.com/lokker-support — the page has 1868 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
- https://lokker.com/resources — the page has 2489 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
notice Legacy image format (jpg/png/gif) with no next-gen fallback
Rule perf.images_legacy_format · Performance · 9 occurrence(s)
- https://lokker.com/ — 36 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/about — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/bitsight-support — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/de — 36 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/de/about — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/fr — 36 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/fr/about — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/lokker-support — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
- https://lokker.com/press — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
notice URL redirects to another URL
Rule redirect.single · Crawlability · 1 occurrence(s)
- https://lokker.com/lokker-support — redirects to https://lokker.com/bitsight-support
notice Article schema missing recommended properties (Top Stories / image carousel)
Rule schema.article_incomplete · Structured Data · 5 occurrence(s)
- https://lokker.com/press/2023-in-review-the-rise-of-healthcare-data-privacy-regulations — NewsArticle structured data is missing recommended property (author) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://lokker.com/privacy-law/bipa — Article structured data is missing recommended properties (image, datePublished) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://lokker.com/privacy-policy-guide/cookiebot — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://lokker.com/resources/2022-holiday-shopping-data-privacy-report — BlogPosting structured data is missing recommended property (author) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- https://lokker.com/resources/quarterly-reports/quarterly-risk-report-q1-2026 — BlogPosting structured data is missing recommended property (author) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
notice Deprecated schema type with no Google rich result
Rule schema.deprecated_type · Structured Data · 4 occurrence(s)
- https://lokker.com/ — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- https://lokker.com/de — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- https://lokker.com/fr — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- https://lokker.com/privacy-policy-guide/cookiebot — deprecated rich-result type(s) present: HowTo. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
notice FAQPage structured data (rich result removed May 2026)
Rule schema.faq_deprecated · Structured Data · 4 occurrence(s)
- https://lokker.com/compare/ab-testing-tools — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
- https://lokker.com/privacy-law/bipa — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
- https://lokker.com/privacy-policy-guide/cookiebot — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
- https://lokker.com/products/consent-validator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
notice Title is very short
Rule title.too_short · Titles · 1 occurrence(s)
- https://lokker.com/blog — 13 chars
| URL | Status | Indexable | Words | In-links |
|---|---|---|---|---|
| https://lokker.com/about About Lokker | Lokker |
200 | yes | 1807 | 45 |
| https://lokker.com/ Privacy Intelligence Platform for Web Properties | Lokker |
200 | yes | 1091 | 45 |
| https://lokker.com/blog Blog | Lokker |
200 | yes | 1843 | 43 |
| https://lokker.com/careers Careers | Lokker |
200 | yes | 1076 | 43 |
| https://lokker.com/compare MarTech Tool Comparisons: Privacy, Features, and Compliance | Lokker |
200 | yes | 1120 | 43 |
| https://lokker.com/contact Contact Us | Lokker |
200 | yes | 1296 | 43 |
| https://lokker.com/demo Request a Demo | Lokker |
200 | yes | 1045 | 43 |
| https://lokker.com/docs Documentation | Lokker |
200 | yes | 672 | 43 |
| https://lokker.com/events Privacy Industry Events: Conferences for Privacy, Legal, and Security Teams | Lokker |
200 | yes | 1350 | 43 |
| https://lokker.com/glossary Web Privacy Glossary: Key Terms Explained | Lokker |
200 | yes | 8642 | 43 |
| https://lokker.com/press Press & News | Lokker |
200 | yes | 1576 | 43 |
| https://lokker.com/privacy-law US Privacy Laws and Website Liability: VPPA, CIPA, HIPAA, CCPA, and More | Lokker |
200 | yes | 1025 | 43 |
| https://lokker.com/privacy-policy Privacy Notice | Lokker |
200 | yes | 6014 | 43 |
| https://lokker.com/privacy-policy-guide Privacy Policy Disclosure Guide for Third-Party Tools | Lokker |
200 | yes | 2315 | 43 |
| https://lokker.com/products Privacy Management Software and Data Privacy Tools | Lokker |
200 | yes | 879 | 43 |
| https://lokker.com/products/consent-validator Consent Validator: Consent Misconfiguration Detection | Lokker |
200 | yes | 1473 | 43 |
| https://lokker.com/resources Resources | Lokker |
200 | yes | 7481 | 43 |
| https://lokker.com/resources?type=quarterly_reports Resources | Lokker |
200 | yes | 730 | 43 |
| https://lokker.com/security Security at LOKKER | Lokker |
200 | yes | 668 | 43 |
| https://lokker.com/services/consent-tag-orchestration CMP and Tag Manager Orchestration Services | Lokker |
200 | yes | 1735 | 43 |
| https://lokker.com/solutions Solutions | Lokker |
200 | yes | 894 | 43 |
| https://lokker.com/solutions/board-risk-reporting Board & risk reporting | Solutions | Lokker |
200 | yes | 819 | 43 |
| https://lokker.com/terms-of-use Terms of Use | Lokker |
200 | yes | 7274 | 43 |
| https://lokker.com/training Training: Privacy Academy | Lokker |
200 | yes | 1131 | 43 |
| https://lokker.com/who-we-help Who We Help | Lokker |
200 | yes | 1121 | 43 |
| https://lokker.com/who-we-help/agencies Agencies | Lokker |
200 | yes | 920 | 43 |
| https://lokker.com/de/about Über Lokker | Lokker |
200 | yes | 1702 | 5 |
| https://lokker.com/de Datenschutz-Intelligenz-Plattform für Web-Properties | Lokker |
200 | yes | 1020 | 5 |
| https://lokker.com/fr/about À propos de Lokker | Lokker |
200 | yes | 2050 | 4 |
| https://lokker.com/fr Plateforme d'intelligence en matière de confidentialité pour les propriétés web | Lokker |
200 | yes | 1328 | 4 |
| https://lokker.com/topics Privacy Stack Topics: CMPs, Tag Managers, and Marketing Tools | Lokker |
200 | yes | 1749 | 6 |
| https://lokker.com/resources/quarterly-reports/quarterly-risk-report-q1-2026 Quarterly Risk Report – Q1 2026 | Lokker |
200 | yes | 974 | 5 |
| https://lokker.com/careers/openings Open Positions | Lokker |
200 | yes | 768 | 4 |
| https://lokker.com/topics/adobe-experience-platform-data-collection Adobe Experience Platform Data Collection Privacy Risk and Consent | Lokker |
200 | yes | 1317 | 3 |
| https://lokker.com/privacy-law/bipa Illinois BIPA: Biometric Data, Device Fingerprinting, and Website Liability | Lokker |
200 | yes | 1420 | 2 |
| https://lokker.com/services Services | Lokker |
200 | yes | 668 | 2 |
| https://lokker.com/training/advanced-privacy Advanced Privacy: Privacy Academy | Lokker |
200 | yes | 827 | 2 |
| https://lokker.com/compare/ab-testing-tools Best A/B Testing Tools Compared (2026): Privacy, Consent, and Feature Flags | Lokker |
200 | yes | 2990 | 2 |
| https://lokker.com/events/iapp-europe-data-protection-congress IAPP Europe Data Protection Congress: Web Privacy and GDPR Topics | Lokker |
200 | yes | 1015 | 2 |
| https://lokker.com/fingerprinting-demo Device Fingerprinting Demo | Lokker |
200 | yes | 981 | 2 |
| https://lokker.com/privacy-policy-guide/cookiebot How to Disclose Cookiebot in Your Privacy Policy | Lokker |
200 | yes | 2161 | 2 |
| https://lokker.com/blog/apples-got-it-exactly-right Apple’s got it exactly right! | Lokker |
200 | yes | 705 | 2 |
| https://lokker.com/press/2023-in-review-the-rise-of-healthcare-data-privacy-regulations 2023 in Review: The Rise of Healthcare Data Privacy Regulations | Lokker |
200 | yes | 915 | 2 |
| https://lokker.com/resources/2022-holiday-shopping-data-privacy-report 2022 Holiday Shopping Data Privacy Report | Lokker |
200 | yes | 753 | 2 |
| https://lokker.com/de/careers/openings Offene Stellen | Lokker |
200 | yes | 715 | 2 |
| https://lokker.com/careers/openings/privacy-engineer-forensics Software Engineer, Privacy & Consent - Open Position | Lokker |
200 | yes | 1197 | 2 |
| https://lokker.com/bitsight-support Support for Your Privacy Risk Assessment Report | Lokker |
200 | yes | 5602 | 2 |
| https://lokker.com/lokker-support Support for Your Privacy Risk Assessment Report | Lokker |
200 | yes | 5602 | 0 |
| https://lokker.com/llms-full.txt | 200 | no | 0 | 0 |
| https://lokker.com/llms.txt | 200 | no | 0 | 0 |
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.