Diablo2.io Site Title
Diablo 2 Resurrected - Everything we know so far
Diablo2.io Meta Description
This is a filterable and searchable FAQ for everything we know about Diablo 2 Resurrected so far; including release date, offline play, graphics and more.
Diablo2.io Test Results
Diablo2.io Mobile Performance: 46/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce JavaScript execution time
7.5 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 CSS
Potential savings of 72 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.
Largest Contentful Paint element
4,290 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minify CSS
Potential savings of 26 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Minimize main-thread work
13.1 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
Reduce initial server response time
Root document took 1,070 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Avoid an excessive DOM size
1,782 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.
Defer offscreen images
Potential savings of 100 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.
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 the impact of third-party code
Third-party code blocked the main thread for 2,370 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.
Eliminate render-blocking resources
Potential savings of 1,110 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 22 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
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.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Serve static assets with an efficient cache policy
79 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused JavaScript
Potential savings of 275 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.
Minify JavaScript
Potential savings of 13 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Max Potential First Input Delay
1,010 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
17.5 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.
Diablo2.io Mobile SEO: 83/100
Quick overview:
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Diablo2.io Mobile Best Practices: 59/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.
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
Uses third-party cookies
1 cookie 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.
Diablo2.io Mobile Accessibility: 58/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.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are not wrapped in `<dl>` elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
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.
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.
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.
Similar sites
Similar tests
www.diablo2.com
www.diablo2.net
www.diablo2.org
www.diablo2.info
www.diablo2.biz
www.diablo2.us
www.diablo2.mobi
www.iablo2.io
www.diablo2.io
www.xiablo2.io
www.dxiablo2.io
www.xdiablo2.io
www.siablo2.io
www.dsiablo2.io
www.sdiablo2.io
www.eiablo2.io
www.deiablo2.io
www.ediablo2.io
www.riablo2.io
www.driablo2.io
www.rdiablo2.io
www.fiablo2.io
www.dfiablo2.io
www.fdiablo2.io
www.ciablo2.io
www.dciablo2.io
www.cdiablo2.io
www.dablo2.io
www.duablo2.io
www.diuablo2.io
www.duiablo2.io
www.djablo2.io
www.dijablo2.io
www.djiablo2.io
www.dkablo2.io
www.dikablo2.io
www.dkiablo2.io
www.doablo2.io
www.dioablo2.io
www.doiablo2.io
www.diblo2.io
www.diqblo2.io
www.diaqblo2.io
www.diqablo2.io
www.diwblo2.io
www.diawblo2.io
www.diwablo2.io
www.disblo2.io
www.diasblo2.io
www.disablo2.io
www.dizblo2.io
www.diazblo2.io
www.dizablo2.io
www.dialo2.io
www.diavlo2.io
www.diabvlo2.io
www.diavblo2.io
www.diaglo2.io
www.diabglo2.io
www.diagblo2.io
www.diahlo2.io
www.diabhlo2.io
www.diahblo2.io
www.dianlo2.io
www.diabnlo2.io
www.dianblo2.io
www.diabo2.io
www.diabpo2.io
www.diablpo2.io
www.diabplo2.io
www.diaboo2.io
www.diabloo2.io
www.diabolo2.io
www.diabko2.io
www.diablko2.io
www.diabklo2.io
www.diabl2.io
www.diabli2.io
www.diabloi2.io
www.diablio2.io
www.diablk2.io
www.diablok2.io
www.diabll2.io
www.diablol2.io
www.diabllo2.io
www.diablp2.io
www.diablop2.io
www.diablo.io
www.diablo2.net
www.diablo2.org
www.diablo2.info
www.diablo2.biz
www.diablo2.us
www.diablo2.mobi
www.iablo2.io
www.diablo2.io
www.xiablo2.io
www.dxiablo2.io
www.xdiablo2.io
www.siablo2.io
www.dsiablo2.io
www.sdiablo2.io
www.eiablo2.io
www.deiablo2.io
www.ediablo2.io
www.riablo2.io
www.driablo2.io
www.rdiablo2.io
www.fiablo2.io
www.dfiablo2.io
www.fdiablo2.io
www.ciablo2.io
www.dciablo2.io
www.cdiablo2.io
www.dablo2.io
www.duablo2.io
www.diuablo2.io
www.duiablo2.io
www.djablo2.io
www.dijablo2.io
www.djiablo2.io
www.dkablo2.io
www.dikablo2.io
www.dkiablo2.io
www.doablo2.io
www.dioablo2.io
www.doiablo2.io
www.diblo2.io
www.diqblo2.io
www.diaqblo2.io
www.diqablo2.io
www.diwblo2.io
www.diawblo2.io
www.diwablo2.io
www.disblo2.io
www.diasblo2.io
www.disablo2.io
www.dizblo2.io
www.diazblo2.io
www.dizablo2.io
www.dialo2.io
www.diavlo2.io
www.diabvlo2.io
www.diavblo2.io
www.diaglo2.io
www.diabglo2.io
www.diagblo2.io
www.diahlo2.io
www.diabhlo2.io
www.diahblo2.io
www.dianlo2.io
www.diabnlo2.io
www.dianblo2.io
www.diabo2.io
www.diabpo2.io
www.diablpo2.io
www.diabplo2.io
www.diaboo2.io
www.diabloo2.io
www.diabolo2.io
www.diabko2.io
www.diablko2.io
www.diabklo2.io
www.diabl2.io
www.diabli2.io
www.diabloi2.io
www.diablio2.io
www.diablk2.io
www.diablok2.io
www.diabll2.io
www.diablol2.io
www.diabllo2.io
www.diablp2.io
www.diablop2.io
www.diablo.io