Tools & Wizards About Us
jptower.jp screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

jptower.jp

JPタワー / JP TOWER

Page Load Speed

8.9 sec in total

First Response

787 ms

Resources Loaded

8 sec

Page Rendered

132 ms

jptower.jp screenshot

About Website

Visit jptower.jp now to see the best up-to-date JP TOWER content for Japan and also check out these interesting facts you probably never knew about jptower.jp

ＪＰタワーの公式ウェブサイト。ＪＰタワーは、商業施設「ＫＩＴＴＥ」（キッテ）や東京中央郵便局、ＪＰタワー学術文化総合ミュージアム「インターメディアテク」、観光・ビジネス情報センター「東京シティアイ」、ＪＰタワー ホール＆カンファレンスなどからなる複合施設です。

Visit jptower.jp

Key Findings

We analyzed Jptower.jp page load time and found that the first response time was 787 ms and then it took 8.1 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

jptower.jp performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

jptower.jp

787 ms

default.css

380 ms

ob_style.css

381 ms

jquery-1.9.1.min.js

1142 ms

top.js

384 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Jptower.jp, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Jptower.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.6 kB (3%)

Content Size

3.0 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-64%

Potential reduce by 3.0 kB

  • Original 4.7 kB
  • After minification 4.4 kB
  • After compression 1.7 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 3.0 kB or 64% of the original size.

Image Optimization

-0%

Potential reduce by 10.2 kB

  • Original 2.9 MB
  • After minification 2.9 MB

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. JP TOWER images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 61.1 kB

  • Original 112.4 kB
  • After minification 112.1 kB
  • After compression 51.3 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 61.1 kB or 54% of the original size.

CSS Optimization

-71%

Potential reduce by 3.3 kB

  • Original 4.6 kB
  • After minification 3.6 kB
  • After compression 1.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. Jptower.jp needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (32%)

Requests Now

25

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jptower.jp

jptower.jp

787 ms

default.css

default.css

380 ms

ob_style.css

ob_style.css

381 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1142 ms

top.js

top.js

384 ms

smartRollover.js

smartRollover.js

385 ms

ga.js

ga.js

23 ms

logo.gif

logo.gif

192 ms

menu_top_on.gif

menu_top_on.gif

375 ms

menu_jptower_off.gif

menu_jptower_off.gif

380 ms

menu_release_off.gif

menu_release_off.gif

381 ms

menu_access_off.gif

menu_access_off.gif

380 ms

menu_topics_off.gif

menu_topics_off.gif

399 ms

bg1.jpg

bg1.jpg

2861 ms

bg2.jpg

bg2.jpg

3060 ms

bg3.jpg

bg3.jpg

3417 ms

bg4.jpg

bg4.jpg

3853 ms

banner_kitte_off.gif

banner_kitte_off.gif

957 ms

banner_rmt_off.gif

banner_rmt_off.gif

958 ms

banner_tokyocity_off.gif

banner_tokyocity_off.gif

1528 ms

banner_conference_off.gif

banner_conference_off.gif

1532 ms

bg1_new.jpg

bg1_new.jpg

4019 ms

bg2_new.jpg

bg2_new.jpg

4202 ms

bg3_new.jpg

bg3_new.jpg

5199 ms

bg4_new.jpg

bg4_new.jpg

6176 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

jptower.jp accessibility score

85

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

jptower.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jptower.jp SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jptower.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jptower.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

jptower.jp

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