Open2.net Test Results
Open2.net Mobile Performance: 5/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Enable text compression
Potential savings of 79 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Eliminate render-blocking resources
Potential savings of 4,740 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 serving legacy JavaScript to modern browsers
Potential savings of 41 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
Reduce unused CSS
Potential savings of 576 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.
Reduce unused JavaScript
Potential savings of 3,269 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.
Largest Contentful Paint element
12,040 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
6.2 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
2 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
Avoid multiple page redirects
Potential savings of 1,440 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,170 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.
Minimize main-thread work
9.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 minimize main-thread work
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`.
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.
Serve static assets with an efficient cache policy
18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
Avoid enormous network payloads
Total size was 4,780 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Max Potential First Input Delay
1,110 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
30.0 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.
Open2.net Mobile SEO: 75/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page has unsuccessful HTTP status code
404
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
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
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.
Open2.net Mobile Best Practices: 41/100
Quick overview:
General
Uses third-party cookies
2 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.
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
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.
Trust and Safety
Does not use HTTPS
3 insecure requests 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.
Open2.net Mobile Accessibility: 96/100
Quick overview:
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Similar sites
Similar tests
www.open2.com
www.open2.net
www.open2.org
www.open2.info
www.open2.biz
www.open2.us
www.open2.mobi
www.pen2.net
www.open2.net
www.ipen2.net
www.oipen2.net
www.iopen2.net
www.kpen2.net
www.okpen2.net
www.kopen2.net
www.lpen2.net
www.olpen2.net
www.lopen2.net
www.ppen2.net
www.oppen2.net
www.popen2.net
www.oen2.net
www.ooen2.net
www.opoen2.net
www.oopen2.net
www.olen2.net
www.oplen2.net
www.opn2.net
www.opwn2.net
www.opewn2.net
www.opwen2.net
www.opsn2.net
www.opesn2.net
www.opsen2.net
www.opdn2.net
www.opedn2.net
www.opden2.net
www.oprn2.net
www.opern2.net
www.opren2.net
www.ope2.net
www.opeb2.net
www.openb2.net
www.opebn2.net
www.opeh2.net
www.openh2.net
www.opehn2.net
www.opej2.net
www.openj2.net
www.opejn2.net
www.opem2.net
www.openm2.net
www.opemn2.net
www.open.net
www.open2.net
www.open2.org
www.open2.info
www.open2.biz
www.open2.us
www.open2.mobi
www.pen2.net
www.open2.net
www.ipen2.net
www.oipen2.net
www.iopen2.net
www.kpen2.net
www.okpen2.net
www.kopen2.net
www.lpen2.net
www.olpen2.net
www.lopen2.net
www.ppen2.net
www.oppen2.net
www.popen2.net
www.oen2.net
www.ooen2.net
www.opoen2.net
www.oopen2.net
www.olen2.net
www.oplen2.net
www.opn2.net
www.opwn2.net
www.opewn2.net
www.opwen2.net
www.opsn2.net
www.opesn2.net
www.opsen2.net
www.opdn2.net
www.opedn2.net
www.opden2.net
www.oprn2.net
www.opern2.net
www.opren2.net
www.ope2.net
www.opeb2.net
www.openb2.net
www.opebn2.net
www.opeh2.net
www.openh2.net
www.opehn2.net
www.opej2.net
www.openj2.net
www.opejn2.net
www.opem2.net
www.openm2.net
www.opemn2.net
www.open.net