Hange.jp Test Results

Hange.jp Mobile Performance: 48/100
Quick overview:
Max Potential First Input Delay
400 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.
First Meaningful Paint
4.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
6.4 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.
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.
Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.
Script Treemap Data
Used for treemap app
Final Screenshot
The last screenshot captured of the pageload.

851864340730

Tasks
Lists the toplevel main thread tasks that executed during page load.
Diagnostics
Collection of useful page vitals.
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.

Hange.jp Mobile SEO: 80/100
Quick overview:
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.
Document doesn't use legible font sizes
51.02% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Tap targets are not sized appropriately
69% 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.
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

Hange.jp Mobile Best Practices: 83/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.
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
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 about this errors in console diagnostic audit
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.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Hange.jp Mobile PWA: 33/100
Quick overview:
PWA Optimized
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 about Service Workers.
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 about maskable manifest icons. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. 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 about splash screens. Failures: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Hange.jp Mobile Accessibility: 77/100
Quick overview:
Navigation
These are opportunities to improve keyboard navigation in your application.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
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.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. 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.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
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 tests
www.hange.com
www.hange.net
www.hange.org
www.hange.info
www.hange.biz
www.hange.us
www.hange.mobi
www.ange.jp
www.hange.jp
www.bange.jp
www.hbange.jp
www.bhange.jp
www.gange.jp
www.hgange.jp
www.ghange.jp
www.yange.jp
www.hyange.jp
www.yhange.jp
www.uange.jp
www.huange.jp
www.uhange.jp
www.jange.jp
www.hjange.jp
www.jhange.jp
www.nange.jp
www.hnange.jp
www.nhange.jp
www.hnge.jp
www.hqnge.jp
www.haqnge.jp
www.hqange.jp
www.hwnge.jp
www.hawnge.jp
www.hwange.jp
www.hsnge.jp
www.hasnge.jp
www.hsange.jp
www.hznge.jp
www.haznge.jp
www.hzange.jp
www.hage.jp
www.habge.jp
www.hanbge.jp
www.habnge.jp
www.hahge.jp
www.hanhge.jp
www.hahnge.jp
www.hajge.jp
www.hanjge.jp
www.hajnge.jp
www.hamge.jp
www.hanmge.jp
www.hamnge.jp
www.hane.jp
www.hanfe.jp
www.hangfe.jp
www.hanfge.jp
www.hanve.jp
www.hangve.jp
www.hanvge.jp
www.hante.jp
www.hangte.jp
www.hantge.jp
www.hanbe.jp
www.hangbe.jp
www.hanye.jp
www.hangye.jp
www.hanyge.jp
www.hanhe.jp
www.hanghe.jp
www.hang.jp
www.hangw.jp
www.hangew.jp
www.hangwe.jp
www.hangs.jp
www.hanges.jp
www.hangse.jp
www.hangd.jp
www.hanged.jp
www.hangde.jp
www.hangr.jp
www.hanger.jp
www.hangre.jp
Last Tested: