Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

hotspot.ne.jp

無線LANサービス ホットスポット

Page Load Speed

3.6 sec in total

First Response

251 ms

Resources Loaded

3.3 sec

Page Rendered

95 ms

hotspot.ne.jp screenshot

About Website

Click here to check amazing Hotspot content. Otherwise, check out these important facts you probably never knew about hotspot.ne.jp

国際電話0033のNTTコミュニケーションズは、無線LANサービスも充実。「ホットスポット」は、新幹線や海外でも利用でき、ビジネスシーンに役立ちます。

Visit hotspot.ne.jp

Key Findings

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

Performance Metrics

hotspot.ne.jp performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

hotspot.ne.jp

251 ms

hotspot.ne.jp

395 ms

import_home.css

338 ms

rollover.js

339 ms

urchin.js

364 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 95% of them (37 requests) were addressed to the original Hotspot.ne.jp, 5% (2 requests) were made to Ocn.ne.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Hotspot.ne.jp.

Page Optimization Overview & Recommendations

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

Content Size

140.3 kB

After Optimization

120.5 kB

In fact, the total size of Hotspot.ne.jp main page is 140.3 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 10% of websites need less resources to load. Images take 122.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.5 kB

  • Original 10.6 kB
  • After minification 9.0 kB
  • After compression 3.1 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 1.6 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 7.5 kB or 71% of the original size.

Image Optimization

-9%

Potential reduce by 11.3 kB

  • Original 122.8 kB
  • After minification 111.6 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. Hotspot images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 1.0 kB

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 5.9 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 1.0 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (51%)

Requests Now

35

After Optimization

17

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

Accessibility Review

hotspot.ne.jp accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

hotspot.ne.jp SEO score

62

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

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotspot.ne.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Hotspot.ne.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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