Tools & Wizards About Us
nepia.co.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    67% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

nepia.co.jp

ティシュ, トイレットペーパー, やわらかハート ネピア

Page Load Speed

4.9 sec in total

First Response

332 ms

Resources Loaded

4.1 sec

Page Rendered

442 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

やさしいティシュ。やさしさは、ふれればわかる。ネピアオフィシャルサイト。

Visit nepia.co.jp

Key Findings

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

Performance Metrics

nepia.co.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

www.nepia.co.jp

332 ms

base.css

164 ms

hf.css

307 ms

jquery.min.js

31 ms

jquery.cookie.js

332 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 92% of them (67 requests) were addressed to the original Nepia.co.jp, 4% (3 requests) were made to Www02.tracer.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Nepia.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

5.0 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nepia.co.jp main page is 5.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. 50% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 26.1 kB

  • Original 32.1 kB
  • After minification 26.6 kB
  • After compression 6.0 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 5.5 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 26.1 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 140.9 kB

  • Original 4.8 MB
  • After minification 4.7 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.

JavaScript Optimization

-60%

Potential reduce by 58.4 kB

  • Original 97.9 kB
  • After minification 91.1 kB
  • After compression 39.5 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 58.4 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 69.9 kB

  • Original 82.0 kB
  • After minification 68.4 kB
  • After compression 12.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. Nepia.co.jp needs all CSS files to be minified and compressed as it can save up to 69.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (15%)

Requests Now

72

After Optimization

61

  • Images
  • JavaScript
  • CSS

The browser has sent 72 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 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.nepia.co.jp

www.nepia.co.jp

332 ms

base.css

base.css

164 ms

hf.css

hf.css

307 ms

jquery.min.js

jquery.min.js

31 ms

jquery.cookie.js

jquery.cookie.js

332 ms

cssua.min.js

cssua.min.js

304 ms

jquery.common.js

jquery.common.js

333 ms

jquery.bxslider.css

jquery.bxslider.css

301 ms

top.css

top.css

336 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

472 ms

Trace

Trace

596 ms

bodyBg.png

bodyBg.png

519 ms

topBg.png

topBg.png

1044 ms

topBg_cloud.png

topBg_cloud.png

1045 ms

headBg.png

headBg.png

153 ms

headerBg.png

headerBg.png

299 ms

siteID.png

siteID.png

151 ms

sprite.png

sprite.png

1046 ms

mv5.jpg

mv5.jpg

1353 ms

mv14.jpg

mv14.jpg

1488 ms

mv16.jpg

mv16.jpg

1406 ms

mv15.jpg

mv15.jpg

1199 ms

mv11.jpg

mv11.jpg

1339 ms

mv10.jpg

mv10.jpg

1343 ms

mv9.jpg

mv9.jpg

1502 ms

mv8.jpg

mv8.jpg

1644 ms

mv3.jpg

mv3.jpg

1937 ms

mv14sp.jpg

mv14sp.jpg

1511 ms

mv16sp.jpg

mv16sp.jpg

1715 ms

mv15sp.jpg

mv15sp.jpg

1933 ms

mv11sp.jpg

mv11sp.jpg

1652 ms

mv10sp.jpg

mv10sp.jpg

1665 ms

mv9sp.jpg

mv9sp.jpg

1796 ms

mv8sp.jpg

mv8sp.jpg

1808 ms

mv3sp.jpg

mv3sp.jpg

1962 ms

mv5sp.jpg

mv5sp.jpg

2018 ms

ptnGray.png

ptnGray.png

1944 ms

icon_new_top.png

icon_new_top.png

1959 ms

pcCampaign06.jpg

pcCampaign06.jpg

2083 ms

pcCampaign07.jpg

pcCampaign07.jpg

2088 ms

pcCampaign01.jpg

pcCampaign01.jpg

2095 ms

spCampaign06.jpg

spCampaign06.jpg

2109 ms

spCampaign07.jpg

spCampaign07.jpg

2142 ms

spCampaign01.jpg

spCampaign01.jpg

2168 ms

pcQuality.png

pcQuality.png

2232 ms

pcQuality1.png

pcQuality1.png

2237 ms

analytics.js

analytics.js

22 ms

pcQuality2.png

pcQuality2.png

2206 ms

collect

collect

13 ms

VLJavaScript_bs.js

VLJavaScript_bs.js

590 ms

pcQuality3.png

pcQuality3.png

2114 ms

spQuality.png

spQuality.png

2145 ms

spQuality1.png

spQuality1.png

2025 ms

spQuality2.png

spQuality2.png

1868 ms

Trace

Trace

381 ms

spQuality3.png

spQuality3.png

1352 ms

pcTopProducts01.png

pcTopProducts01.png

1378 ms

spTopProducts01.png

spTopProducts01.png

1372 ms

pcTopProducts02.png

pcTopProducts02.png

1247 ms

spTopProducts02.png

spTopProducts02.png

1134 ms

spTopProducts_copyright.png

spTopProducts_copyright.png

1194 ms

pcTopProducts03.png

pcTopProducts03.png

1191 ms

spTopProducts03.png

spTopProducts03.png

1161 ms

footMenuBg.png

footMenuBg.png

1090 ms

brand5.png

brand5.png

1096 ms

brand1.png

brand1.png

1110 ms

brand2.png

brand2.png

1042 ms

brand3.png

brand3.png

1042 ms

brand4.png

brand4.png

1052 ms

corpLogo.png

corpLogo.png

1010 ms

bx_loader.gif

bx_loader.gif

953 ms

pdf.png

pdf.png

965 ms

pt_top.css

pt_top.css

153 ms

Accessibility Review

nepia.co.jp accessibility score

73

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

nepia.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    N/A

  • 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 neither this language nor any other was claimed in <html> or <meta> tags. 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 description is not detected on the main page of Nepia. 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: