Tools & Wizards About Us
napla.co.jp screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    48% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 85% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

napla.co.jp

ヘアカラーをはじめとするヘアケア製品の総合メーカー | 株式会社ナプラ

Page Load Speed

28.9 sec in total

First Response

1.4 sec

Resources Loaded

27 sec

Page Rendered

406 ms

napla.co.jp screenshot

About Website

Welcome to napla.co.jp homepage info - get ready to check Napla best content for Taiwan right away, or after learning these important things about napla.co.jp

業務用・プロ用のヘアケア製品の総合メーカー。美容室専売のシャンプー・トリートメント・ワックス・カラー剤・パーマ剤・ストレート(縮毛矯正)剤の製造。会社情報、製品情報、ナプラスタジオセミナー情報、各種採用情報など。

Visit napla.co.jp

Key Findings

We analyzed Napla.co.jp page load time and found that the first response time was 1.4 sec and then it took 27.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

napla.co.jp performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value110.3 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

www.napla.co.jp

1436 ms

style_141211.css

947 ms

prettyPhoto.css

792 ms

jquery.js

2873 ms

function.js

583 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 91% of them (89 requests) were addressed to the original Napla.co.jp, 3% (3 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Napla.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.4 kB (10%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 22.6 kB

  • Original 28.2 kB
  • After minification 23.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 15% 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.6 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 54.2 kB

  • Original 2.0 MB
  • After minification 1.9 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. Napla images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 82.6 kB

  • Original 136.3 kB
  • After minification 129.9 kB
  • After compression 53.8 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 82.6 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 55.0 kB

  • Original 63.7 kB
  • After minification 53.0 kB
  • After compression 8.7 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. Napla.co.jp needs all CSS files to be minified and compressed as it can save up to 55.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (26%)

Requests Now

95

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.napla.co.jp

www.napla.co.jp

1436 ms

style_141211.css

style_141211.css

947 ms

prettyPhoto.css

prettyPhoto.css

792 ms

jquery.js

jquery.js

2873 ms

function.js

function.js

583 ms

current.js

current.js

432 ms

heightline.js

heightline.js

624 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

852 ms

jquery.fitimage.js

jquery.fitimage.js

785 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1050 ms

jquery.dropdownplain.js

jquery.dropdownplain.js

955 ms

styleswitch.js

styleswitch.js

964 ms

jquery.cycle.js

jquery.cycle.js

1033 ms

jquery.cycle.option.js

jquery.cycle.option.js

1115 ms

ga.js

ga.js

367 ms

bg.jpg

bg.jpg

292 ms

logo.jpg

logo.jpg

523 ms

h_rec_off.jpg

h_rec_off.jpg

285 ms

gnav01_off.jpg

gnav01_off.jpg

1124 ms

gnav02_off.jpg

gnav02_off.jpg

288 ms

gnav02_01_off.png

gnav02_01_off.png

775 ms

gnav02_02_off.png

gnav02_02_off.png

523 ms

gnav02_03_off.png

gnav02_03_off.png

524 ms

gnav02_04_off.png

gnav02_04_off.png

528 ms

gnav02_05_off.png

gnav02_05_off.png

706 ms

gnav02_06_off.png

gnav02_06_off.png

711 ms

gnav02_07_off.png

gnav02_07_off.png

711 ms

gnav03_off.jpg

gnav03_off.jpg

718 ms

gnav04_off.jpg

gnav04_off.jpg

1190 ms

gnav04_01_off.png

gnav04_01_off.png

933 ms

gnav04_02_off.png

gnav04_02_off.png

931 ms

gnav04_03_off.png

gnav04_03_off.png

941 ms

gnav04_04_off.png

gnav04_04_off.png

1000 ms

gnav05_off.jpg

gnav05_off.jpg

2168 ms

gnav05_01_off.png

gnav05_01_off.png

1174 ms

gnav05_02_off.png

gnav05_02_off.png

1191 ms

gnav05_03_off.png

gnav05_03_off.png

1261 ms

gnav05_04_off.png

gnav05_04_off.png

1355 ms

gnav05_05_off.png

gnav05_05_off.png

1413 ms

gnav06_off.jpg

gnav06_off.jpg

1638 ms

2016DP_A.jpg

2016DP_A.jpg

8483 ms

4e8c9d6b0df07d3f06c0503296d23ad9.jpg

4e8c9d6b0df07d3f06c0503296d23ad9.jpg

11860 ms

NASEED-WAVE-A.jpg

NASEED-WAVE-A.jpg

4103 ms

NASEED-COLOR-A.jpg

NASEED-COLOR-A.jpg

4529 ms

OGyakuyouA.jpg

OGyakuyouA.jpg

4521 ms

NAPURHP980_324.gif

NAPURHP980_324.gif

6888 ms

mainimage1.jpg

mainimage1.jpg

11723 ms

be9a5705aca505c24b9ff2f75043d3e8.gif

be9a5705aca505c24b9ff2f75043d3e8.gif

20448 ms

c32c05ef68a2ded6e240dd92dcb27f66.gif

c32c05ef68a2ded6e240dd92dcb27f66.gif

20448 ms

top_btn01_off.jpg

top_btn01_off.jpg

9110 ms

widgets.js

widgets.js

416 ms

top_btn02_off.jpg

top_btn02_off.jpg

9299 ms

top_btn03_off.jpg

top_btn03_off.jpg

10021 ms

top_btn04_off.jpg

top_btn04_off.jpg

9919 ms

top_btn05_off.jpg

top_btn05_off.jpg

10312 ms

__utm.gif

__utm.gif

132 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

270 ms

top_btn06_off.jpg

top_btn06_off.jpg

10739 ms

bba02ed17e17097036012d7d0f914bc2.jpg

bba02ed17e17097036012d7d0f914bc2.jpg

10488 ms

like.php

like.php

369 ms

2016DP_G.jpg

2016DP_G.jpg

10931 ms

nav_napur_off.jpg

nav_napur_off.jpg

11155 ms

link_monchareaut-1.jpg

link_monchareaut-1.jpg

11135 ms

link_joange-1.jpg

link_joange-1.jpg

11498 ms

nav04_off.jpg

nav04_off.jpg

11365 ms

nav02_off.jpg

nav02_off.jpg

11301 ms

nav07_off.jpg

nav07_off.jpg

11495 ms

tweet_button.fd774b599f565016d763dd860cb31c79.ja.html

tweet_button.fd774b599f565016d763dd860cb31c79.ja.html

319 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

601 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

646 ms

nav01_off.jpg

nav01_off.jpg

11276 ms

nav03_off.jpg

nav03_off.jpg

11512 ms

top_box_top01.jpg

top_box_top01.jpg

11484 ms

ichiran_off.jpg

ichiran_off.jpg

11419 ms

top_box_top03.jpg

top_box_top03.jpg

11353 ms

imprime_art.jpg

imprime_art.jpg

11426 ms

top_box_top02.jpg

top_box_top02.jpg

11424 ms

089e803a03cfcbea23d010abde2850bb.jpg

089e803a03cfcbea23d010abde2850bb.jpg

13203 ms

jot

jot

333 ms

flogo.jpg

flogo.jpg

11400 ms

nav_bg02.jpg

nav_bg02.jpg

11638 ms

nav_bg01.jpg

nav_bg01.jpg

11177 ms

top_box_bg01.jpg

top_box_bg01.jpg

9256 ms

arr.jpg

arr.jpg

8947 ms

new.jpg

new.jpg

8988 ms

top_box_btm01.jpg

top_box_btm01.jpg

6646 ms

top_box_bg02.jpg

top_box_bg02.jpg

5179 ms

top_box_btm03.jpg

top_box_btm03.jpg

4587 ms

top_box_bg03.jpg

top_box_bg03.jpg

4290 ms

top_box_btm02.jpg

top_box_btm02.jpg

3666 ms

pagetop_off.png

pagetop_off.png

3589 ms

fbg.jpg

fbg.jpg

3312 ms

gnav01_on.jpg

gnav01_on.jpg

3088 ms

prev.png

prev.png

2766 ms

next.png

next.png

2657 ms

www.napla.co.jp

www.napla.co.jp

1686 ms

www.napla.co.jp

www.napla.co.jp

1979 ms

www.napla.co.jp

www.napla.co.jp

828 ms

Accessibility Review

napla.co.jp accessibility score

94

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

napla.co.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

napla.co.jp SEO score

92

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

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

napla.co.jp

Open Graph description is not detected on the main page of Napla. 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: