Analyze

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

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

Page load speed analysis

  • 39/100

    Normal result
  • 4

    Successful tests
  • 4

    Failed tests
  • First response

    1.4 sec

  • Resources loaded

    27 sec

  • Page rendered

    406 ms

  • Total page load time

    28.9 sec

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

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 an excellent result, as only a small number 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.

Page optimization

  • HTML 28.2 kB
    Images 2.0 MB
    Javascripts 162.2 kB
    CSS 63.7 kB

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

    • Original 28.2 kB
    • After minification 23.9 kB
    • After compression 5.5 kB

    HTML optimization

    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.

    • Original 2.0 MB
    • After optimization 1.9 MB

    Image optimization

    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.

    • Original 162.2 kB
    • After minification 155.8 kB
    • After compression 52.6 kB

    JavaScript optimization

    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 109.6 kB or 68% of the original size.

    • Original 63.7 kB
    • After minification 53.0 kB
    • After compression 8.7 kB

    CSS optimization

    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.

Network requests diagram

  • www.napla.co.jp
  • style_141211.css
  • prettyPhoto.css
  • jquery.js
  • function.js
  • current.js
  • heightline.js
  • jquery.bxSlider.min.js
  • jquery.fitimage.js
  • jquery.prettyPhoto.js
  • jquery.dropdownplain.js
  • styleswitch.js
  • jquery.cycle.js
  • jquery.cycle.option.js
  • ga.js
  • bg.jpg
  • logo.jpg
  • h_rec_off.jpg
  • gnav01_off.jpg
  • gnav02_off.jpg
  • gnav02_01_off.png
  • gnav02_02_off.png
  • gnav02_03_off.png
  • gnav02_04_off.png
  • gnav02_05_off.png
  • gnav02_06_off.png
  • gnav02_07_off.png
  • gnav03_off.jpg
  • gnav04_off.jpg
  • gnav04_01_off.png
  • gnav04_02_off.png
  • gnav04_03_off.png
  • gnav04_04_off.png
  • gnav05_off.jpg
  • gnav05_01_off.png
  • gnav05_02_off.png
  • gnav05_03_off.png
  • gnav05_04_off.png
  • gnav05_05_off.png
  • gnav06_off.jpg
  • 2016DP_A.jpg
  • 4e8c9d6b0df07d3f06c0503296d23ad9.jpg
  • NASEED-WAVE-A.jpg
  • NASEED-COLOR-A.jpg
  • OGyakuyouA.jpg
  • NAPURHP980_324.gif
  • mainimage1.jpg
  • be9a5705aca505c24b9ff2f75043d3e8.gif
  • c32c05ef68a2ded6e240dd92dcb27f66.gif
  • top_btn01_off.jpg
  • widgets.js
  • top_btn02_off.jpg
  • top_btn03_off.jpg
  • top_btn04_off.jpg
  • top_btn05_off.jpg
  • __utm.gif
  • button.71000885400e222c3c0eec823f8f93f0.js
  • top_btn06_off.jpg
  • bba02ed17e17097036012d7d0f914bc2.jpg
  • like.php
  • 2016DP_G.jpg
  • nav_napur_off.jpg
  • link_monchareaut-1.jpg
  • link_joange-1.jpg
  • nav04_off.jpg
  • nav02_off.jpg
  • nav07_off.jpg
  • tweet_button.fd774b599f565016d763dd860cb31c79.ja.html
  • Sh_BYjerrZ8.js
  • LVx-xkvaJ0b.png
  • nav01_off.jpg
  • nav03_off.jpg
  • top_box_top01.jpg
  • ichiran_off.jpg
  • top_box_top03.jpg
  • imprime_art.jpg
  • top_box_top02.jpg
  • 089e803a03cfcbea23d010abde2850bb.jpg
  • jot
  • flogo.jpg
  • nav_bg02.jpg
  • nav_bg01.jpg
  • top_box_bg01.jpg
  • arr.jpg
  • new.jpg
  • top_box_btm01.jpg
  • top_box_bg02.jpg
  • top_box_btm03.jpg
  • top_box_bg03.jpg
  • top_box_btm02.jpg
  • pagetop_off.png
  • fbg.jpg
  • gnav01_on.jpg
  • prev.png
  • next.png
  • www.napla.co.jp
  • www.napla.co.jp
  • www.napla.co.jp

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.

Additional info on napla.co.jp

Requests

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.

15

Javascripts

73

Images

2

CSS

5

AJAX

95

All

Possible request optimization

1

Javascripts

62

Images

2

CSS

5

AJAX

25

Optimized

70

All

Normal result

IP address

This IP address is dedicated to Napla.co.jp. This is the best domain hosting practice .

Normal result

IP Trace

napla.co.jp

150.60.197.59

DNS records

Type Host Target/ip TTL Other
A

napla.co.jp

150.60.197.59 600
NS

napla.co.jp

ns00.vips.ne.jp 600
NS

napla.co.jp

ns01.vips.ne.jp 600
SOA

napla.co.jp

600 Mname: ns00.vips.ne.jp
Rname: helpdesk.jens.jp
Serial: 2019011101
Refresh: 10800
Retry: 1800
Expire: 1209600
Minimum-ttl: 3600
MX

napla.co.jp

ALT1.ASPMX.L.GOOGLE.COM 600 Pri: 10

Language and encoding

Normal result

Language

N/A  language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

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. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. 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.

HTTPS certificate

SSL Certificate

Napla.co.jp has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 23.3% of all visits is Taiwan. It lies approximately 1400 miles away from the server location (Japan) and such a distance cannot critically affect website speed, but moving the server closer to their user base in Taiwan can speed up Napla.co.jp page load time anyway.

Normal result

Poor result

Social Sharing Optimization

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:

napla.co.jp

Share this report in social media

Analyze another website

Analyze