Spamhaus.com Test Results

Spamhaus.com Mobile Performance: 24/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 710 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid an excessive DOM size
3,257 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce JavaScript execution time
7.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid large layout shifts
3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,620 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Properly size images
Potential savings of 742 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Eliminate render-blocking resources
Potential savings of 1,940 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused CSS
Potential savings of 32 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Minimize main-thread work
13.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Largest Contentful Paint element
12,660 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 756 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Serve static assets with an efficient cache policy
25 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Defer offscreen images
Potential savings of 135 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid enormous network payloads
Total size was 4,691 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
First Meaningful Paint
18.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
28.7 s
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.
Max Potential First Input Delay
440 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Spamhaus.com Mobile SEO: 85/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
8 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Spamhaus.com Mobile Best Practices: 76/100
Quick overview:
General
Browser errors were logged to the console
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
Trust and Safety
Does not use HTTPS
1 insecure request found
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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
Spamhaus.com Mobile Accessibility: 78/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
`[role]`s are not contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Similar sites
Similar tests
www.spamhaus.com
www.spamhaus.net
www.spamhaus.org
www.spamhaus.info
www.spamhaus.biz
www.spamhaus.us
www.spamhaus.mobi
www.pamhaus.com
www.spamhaus.com
www.wpamhaus.com
www.swpamhaus.com
www.wspamhaus.com
www.epamhaus.com
www.sepamhaus.com
www.espamhaus.com
www.dpamhaus.com
www.sdpamhaus.com
www.dspamhaus.com
www.zpamhaus.com
www.szpamhaus.com
www.zspamhaus.com
www.xpamhaus.com
www.sxpamhaus.com
www.xspamhaus.com
www.apamhaus.com
www.sapamhaus.com
www.aspamhaus.com
www.samhaus.com
www.soamhaus.com
www.spoamhaus.com
www.sopamhaus.com
www.slamhaus.com
www.splamhaus.com
www.slpamhaus.com
www.spmhaus.com
www.spqmhaus.com
www.spaqmhaus.com
www.spqamhaus.com
www.spwmhaus.com
www.spawmhaus.com
www.spwamhaus.com
www.spsmhaus.com
www.spasmhaus.com
www.spsamhaus.com
www.spzmhaus.com
www.spazmhaus.com
www.spzamhaus.com
www.spahaus.com
www.spanhaus.com
www.spamnhaus.com
www.spanmhaus.com
www.spajhaus.com
www.spamjhaus.com
www.spajmhaus.com
www.spakhaus.com
www.spamkhaus.com
www.spakmhaus.com
www.spamaus.com
www.spambaus.com
www.spamhbaus.com
www.spambhaus.com
www.spamgaus.com
www.spamhgaus.com
www.spamghaus.com
www.spamyaus.com
www.spamhyaus.com
www.spamyhaus.com
www.spamuaus.com
www.spamhuaus.com
www.spamuhaus.com
www.spamjaus.com
www.spamhjaus.com
www.spamnaus.com
www.spamhnaus.com
www.spamhus.com
www.spamhqus.com
www.spamhaqus.com
www.spamhqaus.com
www.spamhwus.com
www.spamhawus.com
www.spamhwaus.com
www.spamhsus.com
www.spamhasus.com
www.spamhsaus.com
www.spamhzus.com
www.spamhazus.com
www.spamhzaus.com
www.spamhas.com
www.spamhays.com
www.spamhauys.com
www.spamhayus.com
www.spamhahs.com
www.spamhauhs.com
www.spamhahus.com
www.spamhajs.com
www.spamhaujs.com
www.spamhajus.com
www.spamhais.com
www.spamhauis.com
www.spamhaius.com
www.spamhau.com
www.spamhauw.com
www.spamhausw.com
www.spamhauws.com
www.spamhaue.com
www.spamhause.com
www.spamhaues.com
www.spamhaud.com
www.spamhausd.com
www.spamhauds.com
www.spamhauz.com
www.spamhausz.com
www.spamhauzs.com
www.spamhaux.com
www.spamhausx.com
www.spamhauxs.com
www.spamhaua.com
www.spamhausa.com
www.spamhauas.com
www.spamhaus.con
Last Tested: