Door.ntt Site Title
DOOR 開け。次の世界 -
Door.ntt Meta Description
DOOR 開け。次の世界
Door.ntt Test Results
Door.ntt Mobile Performance: 29/100
Quick overview:
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 3,258 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Remove unused JavaScript. Potential savings of 366 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Defer offscreen images. Potential savings of 1,401 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Reduce initial server response time. Root document took 1,230 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Eliminate render-blocking resources. Potential savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 6 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 More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
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.
Avoid enormous network payloads
Total size was 4,377 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Minimize main-thread work
3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
11 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
33 requests • 4,377 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Door.ntt Mobile SEO: 90/100
Quick overview:
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.
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
75% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Door.ntt Mobile Best Practices: 79/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 servedover 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.
General
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
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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Door.ntt Mobile Progressive Web App: 25/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 11.2 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
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 servedover 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.
Door.ntt Mobile Accessibility: 86/100
Quick overview:
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.
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.
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 more.
Similar sites
Similar tests
www.door.com
www.door.net
www.door.org
www.door.info
www.door.biz
www.door.us
www.door.mobi
www.oor.ntt
www.door.ntt
www.xoor.ntt
www.dxoor.ntt
www.xdoor.ntt
www.soor.ntt
www.dsoor.ntt
www.sdoor.ntt
www.eoor.ntt
www.deoor.ntt
www.edoor.ntt
www.roor.ntt
www.droor.ntt
www.rdoor.ntt
www.foor.ntt
www.dfoor.ntt
www.fdoor.ntt
www.coor.ntt
www.dcoor.ntt
www.cdoor.ntt
www.dor.ntt
www.dior.ntt
www.doior.ntt
www.dioor.ntt
www.dkor.ntt
www.dokor.ntt
www.dkoor.ntt
www.dlor.ntt
www.dolor.ntt
www.dloor.ntt
www.dpor.ntt
www.dopor.ntt
www.dpoor.ntt
www.doir.ntt
www.dooir.ntt
www.dokr.ntt
www.dookr.ntt
www.dolr.ntt
www.doolr.ntt
www.dopr.ntt
www.doopr.ntt
www.doo.ntt
www.dooe.ntt
www.doore.ntt
www.dooer.ntt
www.dood.ntt
www.doord.ntt
www.doodr.ntt
www.doof.ntt
www.doorf.ntt
www.doofr.ntt
www.doot.ntt
www.doort.ntt
www.dootr.ntt
www.door.net
www.door.org
www.door.info
www.door.biz
www.door.us
www.door.mobi
www.oor.ntt
www.door.ntt
www.xoor.ntt
www.dxoor.ntt
www.xdoor.ntt
www.soor.ntt
www.dsoor.ntt
www.sdoor.ntt
www.eoor.ntt
www.deoor.ntt
www.edoor.ntt
www.roor.ntt
www.droor.ntt
www.rdoor.ntt
www.foor.ntt
www.dfoor.ntt
www.fdoor.ntt
www.coor.ntt
www.dcoor.ntt
www.cdoor.ntt
www.dor.ntt
www.dior.ntt
www.doior.ntt
www.dioor.ntt
www.dkor.ntt
www.dokor.ntt
www.dkoor.ntt
www.dlor.ntt
www.dolor.ntt
www.dloor.ntt
www.dpor.ntt
www.dopor.ntt
www.dpoor.ntt
www.doir.ntt
www.dooir.ntt
www.dokr.ntt
www.dookr.ntt
www.dolr.ntt
www.doolr.ntt
www.dopr.ntt
www.doopr.ntt
www.doo.ntt
www.dooe.ntt
www.doore.ntt
www.dooer.ntt
www.dood.ntt
www.doord.ntt
www.doodr.ntt
www.doof.ntt
www.doorf.ntt
www.doofr.ntt
www.doot.ntt
www.doort.ntt
www.dootr.ntt