Tools & Wizards About Us
hanshin.co.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% 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

  • 89

    SEO

    Google-friendlier than
    66% of websites

hanshin.co.jp

阪神電気鉄道株式会社

Page Load Speed

8.3 sec in total

First Response

555 ms

Resources Loaded

7 sec

Page Rendered

763 ms

hanshin.co.jp screenshot

About Website

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

阪神電車の公式サイト。ダイヤ・運賃検索、時刻表、定期券、お得なきっぷ、路線図・駅情報や企業情報・ニュースリリースなどをご紹介します。

Visit hanshin.co.jp

Key Findings

We analyzed Hanshin.co.jp page load time and found that the first response time was 555 ms and then it took 7.7 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

hanshin.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value680 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.341

33/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

hanshin.co.jp

555 ms

hanshin.co.jp

998 ms

gtm.js

54 ms

slick.css

357 ms

jquery-ui.min.css

672 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 93% of them (96 requests) were addressed to the original Hanshin.co.jp, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Hanshin.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.1 kB (8%)

Content Size

4.6 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 79.6 kB

  • Original 92.7 kB
  • After minification 73.8 kB
  • After compression 13.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 18.9 kB, which is 20% 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 79.6 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 242.4 kB

  • Original 4.4 MB
  • After minification 4.2 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. Hanshin images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 16.4 kB

  • Original 98.4 kB
  • After minification 95.1 kB
  • After compression 82.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 16.4 kB or 17% of the original size.

CSS Optimization

-34%

Potential reduce by 12.6 kB

  • Original 37.4 kB
  • After minification 37.4 kB
  • After compression 24.8 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. Hanshin.co.jp needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (28%)

Requests Now

100

After Optimization

72

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hanshin.co.jp

hanshin.co.jp

555 ms

hanshin.co.jp

hanshin.co.jp

998 ms

gtm.js

gtm.js

54 ms

slick.css

slick.css

357 ms

jquery-ui.min.css

jquery-ui.min.css

672 ms

base.css

base.css

508 ms

common.css

common.css

898 ms

top.css

top.css

536 ms

jquery.js

jquery.js

1075 ms

slick.min.js

slick.min.js

907 ms

jquery-ui.min.js

jquery-ui.min.js

843 ms

common.js

common.js

717 ms

top.js

top.js

836 ms

information_press.js

information_press.js

905 ms

timetable.json.js

timetable.json.js

1205 ms

timetable.listbox.js

timetable.listbox.js

1223 ms

jquery.cookie.js

jquery.cookie.js

1227 ms

js

js

50 ms

analytics.js

analytics.js

22 ms

collect

collect

97 ms

collect

collect

51 ms

css2

css2

33 ms

9f5c59fd41283b8e68ae280767c9e1c736184f0b.png

9f5c59fd41283b8e68ae280767c9e1c736184f0b.png

634 ms

a4a4d1eccade42f13f76859bbe8f6bc910b873bf.jpg

a4a4d1eccade42f13f76859bbe8f6bc910b873bf.jpg

315 ms

f21e3de04d7f8f99d00dc9269af7e7daa0d23b93.png

f21e3de04d7f8f99d00dc9269af7e7daa0d23b93.png

370 ms

OMP_bunner_240_184.jpg

OMP_bunner_240_184.jpg

522 ms

9265bbdf100913a4e1928346751f4c9191da7f0f.jpg

9265bbdf100913a4e1928346751f4c9191da7f0f.jpg

507 ms

dabf71f5ee18049db0dcdf1d383cc52cf076ccf4.png

dabf71f5ee18049db0dcdf1d383cc52cf076ccf4.png

547 ms

topics_enkachi.jpg

topics_enkachi.jpg

548 ms

ad8aa12dd2d03f8c5b0ab8fd6ee521960bf91f20.jpg

ad8aa12dd2d03f8c5b0ab8fd6ee521960bf91f20.jpg

568 ms

28bc278b006468166bde7fb6267a15ac56693a57.png

28bc278b006468166bde7fb6267a15ac56693a57.png

715 ms

c72ba146e9d126e98c0323f7836b2d073aeef6cf.png

c72ba146e9d126e98c0323f7836b2d073aeef6cf.png

750 ms

logo_gr.png

logo_gr.png

204 ms

logo_taisetsu_gr.svg

logo_taisetsu_gr.svg

207 ms

ic_arrow_wh.svg

ic_arrow_wh.svg

202 ms

ic_lang_gr.svg

ic_lang_gr.svg

200 ms

ic_operational_normal.svg

ic_operational_normal.svg

199 ms

ic_train_gr.svg

ic_train_gr.svg

204 ms

ic_price_gr.svg

ic_price_gr.svg

334 ms

ic_ticket_gr.svg

ic_ticket_gr.svg

336 ms

ic_oneday_gr.svg

ic_oneday_gr.svg

342 ms

slider_taisetsu_pc.png

slider_taisetsu_pc.png

360 ms

slider_taisetsu_sp.png

slider_taisetsu_sp.png

359 ms

slider_taisetsu_2_pc.png

slider_taisetsu_2_pc.png

1616 ms

slider_taisetsu_2_sp.png

slider_taisetsu_2_sp.png

1819 ms

slider_division_pc.png

slider_division_pc.png

1335 ms

slider_division_sp.png

slider_division_sp.png

1191 ms

slider_umeda_pc.jpg

slider_umeda_pc.jpg

715 ms

slider_umeda_sp.jpg

slider_umeda_sp.jpg

717 ms

slider_koshien_pc.jpg

slider_koshien_pc.jpg

895 ms

slider_koshien_sp.jpg

slider_koshien_sp.jpg

900 ms

slider_herbis_pc.jpg

slider_herbis_pc.jpg

1251 ms

slider_herbis_sp.jpg

slider_herbis_sp.jpg

1259 ms

slider_ritzcarlton_pc.jpg

slider_ritzcarlton_pc.jpg

1530 ms

slider_ritzcarlton_sp.jpg

slider_ritzcarlton_sp.jpg

1609 ms

ic_barrierfree_gr.svg

ic_barrierfree_gr.svg

1441 ms

ic_q_gr.svg

ic_q_gr.svg

1502 ms

illust_article_take_pc.png

illust_article_take_pc.png

1622 ms

illust_article_take_sp.png

illust_article_take_sp.png

1670 ms

illust_article_stay_pc.png

illust_article_stay_pc.png

1700 ms

illust_article_stay_sp.png

illust_article_stay_sp.png

1787 ms

logo_koshien.jpg

logo_koshien.jpg

1793 ms

logo_rokkosan.jpg

logo_rokkosan.jpg

1801 ms

logo_ritzcarlton.jpg

logo_ritzcarlton.jpg

1838 ms

logo_herbis.jpg

logo_herbis.jpg

1871 ms

illust_article_life_pc.png

illust_article_life_pc.png

1965 ms

illust_article_life_sp.png

illust_article_life_sp.png

1972 ms

logo_hanshinbus.jpg

logo_hanshinbus.jpg

1953 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

21 ms

logo_mimamorume.jpg

logo_mimamorume.jpg

1788 ms

logo_lafit.jpg

logo_lafit.jpg

1813 ms

logo_baycom.jpg

logo_baycom.jpg

1848 ms

logo_ikiiki.jpg

logo_ikiiki.jpg

1949 ms

app_hh_bg.png

app_hh_bg.png

2315 ms

logo_app_hh.png

logo_app_hh.png

1948 ms

app_bnr_google.png

app_bnr_google.png

1835 ms

app_bnr_app.png

app_bnr_app.png

1845 ms

app_twitter_unkou_bg.png

app_twitter_unkou_bg.png

2217 ms

ic_app_x.svg

ic_app_x.svg

1972 ms

app_twitter_bg.png

app_twitter_bg.png

2457 ms

app_youtube_bg.png

app_youtube_bg.png

1991 ms

logo_app_youtube.png

logo_app_youtube.png

1630 ms

app_insta_bg.png

app_insta_bg.png

1969 ms

logo_app_insta.png

logo_app_insta.png

1616 ms

app_line_bg.png

app_line_bg.png

1829 ms

logo_app_line.png

logo_app_line.png

1446 ms

app_facebook_bg.png

app_facebook_bg.png

1810 ms

logo_app_facebook.png

logo_app_facebook.png

1545 ms

info_bnr_pc.png

info_bnr_pc.png

2515 ms

info_bnr_sp.png

info_bnr_sp.png

2961 ms

ic_app_facebook.svg

ic_app_facebook.svg

1514 ms

ic_app_insta.svg

ic_app_insta.svg

1452 ms

ic_replacement_sp_gr.svg

ic_replacement_sp_gr.svg

1574 ms

ic_calendar_gr.svg

ic_calendar_gr.svg

1599 ms

ic_radiocheck_gr.svg

ic_radiocheck_gr.svg

1570 ms

ic_play.svg

ic_play.svg

1538 ms

ic_stop.svg

ic_stop.svg

1568 ms

ic_replacement_pc_gr.svg

ic_replacement_pc_gr.svg

1606 ms

ic_exclamation_or.svg

ic_exclamation_or.svg

1608 ms

ic_circle.png

ic_circle.png

1606 ms

line_rainbow.svg

line_rainbow.svg

1683 ms

bt_totop_pc.png

bt_totop_pc.png

1707 ms

ic_blank_wh.svg

ic_blank_wh.svg

1614 ms

Accessibility Review

hanshin.co.jp accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

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

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

hanshin.co.jp SEO score

89

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

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

hanshin.co.jp

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