Lighthouse Desktop
· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.Detailed Report
Audit breakdown by category with detailed findings.
Performance
Insights
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
Performance issues directly impact user engagement and conversion rates.
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 |
Accessibility
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.
Navigation
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.
Best practices
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.
Best Practices
Trust and Safety
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 |
General
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 |
SEO
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.
Content Best Practices
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.
Crawling and Indexing
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.