Plus.co.jp Test Results

Plus.co.jp Mobile Performance: 33/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 339 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Potential savings of 120 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.
Minimize main-thread work
4.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
Eliminate render-blocking resources
Potential savings of 150 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 large layout shifts
3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Largest Contentful Paint element
7,940 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Potential savings of 2,160 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Properly size images
Potential savings of 31 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Enable text compression
Potential savings of 140 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Reduce the impact of third-party code
Third-party code blocked the main thread for 320 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.
Reduce initial server response time
Root document took 1,290 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.
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.
Minify CSS
Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 9 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
Serve static assets with an efficient cache policy
52 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid an excessive DOM size
1,124 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.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Time to Interactive
11.0 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.
Max Potential First Input Delay
340 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
2.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Plus.co.jp Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more about canonical links. Points to the domain's root URL (the homepage), instead of an equivalent page of content

Plus.co.jp Mobile Best Practices: 62/100
Quick overview:
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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
Plus.co.jp Mobile Accessibility: 79/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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.
Similar sites
Similar tests
www.plus.com
www.plus.net
www.plus.org
www.plus.info
www.plus.biz
www.plus.us
www.plus.mobi
www.lus.co.jp
www.plus.co.jp
www.olus.co.jp
www.polus.co.jp
www.oplus.co.jp
www.llus.co.jp
www.pllus.co.jp
www.lplus.co.jp
www.pus.co.jp
www.ppus.co.jp
www.plpus.co.jp
www.pplus.co.jp
www.pous.co.jp
www.plous.co.jp
www.pkus.co.jp
www.plkus.co.jp
www.pklus.co.jp
www.pls.co.jp
www.plys.co.jp
www.pluys.co.jp
www.plyus.co.jp
www.plhs.co.jp
www.pluhs.co.jp
www.plhus.co.jp
www.pljs.co.jp
www.plujs.co.jp
www.pljus.co.jp
www.plis.co.jp
www.pluis.co.jp
www.plius.co.jp
www.plu.co.jp
www.pluw.co.jp
www.plusw.co.jp
www.pluws.co.jp
www.plue.co.jp
www.pluse.co.jp
www.plues.co.jp
www.plud.co.jp
www.plusd.co.jp
www.pluds.co.jp
www.pluz.co.jp
www.plusz.co.jp
www.pluzs.co.jp
www.plux.co.jp
www.plusx.co.jp
www.pluxs.co.jp
www.plua.co.jp
www.plusa.co.jp
www.pluas.co.jp
Last Tested: