5e.tools Site Title
5etools
5e.tools Meta Description
A suite of browser-based tools for 5th Edition Dungeons & Dragons players and Dungeon Masters.
5e.tools Test Results
5e.tools Mobile Performance: 48/100
Quick overview:
Max Potential First Input Delay
350 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
8.3 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.
First Meaningful Paint
2.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.
Final Screenshot
The last screenshot captured of the pageload.
7586513194
Tasks
Lists the toplevel main thread tasks that executed during page load.
Script Treemap Data
Used for treemap app
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Diagnostics
Collection of useful page vitals.
5e.tools Mobile SEO: 90/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
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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
95% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
5e.tools Mobile Best Practices: 75/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection 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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
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.
5e.tools Mobile PWA: 100/100
Quick overview:
5e.tools Mobile Accessibility: 87/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.
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.
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.
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.
Similar sites
Similar tests
www.5e.com
www.5e.net
www.5e.org
www.5e.info
www.5e.biz
www.5e.us
www.5e.mobi
www.e.tools
www.5e.tools
www.5.tools
www.5w.tools
www.5ew.tools
www.5we.tools
www.5s.tools
www.5es.tools
www.5se.tools
www.5d.tools
www.5ed.tools
www.5de.tools
www.5r.tools
www.5er.tools
www.5re.tools
www.5e.net
www.5e.org
www.5e.info
www.5e.biz
www.5e.us
www.5e.mobi
www.e.tools
www.5e.tools
www.5.tools
www.5w.tools
www.5ew.tools
www.5we.tools
www.5s.tools
www.5es.tools
www.5se.tools
www.5d.tools
www.5ed.tools
www.5de.tools
www.5r.tools
www.5er.tools
www.5re.tools