Hornet.org Site Title

The Hornet Archive

Hornet.org Test Results

Hornet.org Mobile Performance: 31/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 1,500 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.
Avoid large layout shifts
4 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
Minimize main-thread work
19.3 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
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.
Reduce JavaScript execution time
15.6 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.
Reduce unused JavaScript
Potential savings of 1,956 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.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
Reduce the impact of third-party code
Third-party code blocked the main thread for 13,020 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.
Largest Contentful Paint element
3,690 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Efficiently encode images
Potential savings of 22 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid enormous network payloads
Total size was 3,890 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused CSS
Potential savings of 58 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.
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.
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`.
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
Enable text compression
Potential savings of 3 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Serve images in next-gen formats
Potential savings of 25 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.
Max Potential First Input Delay
1,340 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.
Time to Interactive
36.1 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.

Hornet.org Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
467 errors found
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.

Hornet.org Mobile Best Practices: 55/100
Quick overview:
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.
General
Issues were logged in the `Issues` panel in Chrome Devtools
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.
Uses third-party cookies
3 cookies found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Browser Compatibility
Charset declaration is missing or occurs too late in the HTML
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Hornet.org Mobile Accessibility: 70/100
Quick overview:
Contrast
These are opportunities to improve the legibility of your content.
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.
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.
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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Similar tests
www.hornet.com
www.hornet.net
www.hornet.org
www.hornet.info
www.hornet.biz
www.hornet.us
www.hornet.mobi
www.ornet.org
www.hornet.org
www.bornet.org
www.hbornet.org
www.bhornet.org
www.gornet.org
www.hgornet.org
www.ghornet.org
www.yornet.org
www.hyornet.org
www.yhornet.org
www.uornet.org
www.huornet.org
www.uhornet.org
www.jornet.org
www.hjornet.org
www.jhornet.org
www.nornet.org
www.hnornet.org
www.nhornet.org
www.hrnet.org
www.hirnet.org
www.hoirnet.org
www.hiornet.org
www.hkrnet.org
www.hokrnet.org
www.hkornet.org
www.hlrnet.org
www.holrnet.org
www.hlornet.org
www.hprnet.org
www.hoprnet.org
www.honet.org
www.hoenet.org
www.horenet.org
www.hoernet.org
www.hodnet.org
www.hordnet.org
www.hodrnet.org
www.hofnet.org
www.horfnet.org
www.hofrnet.org
www.hotnet.org
www.hortnet.org
www.hotrnet.org
www.horet.org
www.horbet.org
www.hornbet.org
www.horbnet.org
www.horhet.org
www.hornhet.org
www.horhnet.org
www.horjet.org
www.hornjet.org
www.horjnet.org
www.hormet.org
www.hornmet.org
www.hormnet.org
www.hornt.org
www.hornwt.org
www.hornewt.org
www.hornwet.org
www.hornst.org
www.hornest.org
www.hornset.org
www.horndt.org
www.hornedt.org
www.horndet.org
www.hornrt.org
www.hornert.org
www.hornret.org
www.horne.org
www.horner.org
www.hornetr.org
www.hornef.org
www.hornetf.org
www.horneft.org
www.horneg.org
www.hornetg.org
www.hornegt.org
www.horney.org
www.hornety.org
www.horneyt.org
Last Tested: