Analyze

hikari-n.jp: フレッツ光/NTT | インターネット光回線

フレッツ光の新規お申し込みサイトです。インターネット、Wi-Fi(無線LAN)IP電話ならフレッツ光。NTT東日本・NTT西日本販売代理店ネットナビ

Page load speed analysis

  • 67/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    453 ms

  • Resources loaded

    8.9 sec

  • Page rendered

    431 ms

  • Total page load time

    9.8 sec

Welcome to hikari-n.jp homepage info - get ready to check Hikari N best content for Japan right away, or after learning these important things about hikari-n.jp

We analyzed Hikari-n.jp page load time and found that the first response time was 453 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Page optimization

  • HTML 29.7 kB
    Images 1.3 MB
    Javascripts 256.6 kB
    CSS 21.4 kB

    In fact, the total size of Hikari-n.jp main page is 1.6 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 1.3 MB which makes up the majority of the site volume.

    • Original 29.7 kB
    • After minification 28.0 kB
    • After compression 6.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.1 kB or 78% of the original size.

    • Original 1.3 MB
    • After optimization 1.2 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. Hikari N images are well optimized though.

    • Original 256.6 kB
    • After minification 255.0 kB
    • After compression 89.4 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 167.2 kB or 65% of the original size.

    • Original 21.4 kB
    • After minification 21.2 kB
    • After compression 5.1 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. Hikari-n.jp needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 76% of the original size.

Network requests diagram

  • hikari-n.jp
  • hikari-n.jp
  • common.css
  • index.css
  • shadowbox.css
  • jquery.min.js
  • heightLine.js
  • common.js
  • shadowbox.js
  • m.js
  • ic-top.png
  • ic-service.png
  • ic-plan.png
  • ic-provider.png
  • ic-campaign.png
  • ic-faq.png
  • follow-header-campaign.png
  • header-support.png
  • head-logo.png
  • icon-head-reservation.png
  • btn-head-tel.png
  • mainv1.png
  • banner-east.png
  • ribon-east.png
  • banner-west.png
  • ribon-west.png
  • banner-collabo.png
  • ribon-collabo.png
  • hikari-denwa.png
  • flets-tv.png
  • security.png
  • support.png
  • btn-west.png
  • btn-east.png
  • rapidssl-seal.png
  • sbs-icon.png
  • spsite-banner.png
  • title-select-area.png
  • img-select-area.png
  • gtm.js
  • fd.png
  • arrow-b.png
  • h-flets-hikari-bg.png
  • arrow-white-right.png
  • h-option-bg.png
  • arrow-pagetop.png
  • icon-foot-area.png
  • 557a97e5-867c-4665-9a13-0408ac1f5756.json
  • brick.js
  • tag.js
  • fbds.js
  • pre
  • conversion_async.js
  • tag
  • cast-mark-j.adtdp.com
  • analytics.js
  • s_retargeting.js
  • UA-29207634-10.js
  • linkid.js
  • mark
  • collect
  • collect
  • brick.heatmap.js
  • sync
  • allcsync.js
  • cookiesync
  • brick.lib.js
  • xrost
  • sync.ad
  • adstir
  • s.kau.li
  • pixel
  • mediba
  • compass
  • sync
  • google
  • sd
  • brick.heatmap_base.js
  • gcs
  • ya.js
  • conversion.js
  • sync.php
  • sync.php
  • pb.js
  • collect
  • collect
  • conversion.js

Our browser made a total of 100 requests to load all elements on the main page. We found that 44% of them (44 requests) were addressed to the original Hikari-n.jp, 6% (6 requests) were made to Bs.nakanohito.jp and 6% (6 requests) were made to Cast-cs-j.adtdp.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Hikari-n.jp.

Additional info on hikari-n.jp

Requests

The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hikari N. 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 as a result speed up the page load time.

26

Javascripts

63

Images

3

CSS

1

AJAX

93

All

Possible request optimization

1

Javascripts

30

Images

3

CSS

1

AJAX

58

Optimized

35

All

Normal result

Redirects

As for redirects, our browser was forwarded to https://hikari-n.jp/ before it reached this domain.

IP address

This IP address is dedicated to Hikari-n.jp. This is the best domain hosting practice .

Normal result

IP Trace

hikari-n.jp

52.198.211.112

52.199.108.252

DNS records

Type Host Target/ip TTL Other
A

hikari-n.jp

52.198.211.112 60
A

hikari-n.jp

52.199.108.252 60
NS

hikari-n.jp

ns-1131.awsdns-13.org 86400
NS

hikari-n.jp

ns-1860.awsdns-40.co.uk 86400
NS

hikari-n.jp

ns-425.awsdns-53.com 86400

Language and encoding

Good result

Language

JA ja 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 Hikari-n.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 Hikari-n.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

Hikari-n.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 100% of all visits is Japan. It’s good for Hikari-n.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Good result

Social Sharing Optimization

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

hikari-n.jp

Share this report in social media

Analyze another website

Analyze