Tools & Wizards About Us
nepia.co.jp screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nepia.co.jp

人と地球に、ここちいい。｜【森のnepia】王子ネピア

Page Load Speed

5.8 sec in total

First Response

349 ms

Resources Loaded

4.8 sec

Page Rendered

700 ms

nepia.co.jp screenshot

About Website

Click here to check amazing Nepia content for Japan. Otherwise, check out these important facts you probably never knew about nepia.co.jp

人や暮らしだけでなく、私たちが生きる地球も見つめて。ふだんの暮らしに寄り添い、すべての毎日を支え続ける。【森のnepia】王子ネピアのオフィシャルサイトです。

Visit nepia.co.jp

Key Findings

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

Performance Metrics

nepia.co.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value21.6 s

0/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value610 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

nepia.co.jp

349 ms

www.nepia.co.jp

693 ms

slick.css

50 ms

top.css

346 ms

vegas.min.css

59 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 81% of them (48 requests) were addressed to the original Nepia.co.jp, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Nepia.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.2 kB (3%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images

In fact, the total size of Nepia.co.jp main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 22.0 kB

  • Original 26.2 kB
  • After minification 18.4 kB
  • After compression 4.2 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 7.8 kB, which is 30% 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 22.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 11.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. Nepia images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 10 (18%)

Requests Now

57

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nepia.co.jp

nepia.co.jp

349 ms

www.nepia.co.jp

www.nepia.co.jp

693 ms

slick.css

slick.css

50 ms

top.css

top.css

346 ms

vegas.min.css

vegas.min.css

59 ms

jquery-3.7.1.js

jquery-3.7.1.js

43 ms

slick.min.js

slick.min.js

61 ms

vegas.min.js

vegas.min.js

71 ms

slick-slide.js

slick-slide.js

515 ms

kv-slide.js

kv-slide.js

517 ms

main.js

main.js

525 ms

css2

css2

41 ms

notosansjp.css

notosansjp.css

65 ms

gtm.js

gtm.js

163 ms

top.svg

top.svg

177 ms

sprite.svg

sprite.svg

264 ms

logo.svg

logo.svg

267 ms

%E3%80%90%E3%82%AD%E3%83%BC%E3%83%93%E3%82%B8%E3%83%A5%E3%82%A2%E3%83%AB%E3%83%90%E3%83%8A%E3%83%BC%E3%80%91800x500_0409.jpg

%E3%80%90%E3%82%AD%E3%83%BC%E3%83%93%E3%82%B8%E3%83%A5%E3%82%A2%E3%83%AB%E3%83%90%E3%83%8A%E3%83%BC%E3%80%91800x500_0409.jpg

1095 ms

%E3%80%90%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B3%E3%83%90%E3%83%8A%E3%83%BC%E3%80%91800x500_0409.jpg

%E3%80%90%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B3%E3%83%90%E3%83%8A%E3%83%BC%E3%80%91800x500_0409.jpg

1506 ms

bottom.svg

bottom.svg

431 ms

toppage-catch.webp

toppage-catch.webp

434 ms

bg-mid-sec.webp

bg-mid-sec.webp

3330 ms

value-img01.webp

value-img01.webp

1337 ms

value-bg01.webp

value-bg01.webp

765 ms

value-bg02.png

value-bg02.png

601 ms

value-img02.webp

value-img02.webp

1101 ms

product-bg.webp

product-bg.webp

932 ms

prodact01.webp

prodact01.webp

1432 ms

prodact02.webp

prodact02.webp

1270 ms

prodact07.webp

prodact07.webp

1271 ms

prodact03.webp

prodact03.webp

1445 ms

prodact04.webp

prodact04.webp

1440 ms

prodact22.webp

prodact22.webp

1510 ms

prodact05.webp

prodact05.webp

1764 ms

prodact21.webp

prodact21.webp

1611 ms

home-mask01.png

home-mask01.png

1620 ms

prodact10.webp

prodact10.webp

1672 ms

prodact08.webp

prodact08.webp

1678 ms

prodact09.webp

prodact09.webp

1780 ms

prodact20.webp

prodact20.webp

1792 ms

prodact11.webp

prodact11.webp

2003 ms

prodact12.webp

prodact12.webp

1849 ms

prodact13.webp

prodact13.webp

1932 ms

prodact14.webp

prodact14.webp

1949 ms

prodact15.webp

prodact15.webp

1964 ms

prodact16.webp

prodact16.webp

2017 ms

prodact17.webp

prodact17.webp

2108 ms

font

font

55 ms

font

font

60 ms

font

font

83 ms

prodact18.webp

prodact18.webp

2032 ms

pdf-icon.svg

pdf-icon.svg

2042 ms

bn-top01.webp

bn-top01.webp

2075 ms

icon-line.svg

icon-line.svg

2016 ms

icon-x.svg

icon-x.svg

2019 ms

dot.png

dot.png

2023 ms

top_kv_01.webp

top_kv_01.webp

2047 ms

top_kv_02.webp

top_kv_02.webp

2412 ms

top_kv_03.webp

top_kv_03.webp

2091 ms

Accessibility Review

nepia.co.jp accessibility score

80

Accessibility Issues

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-hidden="true"] elements contain focusable descendents

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

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.

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

nepia.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

Page has valid source maps

SEO Factors

nepia.co.jp SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Nepia.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 Nepia.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

nepia.co.jp

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