Tools & Wizards About Us
web116.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

web116.jp

総合トップ｜NTT東日本 Web116.jp

Page Load Speed

6.9 sec in total

First Response

903 ms

Resources Loaded

5.8 sec

Page Rendered

213 ms

web116.jp screenshot

About Website

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

電話やインターネットのお手続きや各種商品・サービスのお申し込み、通信機器の購入からサポートまで、Web116.jpなら簡単でスピーディーです。

Visit web116.jp

Key Findings

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

Performance Metrics

web116.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value5,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

web116.jp

903 ms

swiper.min.css

376 ms

home.css

527 ms

main.css

1047 ms

shared.css

879 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 31% of them (31 requests) were addressed to the original Web116.jp, 14% (14 requests) were made to Googletagmanager.com and 10% (10 requests) were made to I6.smartnews-ads.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Web116.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 599.7 kB (50%)

Content Size

1.2 MB

After Optimization

597.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Web116.jp main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 470.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.3 kB

  • Original 42.4 kB
  • After minification 42.1 kB
  • After compression 8.2 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.3 kB or 81% of the original size.

Image Optimization

-17%

Potential reduce by 80.7 kB

  • Original 470.8 kB
  • After minification 390.1 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. Obviously, Web116 needs image optimization as it can save up to 80.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 202.8 kB

  • Original 362.0 kB
  • After minification 352.4 kB
  • After compression 159.2 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 202.8 kB or 56% of the original size.

CSS Optimization

-87%

Potential reduce by 281.9 kB

  • Original 322.2 kB
  • After minification 236.8 kB
  • After compression 40.4 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. Web116.jp needs all CSS files to be minified and compressed as it can save up to 281.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (60%)

Requests Now

98

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web116.jp

web116.jp

903 ms

swiper.min.css

swiper.min.css

376 ms

home.css

home.css

527 ms

main.css

main.css

1047 ms

shared.css

shared.css

879 ms

web116.css

web116.css

884 ms

module.css

module.css

830 ms

init.js

init.js

560 ms

jquery.js

jquery.js

1043 ms

magnific-popup.min.js

magnific-popup.min.js

760 ms

matchHeight-min.js

matchHeight-min.js

989 ms

shared.js

shared.js

1064 ms

run.js

run.js

1158 ms

swiper.min.js

swiper.min.js

1251 ms

search_tool_n3.js

search_tool_n3.js

693 ms

gtm.js

gtm.js

96 ms

logo_east_01.svg

logo_east_01.svg

240 ms

ico_search.png

ico_search.png

207 ms

icon_top01.svg

icon_top01.svg

207 ms

icon_top03.svg

icon_top03.svg

208 ms

icon_top02.svg

icon_top02.svg

208 ms

icon_dmail.svg

icon_dmail.svg

238 ms

icon_atto.svg

icon_atto.svg

459 ms

icon_houjin.svg

icon_houjin.svg

456 ms

img_main.png

img_main.png

531 ms

img_10.png

img_10.png

530 ms

img_03.png

img_03.png

788 ms

img_04.png

img_04.png

650 ms

img_05.png

img_05.png

787 ms

img_08.png

img_08.png

786 ms

icon_pdf.png

icon_pdf.png

783 ms

icon_blank_02.png

icon_blank_02.png

788 ms

bullet-blank.svg

bullet-blank.svg

1284 ms

analytics.js

analytics.js

51 ms

gtm.js

gtm.js

70 ms

gtm.js

gtm.js

118 ms

gtm.js

gtm.js

293 ms

gtm.js

gtm.js

73 ms

gtm.js

gtm.js

116 ms

gtm.js

gtm.js

289 ms

gtm.js

gtm.js

177 ms

collect

collect

228 ms

collect

collect

231 ms

collect

collect

233 ms

collect

collect

229 ms

collect

collect

226 ms

collect

collect

145 ms

destination

destination

193 ms

ytag.js

ytag.js

1132 ms

collect

collect

197 ms

collect

collect

324 ms

collect

collect

325 ms

collect

collect

731 ms

js

js

65 ms

js

js

229 ms

js

js

222 ms

js

js

217 ms

destination

destination

175 ms

fbevents.js

fbevents.js

685 ms

pixel.js

pixel.js

717 ms

uwt.js

uwt.js

716 ms

bat.js

bat.js

703 ms

track.js

track.js

1164 ms

ga-audiences

ga-audiences

690 ms

ga-audiences

ga-audiences

583 ms

ga-audiences

ga-audiences

648 ms

ga-audiences

ga-audiences

174 ms

187033666.js

187033666.js

23 ms

187068263.js

187068263.js

21 ms

187033666

187033666

88 ms

187068263

187068263

95 ms

adsct

adsct

136 ms

adsct

adsct

142 ms

p

p

677 ms

smallest.png

smallest.png

70 ms

smallest.png

smallest.png

71 ms

smallest.png

smallest.png

73 ms

smallest.png

smallest.png

74 ms

smallest.png

smallest.png

74 ms

smallest.png

smallest.png

75 ms

smallest.png

smallest.png

75 ms

smallest.png

smallest.png

74 ms

smallest.png

smallest.png

76 ms

smallest.png

smallest.png

76 ms

p

p

696 ms

p

p

699 ms

p

p

703 ms

p

p

704 ms

p

p

727 ms

p

p

847 ms

p

p

868 ms

p

p

872 ms

p

p

874 ms

clarity.js

clarity.js

20 ms

universe_cookie_sync.html

universe_cookie_sync.html

710 ms

config.json

config.json

166 ms

new_i_search_assist.js

new_i_search_assist.js

689 ms

new_ac.css

new_ac.css

730 ms

c.gif

c.gif

7 ms

Accessibility Review

web116.jp accessibility score

84

Accessibility Issues

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

High

Form elements do not have associated labels

Best Practices

web116.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

web116.jp SEO score

99

Search Engine Optimization Advices

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Web116.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 Web116.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

web116.jp

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