Access nealsyard.co.jp. 公式ニールズヤードレメディーズ

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value6,540 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.767

5/100

15%

TTI (Time to Interactive)

Value45.0 s

0/100

10%

nealsyard.co.jp

1080 ms

apache_pb2.gif

398 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Nealsyard.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Nealsyard.co.jp.

Content Size

4.0 kB

After Optimization

1.5 kB

In fact, the total size of Nealsyard.co.jp main page is 4.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 4.0 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 2.4 kB

Original 4.0 kB
After minification 3.8 kB
After compression 1.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 2.4 kB or 61% of the original size.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NEAL S YARD. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nealsyard.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Nealsyard.co.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nealsyard.co.jp

Open Graph description is not detected on the main page of NEAL S YARD. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: