Battle.net Blizzard Entertainment
battle.net Mobile Performance
27/100
These metrics represent real-world Chrome users experience viewing battle.net on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Largest Contentful Paint
Cumulative Layout Shift
First Contentful Paint
First Input Delay
Metrics
Largest Contentful Paint0/100 12.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive4/100 17.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index27/100 7.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time41/100 690 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
First Contentful Paint49/100 4.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift87/100 0.113
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (20)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 6,479 KiB
33,510 ms
Efficiently encode images
Potential savings of 3,577 KiB
18,990 ms
Defer offscreen images
Potential savings of 3,237 KiB
8,400 ms
Remove unused JavaScript
Potential savings of 136 KiB
1,870 ms
Avoid multiple page redirects
Potential savings of 1,410 ms
1,410 ms
Remove unused CSS
Potential savings of 90 KiB
600 ms
Eliminate render-blocking resources
Potential savings of 480 ms
480 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 560 ms
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
88 resources found
Avoid enormous network payloads
Total size was 12,429 KiB
Avoid an excessive DOM size
1,750 elements
Minimize main-thread work
4.8 s
Reduce JavaScript execution time
1.9 s
Avoid chaining critical requests
12 chains found
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
155 requests • 12,429 KiB
User Timing marks and measures
1 user timing
Avoid large layout shifts
1 element found
Avoid long main-thread tasks
11 long tasks found
Passed Audits (10)
Properly size images
Minify JavaScript
Avoids `document.write()`
Uses passive listeners to improve scrolling performance
Preconnect to required origins
Preload key requests
Enable text compression
Minify CSS
Use video formats for animated content
Initial server response time was short
Root document took 450 ms
battle.net Mobile SEO
81/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (3)
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
63% appropriately sized tap targets
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
6 links found
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Passed Audits (10)
Document uses legible font sizes
68.63% legible text
Document has a meta description
Document has a valid `hreflang`
Document avoids plugins
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Image elements have `[alt]` attributes
Page isn’t blocked from indexing
Document has a `<title>` element
robots.txt is valid
Page has successful HTTP status code
battle.net Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of battle.net mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
User Experience
Serves images with low resolution
Trust and Safety
Links to cross-origin destinations are unsafe
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Passed Audits (10)
Detected JavaScript libraries
Avoids Application Cache
Avoids deprecated APIs
Properly defines charset
Allows users to paste into password fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
No browser errors logged to the console
Page has the HTML doctype
Displays images with correct aspect ratio
battle.net Mobile Progressive Web App
21/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (10)
Installable
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
1 insecure request found
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 17.7 s
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
PWA Optimized
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Does not provide a valid `apple-touch-icon`
Is not configured for a custom splash screen
Passed Audits (4)
Content is sized correctly for the viewport
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
battle.net Mobile Accessibility
91/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (2)
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
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
Passed Audits (21)
`[aria-*]` attributes have valid values
`<html>` element has a `[lang]` attribute
The page contains a heading, skip link, or landmark region
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` elements do not contain focusable descendents
No element has a `[tabindex]` value greater than 0
Buttons have an accessible name
Image elements have `[alt]` attributes
`<html>` element has a valid value for its `[lang]` attribute
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Document has a `<title>` element
ARIA IDs are unique
`[role]`s are contained by their required parent element
`[lang]` attributes have a valid value
Background and foreground colors have a sufficient contrast ratio
`[role]`s have all required `[aria-*]` attributes
`[aria-*]` attributes are valid and not misspelled
Heading elements appear in a sequentially-descending order
`[role]` values are valid
`[aria-hidden="true"]` is not present on the document `<body>`
`[id]` attributes on active, focusable elements are unique
Mobile Usability
95/100
These checks validate how easily a visitor can use battle.net on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (2)
Size content to viewport
Size tap targets appropriately
Passed Audits (3)
Avoid plugins
Configure the viewport
Use legible font sizes
Mobile Speed
7/100
These checks analyze the performance of battle.net on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (7)
Optimize images
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Prioritize visible content
Avoid landing page redirects
Minify JavaScript
Enable compression
Passed Audits (3)
Reduce server response time
Minify CSS
Minify HTML
www.battle.com
www.battle.net
www.battle.org
www.battle.info
www.battle.biz
www.battle.us
www.battle.mobi
www.attle.net
www.battle.net
www.vattle.net
www.bvattle.net
www.vbattle.net
www.gattle.net
www.bgattle.net
www.gbattle.net
www.hattle.net
www.bhattle.net
www.hbattle.net
www.nattle.net
www.bnattle.net
www.nbattle.net
www.bttle.net
www.bqttle.net
www.baqttle.net
www.bqattle.net
www.bwttle.net
www.bawttle.net
www.bwattle.net
www.bsttle.net
www.basttle.net
www.bsattle.net
www.bzttle.net
www.bazttle.net
www.bzattle.net
www.batle.net
www.bartle.net
www.batrtle.net
www.barttle.net
www.baftle.net
www.batftle.net
www.bafttle.net
www.bagtle.net
www.batgtle.net
www.bagttle.net
www.baytle.net
www.batytle.net
www.bayttle.net
www.batrle.net
www.battrle.net
www.batfle.net
www.battfle.net
www.batgle.net
www.battgle.net
www.batyle.net
www.battyle.net
www.batte.net
www.battpe.net
www.battlpe.net
www.battple.net
www.battoe.net
www.battloe.net
www.battole.net
www.battke.net
www.battlke.net
www.battkle.net
www.battl.net
www.battlw.net
www.battlew.net
www.battlwe.net
www.battls.net
www.battles.net
www.battlse.net
www.battld.net
www.battled.net
www.battlde.net
www.battlr.net
www.battler.net
www.battlre.net
www.battle.net
www.battle.org
www.battle.info
www.battle.biz
www.battle.us
www.battle.mobi
www.attle.net
www.battle.net
www.vattle.net
www.bvattle.net
www.vbattle.net
www.gattle.net
www.bgattle.net
www.gbattle.net
www.hattle.net
www.bhattle.net
www.hbattle.net
www.nattle.net
www.bnattle.net
www.nbattle.net
www.bttle.net
www.bqttle.net
www.baqttle.net
www.bqattle.net
www.bwttle.net
www.bawttle.net
www.bwattle.net
www.bsttle.net
www.basttle.net
www.bsattle.net
www.bzttle.net
www.bazttle.net
www.bzattle.net
www.batle.net
www.bartle.net
www.batrtle.net
www.barttle.net
www.baftle.net
www.batftle.net
www.bafttle.net
www.bagtle.net
www.batgtle.net
www.bagttle.net
www.baytle.net
www.batytle.net
www.bayttle.net
www.batrle.net
www.battrle.net
www.batfle.net
www.battfle.net
www.batgle.net
www.battgle.net
www.batyle.net
www.battyle.net
www.batte.net
www.battpe.net
www.battlpe.net
www.battple.net
www.battoe.net
www.battloe.net
www.battole.net
www.battke.net
www.battlke.net
www.battkle.net
www.battl.net
www.battlw.net
www.battlew.net
www.battlwe.net
www.battls.net
www.battles.net
www.battlse.net
www.battld.net
www.battled.net
www.battlde.net
www.battlr.net
www.battler.net
www.battlre.net