Tools & Wizards About Us
hikari-n.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

hikari-n.jp

フレッツ光／NTT | インターネット光回線

Page Load Speed

7.2 sec in total

First Response

9 ms

Resources Loaded

6.9 sec

Page Rendered

281 ms

hikari-n.jp screenshot

About Website

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

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

Visit hikari-n.jp

Key Findings

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

Performance Metrics

hikari-n.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

hikari-n.jp

9 ms

hikari-n.jp

795 ms

c44f32e3a29c641c519d9381179f7650.js

37 ms

js

69 ms

common.css

961 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 59% of them (66 requests) were addressed to the original Hikari-n.jp, 27% (30 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Sp-trk.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Hikari-n.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.7 kB (14%)

Content Size

855.6 kB

After Optimization

737.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hikari-n.jp main page is 855.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 629.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 34.8 kB

  • Original 45.2 kB
  • After minification 42.4 kB
  • After compression 10.4 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. 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 34.8 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 32.9 kB

  • Original 629.9 kB
  • After minification 596.9 kB

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.

JavaScript Optimization

-30%

Potential reduce by 49.8 kB

  • Original 166.3 kB
  • After minification 166.2 kB
  • After compression 116.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 49.8 kB or 30% of the original size.

CSS Optimization

-1%

Potential reduce by 145 B

  • Original 14.3 kB
  • After minification 14.3 kB
  • After compression 14.2 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. Hikari-n.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 71 (65%)

Requests Now

109

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hikari-n.jp

hikari-n.jp

9 ms

hikari-n.jp

hikari-n.jp

795 ms

c44f32e3a29c641c519d9381179f7650.js

c44f32e3a29c641c519d9381179f7650.js

37 ms

js

js

69 ms

common.css

common.css

961 ms

index.css

index.css

962 ms

shadowbox.css

shadowbox.css

726 ms

showtalk.js

showtalk.js

1278 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

45 ms

gtm.js

gtm.js

81 ms

1228 ms

ic-top.png

ic-top.png

689 ms

ic-service.png

ic-service.png

939 ms

ic-plan.png

ic-plan.png

2437 ms

ic-provider.png

ic-provider.png

2438 ms

ic-campaign.png

ic-campaign.png

2441 ms

ic-faq.png

ic-faq.png

2441 ms

img-cont-2.png

img-cont-2.png

2439 ms

popup_flow2-close.png

popup_flow2-close.png

2442 ms

header-support.png

header-support.png

2438 ms

telepocket.png

telepocket.png

2458 ms

head-logo.png

head-logo.png

2457 ms

contact-icon1.png

contact-icon1.png

2457 ms

contact-icon2.png

contact-icon2.png

2458 ms

contact-icon3.png

contact-icon3.png

2457 ms

contact-icon4.png

contact-icon4.png

2456 ms

fd-icon.png

fd-icon.png

2620 ms

heightLine.js

heightLine.js

2821 ms

common.js

common.js

2860 ms

shadowbox.js

shadowbox.js

3320 ms

decision_domain.js

decision_domain.js

2491 ms

js

js

86 ms

destination

destination

85 ms

destination

destination

210 ms

bat.js

bat.js

80 ms

ytag.js

ytag.js

1081 ms

u

u

388 ms

pdeasofc

pdeasofc

387 ms

script.js

script.js

1081 ms

smartadlpo_v3.js

smartadlpo_v3.js

745 ms

web.js

web.js

195 ms

fbevents.js

fbevents.js

32 ms

destination

destination

96 ms

title-select-area-transparent.png

title-select-area-transparent.png

2117 ms

map.png

map.png

2799 ms

banner_pricecheck.jpg

banner_pricecheck.jpg

2467 ms

banner-west.png

banner-west.png

3290 ms

ribon-west.png

ribon-west.png

2619 ms

f1.png

f1.png

3164 ms

f2.png

f2.png

2666 ms

banner-collabo.png

banner-collabo.png

3793 ms

hikari-denwa.png

hikari-denwa.png

3514 ms

flets-tv.png

flets-tv.png

3145 ms

security.png

security.png

3478 ms

support.png

support.png

3488 ms

pdeasofc

pdeasofc

67 ms

btn-west.png

btn-west.png

3667 ms

btn-east.png

btn-east.png

3283 ms

js

js

218 ms

js

js

212 ms

js

js

208 ms

js

js

461 ms

js

js

455 ms

js

js

449 ms

js

js

440 ms

js

js

435 ms

js

js

432 ms

js

js

432 ms

js

js

429 ms

js

js

422 ms

js

js

422 ms

js

js

416 ms

js

js

415 ms

js

js

415 ms

js

js

402 ms

js

js

398 ms

js

js

393 ms

js

js

389 ms

js

js

393 ms

js

js

372 ms

js

js

369 ms

js

js

353 ms

form-return.css

form-return.css

3714 ms

decision_domain.js

decision_domain.js

3718 ms

sbs-icon.png

sbs-icon.png

3199 ms

popup.css

popup.css

2969 ms

jquery.min.js

jquery.min.js

702 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

2726 ms

common.js

common.js

1927 ms

form-return.js

form-return.js

2359 ms

jquery.autoKana.js

jquery.autoKana.js

2083 ms

spsite-banner.png

spsite-banner.png

2599 ms

title-select-area.png

title-select-area.png

2754 ms

img-select-area.png

img-select-area.png

2377 ms

head-yajirushi-b.png

head-yajirushi-b.png

2876 ms

head-yajirushi-g.png

head-yajirushi-g.png

2517 ms

header_tel_g.png

header_tel_g.png

2550 ms

arrow-button.png

arrow-button.png

3023 ms

white-arrow-icon.png

white-arrow-icon.png

3226 ms

gray-arrow-icon.png

gray-arrow-icon.png

2762 ms

ic-service.png

ic-service.png

2564 ms

h-flets-hikari-bg.png

h-flets-hikari-bg.png

3051 ms

arrow-white-right.png

arrow-white-right.png

3085 ms

h-option-bg.png

h-option-bg.png

2624 ms

arrow-pagetop.png

arrow-pagetop.png

2541 ms

icon-foot-area.png

icon-foot-area.png

2693 ms

tag.js

tag.js

45 ms

showtalk-widget.js

showtalk-widget.js

183 ms

mainv.png

mainv.png

1534 ms

tel_icon.png

tel_icon.png

1089 ms

modal_close.png

modal_close.png

1196 ms

Accessibility Review

hikari-n.jp accessibility score

77

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

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hikari-n.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hikari-n.jp SEO score

85

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

Social Sharing Optimization

hikari-n.jp

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: