Spain · Madrid Completed: Apr 22, 2026 00:33 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Missing metadata means poor previews on social media and search.
Lean and efficient — low environmental impact per visit.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Cookie 'techaro.lol-anubis-auth' is missing the HttpOnly flag
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/b9cc101d-5307-4e76-b07a-eae8821cb3c0)<a href="https://beavercheck.com/results/b9cc101d-5307-4e76-b07a-eae8821cb3c0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmozillazine.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmozillazine.orgThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
7 barrier(s) likely increasing bounce by ~20%.
Page loads in 3.9s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 1.4s over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$350 investment → $2,631/month returns + USD 157,500 risk avoided
$350
4h · 5 findings
$2,631 /mo
~$31,575 / year
USD 157,500
if kept compliant
$200 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
3.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,501 / year if left unfixed
$157,500
+1 more
$0.10 /mo
1298.6 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.00 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.90 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
10 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.038
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.00 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
4.43 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| ssl.google-analytics.com/ga.js | 7200.0 s | 17.4 KiB |
| mozillazine.org/image/default/sky.png | 0.0 ms | 8.6 KiB |
| mozillazine.org/image/default/blimp.png | 0.0 ms | 1.7 KiB |
| mozillazine.org/image/new/title.gif | 0.0 ms | 1.1 KiB |
| mozillazine.org/style/smallfront.css | 0.0 ms | 865 B |
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| mozillazine.org/style/smallfront.css | 865 B |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| mozillazine.org/ | 3.9 s |
| /.within.website/x/cmd/anubis/api/pass-challenge?id=019db... | 0.0 ms |
| mozillazine.org/ | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Forums tbody > tr > td > h3 |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Firefox Support tbody > tr > td > a |
Thunderbird Support tbody > tr > td > a |
Seamonkey Support tbody > tr > td > a |
Extensions and Themes tbody > tr > td > a |
mozillaZine Support tbody > tr > td > a |
Firefox Top Articles tbody > tr > td > a |
Thunderbird Top Articles tbody > tr > td > a |
Seamonkey Top Articles tbody > tr > td > a |
Other Mozilla Products tbody > tr > td > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.google-analytics.com/urchin.js | Blocked |
| pagead2.googlesyndication.com/pagead/show_ads.js | Blocked |
| www.google.com/custom | Allowed with warning |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
MozillaZine body > div#masthead > h1 > img | mozillazine.org/image/new/title.gif | 180 x 70 | 180 x 70 | 270 x 105 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Mixed Content: The page at 'https://mozillazine.org/' was loaded over HTTPS, but requested an insecure script 'http://pagead2.googlesyndication.com/pagead/show_ads.js'. This request has been blocked; the content must be served over HTTPS. | |
Mixed Content: The page at 'https://mozillazine.org/' was loaded over HTTPS, but requested an insecure script 'http://www.google-analytics.com/urchin.js'. This request has been blocked; the content must be served over HTTPS. | |
mozillazine.org/ line 8, col 56 | ReferenceError: urchinTracker is not defined
at https://mozillazine.org/:9:57 |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <!doctype html><html lang="en"><head><title>Oh noes!</title><link rel="stylesheet" href="/.within.website/x/xess/xess.min.css?cachebuster=1.25.0"><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta name="robots" content="noindex,nofollow"><style> | Syntax not understood |
| 2 | body, | Syntax not understood |
| 3 | html { | Syntax not understood |
| 4 | height: 100%; | Unknown directive |
| 5 | display: flex; | Unknown directive |
| 6 | justify-content: center; | Unknown directive |
| 7 | align-items: center; | Unknown directive |
| 8 | margin-left: auto; | Unknown directive |
| 9 | margin-right: auto; | Unknown directive |
| 10 | } | Syntax not understood |
| 12 | .centered-div { | Syntax not understood |
| 13 | text-align: center; | Unknown directive |
| 14 | } | Syntax not understood |
| 17 | font-variant-numeric: tabular-nums; | Unknown directive |
| 18 | } | Syntax not understood |
| 21 | display: none; | Unknown directive |
| 22 | width: 90%; | Unknown directive |
| 23 | width: min(20rem, 90%); | Unknown directive |
| 24 | height: 2rem; | Unknown directive |
| 25 | border-radius: 1rem; | Unknown directive |
| 26 | overflow: hidden; | Unknown directive |
| 27 | margin: 1rem 0 2rem; | Unknown directive |
| 28 | outline-offset: 2px; | Unknown directive |
| 29 | outline: #b16286 solid 4px; | Unknown directive |
| 30 | } | Syntax not understood |
| 32 | .bar-inner { | Syntax not understood |
| 33 | background-color: #b16286; | Unknown directive |
| 34 | height: 100%; | Unknown directive |
| 35 | width: 0; | Unknown directive |
| 36 | transition: width 0.25s ease-in; | Unknown directive |
| 37 | } | Syntax not understood |
| 38 | </style><script id="anubis_version" type="application/json">"1.25.0" | Syntax not understood |
| 39 | </script><script id="anubis_challenge" type="application/json">null | Syntax not understood |
| 40 | </script><script id="anubis_base_prefix" type="application/json">"" | Syntax not understood |
| 41 | </script><script id="anubis_public_url" type="application/json">"" | Syntax not understood |
| 42 | </script></head><body id="top"><script type="ignore"><a href="/.within.website/x/cmd/anubis/api/honeypot/47bad980-b6cb-4839-a0d3-9a10bfd9e7db/init">Don't click me</a></script><main><h1 id="title" class="centered-div">Oh noes!</h1><div class="centered-div"><img id="image" alt="Sad Anubis" style="width:100%;max-width:256px;" src="/.within.website/x/cmd/anubis/static/img/reject.webp?cacheBuster=1.25.0"><p>Access Denied: error code 4d1dbaddfcc0f385.</p><p><a href="/">Go home</a></p></div><footer><div class="centered-div"><p>Protected by <a href="https://github.com/TecharoHQ/anubis">Anubis</a> From <a href="https://techaro.lol">Techaro</a>. Made with ❤️ in 🇨🇦.</p><p>Mascot design by <a href="https://bsky.app/profile/celphase.bsky.social">CELPHASE</a>.</p><p>This website is running Anubis version <code>1.25.0</code>.</p></div></footer></main></body></html> | Unknown directive |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.33 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.43 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.014
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.33 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
1.43 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| ssl.google-analytics.com/ga.js | 7200.0 s | 17.4 KiB |
| mozillazine.org/image/default/sky.png | 0.0 ms | 8.6 KiB |
| mozillazine.org/image/default/blimp.png | 0.0 ms | 1.7 KiB |
| mozillazine.org/image/new/title.gif | 0.0 ms | 1.1 KiB |
| mozillazine.org/style/smallfront.css | 0.0 ms | 865 B |
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| mozillazine.org/style/smallfront.css | 865 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| mozillazine.org/ | 1.4 s |
| /.within.website/x/cmd/anubis/api/pass-challenge?id=019db... | 0.0 ms |
| mozillazine.org/ | 0.0 ms |
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Forums tbody > tr > td > h3 |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Firefox Support tbody > tr > td > a |
Thunderbird Support tbody > tr > td > a |
Seamonkey Support tbody > tr > td > a |
Extensions and Themes tbody > tr > td > a |
mozillaZine Support tbody > tr > td > a |
Firefox Top Articles tbody > tr > td > a |
Thunderbird Top Articles tbody > tr > td > a |
Seamonkey Top Articles tbody > tr > td > a |
Other Mozilla Products tbody > tr > td > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.google-analytics.com/urchin.js | Blocked |
| pagead2.googlesyndication.com/pagead/show_ads.js | Blocked |
| www.google.com/custom | Allowed with warning |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Mixed Content: The page at 'https://mozillazine.org/' was loaded over HTTPS, but requested an insecure script 'http://pagead2.googlesyndication.com/pagead/show_ads.js'. This request has been blocked; the content must be served over HTTPS. | |
Mixed Content: The page at 'https://mozillazine.org/' was loaded over HTTPS, but requested an insecure script 'http://www.google-analytics.com/urchin.js'. This request has been blocked; the content must be served over HTTPS. | |
mozillazine.org/ line 8, col 56 | ReferenceError: urchinTracker is not defined
at https://mozillazine.org/:9:57 |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <!doctype html><html lang="en"><head><title>Oh noes!</title><link rel="stylesheet" href="/.within.website/x/xess/xess.min.css?cachebuster=1.25.0"><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta name="robots" content="noindex,nofollow"><style> | Syntax not understood |
| 2 | body, | Syntax not understood |
| 3 | html { | Syntax not understood |
| 4 | height: 100%; | Unknown directive |
| 5 | display: flex; | Unknown directive |
| 6 | justify-content: center; | Unknown directive |
| 7 | align-items: center; | Unknown directive |
| 8 | margin-left: auto; | Unknown directive |
| 9 | margin-right: auto; | Unknown directive |
| 10 | } | Syntax not understood |
| 12 | .centered-div { | Syntax not understood |
| 13 | text-align: center; | Unknown directive |
| 14 | } | Syntax not understood |
| 17 | font-variant-numeric: tabular-nums; | Unknown directive |
| 18 | } | Syntax not understood |
| 21 | display: none; | Unknown directive |
| 22 | width: 90%; | Unknown directive |
| 23 | width: min(20rem, 90%); | Unknown directive |
| 24 | height: 2rem; | Unknown directive |
| 25 | border-radius: 1rem; | Unknown directive |
| 26 | overflow: hidden; | Unknown directive |
| 27 | margin: 1rem 0 2rem; | Unknown directive |
| 28 | outline-offset: 2px; | Unknown directive |
| 29 | outline: #b16286 solid 4px; | Unknown directive |
| 30 | } | Syntax not understood |
| 32 | .bar-inner { | Syntax not understood |
| 33 | background-color: #b16286; | Unknown directive |
| 34 | height: 100%; | Unknown directive |
| 35 | width: 0; | Unknown directive |
| 36 | transition: width 0.25s ease-in; | Unknown directive |
| 37 | } | Syntax not understood |
| 38 | </style><script id="anubis_version" type="application/json">"1.25.0" | Syntax not understood |
| 39 | </script><script id="anubis_challenge" type="application/json">null | Syntax not understood |
| 40 | </script><script id="anubis_base_prefix" type="application/json">"" | Syntax not understood |
| 41 | </script><script id="anubis_public_url" type="application/json">"" | Syntax not understood |
| 42 | </script></head><body id="top"><script type="ignore"><a href="/.within.website/x/cmd/anubis/api/honeypot/1e505d90-7ffa-428f-858b-3f94bbd3c41d/init">Don't click me</a></script><main><h1 id="title" class="centered-div">Oh noes!</h1><div class="centered-div"><img id="image" alt="Sad Anubis" style="width:100%;max-width:256px;" src="/.within.website/x/cmd/anubis/static/img/reject.webp?cacheBuster=1.25.0"><p>Access Denied: error code 4d1dbaddfcc0f385.</p><p><a href="/">Go home</a></p></div><footer><div class="centered-div"><p>Protected by <a href="https://github.com/TecharoHQ/anubis">Anubis</a> From <a href="https://techaro.lol">Techaro</a>. Made with ❤️ in 🇨🇦.</p><p>Mascot design by <a href="https://bsky.app/profile/celphase.bsky.social">CELPHASE</a>.</p><p>This website is running Anubis version <code>1.25.0</code>.</p></div></footer></main></body></html> | Unknown directive |
To appear in search results, crawlers need access to your app.
Send Feedback