Tools & Wizards About Us

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

nealsyard.co.jp

公式ニールズヤード レメディーズ | NEAL'S YARD REMEDIES

Page Load Speed

13.6 sec in total

First Response

554 ms

Resources Loaded

11.3 sec

Page Rendered

1.7 sec

About Website

Visit nealsyard.co.jp now to see the best up-to-date NEAL S YARD content for Japan and also check out these interesting facts you probably never knew about nealsyard.co.jp

ニールズヤード公式オンラインショップ。ブランド最新情報やスクール、サロン。健康で美しいライフスタイルを提案する英国発のヘルス&ビューティブランド。

Visit nealsyard.co.jp

Key Findings

We analyzed Nealsyard.co.jp page load time and found that the first response time was 554 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nealsyard.co.jp performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.3 s

0/100

25%

SI (Speed Index)

Value47.1 s

0/100

10%

TBT (Total Blocking Time)

Value46,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.581

11/100

15%

TTI (Time to Interactive)

Value96.6 s

0/100

10%

Network Requests Diagram

nealsyard.co.jp

554 ms

nealsyard.co.jp

699 ms

www.nealsyard.co.jp

1161 ms

fs_style.css

1449 ms

fs_theme.css

2150 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 5% of them (6 requests) were addressed to the original Nealsyard.co.jp, 48% (56 requests) were made to Nyrjp.itembox.design and 7% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Nyrjp.itembox.design.

Page Optimization Overview & Recommendations

Page size can be reduced by 445.1 kB (6%)

Content Size

7.0 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nealsyard.co.jp main page is 7.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 118.5 kB

  • Original 138.1 kB
  • After minification 115.2 kB
  • After compression 19.6 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. This page needs HTML code to be minified as it can gain 22.9 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 118.5 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 266.4 kB

  • Original 6.2 MB
  • After minification 6.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. NEAL S YARD images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 56.3 kB

  • Original 436.4 kB
  • After minification 436.3 kB
  • After compression 380.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 56.3 kB or 13% of the original size.

CSS Optimization

-2%

Potential reduce by 3.9 kB

  • Original 162.0 kB
  • After minification 162.0 kB
  • After compression 158.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Nealsyard.co.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (50%)

Requests Now

102

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NEAL S YARD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

nealsyard.co.jp accessibility score

68

Accessibility Issues

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

nealsyard.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

nealsyard.co.jp SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • 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 matches the claimed 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

Open Graph data is detected on the main page of NEAL S YARD. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: