Tools & Wizards About Us
jump.co.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

jump.co.jp

株式会社ジャンプコーポレーション

Page Load Speed

5.5 sec in total

First Response

1.1 sec

Resources Loaded

4.1 sec

Page Rendered

346 ms

jump.co.jp screenshot

About Website

Click here to check amazing Jump content. Otherwise, check out these important facts you probably never knew about jump.co.jp

「テレビはもう終わり」から「テレビは終わらない」へ。変えていけるのは、私たちジャンプコーポレーションです！

Visit jump.co.jp

Key Findings

We analyzed Jump.co.jp page load time and found that the first response time was 1.1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

jump.co.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value34.3 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

jump.co.jp

1089 ms

default.css

327 ms

main.css

361 ms

responsive.css

957 ms

jquery.fancybox.css

926 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 68% of them (58 requests) were addressed to the original Jump.co.jp, 11% (9 requests) were made to Apis.google.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Jump.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 159.2 kB (18%)

Content Size

864.8 kB

After Optimization

705.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jump.co.jp main page is 864.8 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. 60% of websites need less resources to load. Images take 631.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 35.1 kB

  • Original 43.9 kB
  • After minification 37.7 kB
  • After compression 8.8 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 6.2 kB, which is 14% 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 35.1 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 3.4 kB

  • Original 631.0 kB
  • After minification 627.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. Jump images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 101.0 kB

  • Original 166.0 kB
  • After minification 155.6 kB
  • After compression 65.0 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 101.0 kB or 61% of the original size.

CSS Optimization

-82%

Potential reduce by 19.6 kB

  • Original 23.9 kB
  • After minification 18.1 kB
  • After compression 4.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. Jump.co.jp needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (33%)

Requests Now

82

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jump.co.jp

jump.co.jp

1089 ms

default.css

default.css

327 ms

main.css

main.css

361 ms

responsive.css

responsive.css

957 ms

jquery.fancybox.css

jquery.fancybox.css

926 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

922 ms

script.js

script.js

380 ms

lightbox-2.6.min.js

lightbox-2.6.min.js

486 ms

jquery.tile.js

jquery.tile.js

541 ms

bookmark_button.js

bookmark_button.js

322 ms

ga.js

ga.js

85 ms

button-only@2x.png

button-only@2x.png

176 ms

bg_header_flower_left.png

bg_header_flower_left.png

204 ms

bg_header_flower_right.png

bg_header_flower_right.png

217 ms

bg_header_ground.png

bg_header_ground.png

168 ms

bg_header_grass.png

bg_header_grass.png

204 ms

bg_header_main.png

bg_header_main.png

1632 ms

bg_header_logo.png

bg_header_logo.png

355 ms

img_btn_header_business.png

img_btn_header_business.png

370 ms

img_btn_header_results.png

img_btn_header_results.png

395 ms

img_btn_header_company.png

img_btn_header_company.png

396 ms

img_btn_header_recruit.png

img_btn_header_recruit.png

406 ms

img_btn_header_mail.png

img_btn_header_mail.png

526 ms

img_header_title.png

img_header_title.png

553 ms

img_header_sentence.png

img_header_sentence.png

555 ms

img_header_detail.png

img_header_detail.png

557 ms

img-header-human1.gif

img-header-human1.gif

785 ms

img_header_human2.png

img_header_human2.png

699 ms

img-header-human3.gif

img-header-human3.gif

1090 ms

img-header-human4.gif

img-header-human4.gif

1103 ms

img_header_human5.png

img_header_human5.png

742 ms

img-header-human6.gif

img-header-human6.gif

1043 ms

img_header_human7.png

img_header_human7.png

925 ms

img-header-human8.gif

img-header-human8.gif

1390 ms

img_header_human9.png

img_header_human9.png

1110 ms

img-header-human10.gif

img-header-human10.gif

1735 ms

img_official-character.png

img_official-character.png

1268 ms

img_contents_ad.png

img_contents_ad.png

1284 ms

img_contents_info.png

img_contents_info.png

1293 ms

img_contents_column.png

img_contents_column.png

1448 ms

icon_contents_link.png

icon_contents_link.png

1467 ms

img_contents_theater.png

img_contents_theater.png

1478 ms

img_contents_net-tv.png

img_contents_net-tv.png

1579 ms

img_contents_right_top.png

img_contents_right_top.png

1627 ms

img_contents_right_pen.png

img_contents_right_pen.png

1649 ms

img_contents_right_line.png

img_contents_right_line.png

1662 ms

img_contents_right_article15.png

img_contents_right_article15.png

1769 ms

widgets.js

widgets.js

81 ms

sdk.js

sdk.js

48 ms

plusone.js

plusone.js

111 ms

img_site_btn.png

img_site_btn.png

1724 ms

__utm.gif

__utm.gif

34 ms

379 ms

158 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

158 ms

xd_arbiter.php

xd_arbiter.php

33 ms

xd_arbiter.php

xd_arbiter.php

80 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

39 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

67 ms

fastbutton

fastbutton

114 ms

img_contents_right_article1.png

img_contents_right_article1.png

1627 ms

img_contents_right_article3.png

img_contents_right_article3.png

1640 ms

img_contents_right_article9.png

img_contents_right_article9.png

1643 ms

img_contents_right_article6.png

img_contents_right_article6.png

1700 ms

postmessageRelay

postmessageRelay

38 ms

rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ

rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ

5 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

46 ms

rpc:shindig_random.js

rpc:shindig_random.js

45 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

23 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

20 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

48 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

img_contents_right_article2.png

img_contents_right_article2.png

1614 ms

img_contents_right_article10.png

img_contents_right_article10.png

1588 ms

icon_new.png

icon_new.png

1600 ms

img_contents_right_article16.png

img_contents_right_article16.png

1628 ms

img_contents_right_article4.png

img_contents_right_article4.png

1634 ms

reset.css

reset.css

5 ms

entry-button.css

entry-button.css

5 ms

bbtn-s_v3.png

bbtn-s_v3.png

2 ms

img_top_btn.png

img_top_btn.png

1561 ms

img_contents_bottom_human.png

img_contents_bottom_human.png

1566 ms

bg_main.png

bg_main.png

1603 ms

icon_footer_arrow.png

icon_footer_arrow.png

1616 ms

jot.html

jot.html

27 ms

Accessibility Review

jump.co.jp accessibility score

91

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

jump.co.jp best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

jump.co.jp SEO score

93

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 doesn't use 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 Jump.co.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 Jump.co.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

jump.co.jp

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