5.1 sec in total
1 sec
3.9 sec
184 ms
Click here to check amazing Ekitan content for Japan. Otherwise, check out these important facts you probably never knew about ekitan.com
駅探は通勤・通学、旅行やおでかけ、出張に便利な乗換案内・時刻表サービス。全国の電車・バス・飛行機に対応。
Visit ekitan.comWe analyzed Ekitan.com page load time and found that the first response time was 1 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ekitan.com performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value16.1 s
0/100
25%
Value15.4 s
1/100
10%
Value3,850 ms
1/100
30%
Value0.101
89/100
15%
Value20.4 s
2/100
10%
1013 ms
321 ms
332 ms
330 ms
333 ms
Our browser made a total of 178 requests to load all elements on the main page. We found that 54% of them (97 requests) were addressed to the original Ekitan.com, 4% (8 requests) were made to Tpc.googlesyndication.com and 3% (6 requests) were made to Dsum.casalemedia.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ekitan.com.
Page size can be reduced by 1.4 MB (48%)
2.9 MB
1.5 MB
In fact, the total size of Ekitan.com main page is 2.9 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. 55% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 109.9 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 109.9 kB or 75% of the original size.
Potential reduce by 21.3 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. Ekitan images are well optimized though.
Potential reduce by 962.4 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 962.4 kB or 70% of the original size.
Potential reduce by 290.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. Ekitan.com needs all CSS files to be minified and compressed as it can save up to 290.4 kB or 86% of the original size.
Number of requests can be reduced by 122 (73%)
167
45
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ekitan. 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 28 to 1 for CSS and as a result speed up the page load time.
ekitan.com
1013 ms
sp_alert.js
321 ms
ekitan_20140701.css
332 ms
index_top.css
330 ms
pr_top_001.css
333 ms
ekitan_suggest.css
337 ms
sub_unkou.css
479 ms
grayout.css
493 ms
adtext.js
496 ms
norikae_frm.js
661 ms
region.js
671 ms
uuc.js
634 ms
jquery.1.2.6.js
955 ms
hover.js
657 ms
jquery.bgiframe.js
659 ms
ekitan.js
794 ms
ekitan.search.top.js
984 ms
ekitan.search.norikae.js
824 ms
ekitan.grayout.js
826 ms
ekitan.html.subskeleton.js
839 ms
jquery.js
1114 ms
unkou_info_ini.js
989 ms
unkou_info.js
1156 ms
ekitan.rireki.js
1007 ms
ekitan.log.js
1113 ms
ensen_news_list.js
549 ms
common_top.css
823 ms
layout_5_3_variable.css
829 ms
common_unkou.css
850 ms
initialize.css
947 ms
global_20140701.css
950 ms
header.css
986 ms
footer.css
994 ms
common_pr.css
997 ms
cnt_1001a.css
1017 ms
cnt_1002a.css
1105 ms
cnt_1002b.css
1109 ms
cnt_1006a.css
1149 ms
cnt_1008a.css
1158 ms
cnt_1010a.css
1162 ms
cnt_1014a.css
1184 ms
cnt_1007a.css
1260 ms
ekitan.css
333 ms
jquery.min.js
687 ms
default.js
361 ms
cnt_1007b.css
1127 ms
msd_a001a.css
1166 ms
oth_2001b.css
1161 ms
common_sub.css
1164 ms
sublayout_3_3_780c.css
1050 ms
ekitan.atics.js
1139 ms
area_change_map.html
169 ms
reg_del_top_list.html
169 ms
area_by_company.html
172 ms
area_by_result_ex.html
173 ms
gpt.js
16 ms
ekitan_logo.png
168 ms
tr_bg_globalnav.gif
207 ms
btn_replace.gif
322 ms
btn_history.gif
332 ms
btn_search.gif
335 ms
t_travel.gif
331 ms
area_oosaka.jpg
338 ms
area_kyoto.jpg
366 ms
area_sapporo.jpg
490 ms
area_fukuoka.jpg
518 ms
smartphone_menu.jpg
519 ms
bnr_top_pr01.gif
519 ms
bnr_top_pr05.gif
520 ms
bnr_top_pr04.gif
525 ms
bnr_top_pr02.gif
644 ms
today.gif
659 ms
w_c_r_.gif
660 ms
tomorrow.gif
663 ms
w_f_c_.gif
683 ms
realestate_rcolumn.png
684 ms
copyright.gif
804 ms
pubads_impl_81.js
15 ms
top_fst.html
805 ms
icon_rightlink.gif
801 ms
bg_h2_yellow.gif
803 ms
icon_update.gif
826 ms
icon_construction.gif
820 ms
icon_information.gif
940 ms
icon_dia.gif
963 ms
icon_press.gif
965 ms
icon_rightarrow.gif
965 ms
icon_new.gif
975 ms
ads
328 ms
container.html
34 ms
dot.gif
367 ms
bg_topmenu.gif
925 ms
dc.js
28 ms
__utm.gif
11 ms
bg_h3_topmenu.gif
969 ms
icon_travel.png
1028 ms
icon_ekitan.gif
1031 ms
icon_train_syuden.gif
1031 ms
icon_timetable.gif
1031 ms
icon_bus.gif
999 ms
icon_tinfo.gif
980 ms
icon_rosenzu.gif
998 ms
icon_station.gif
998 ms
icon_yard.gif
997 ms
icon_walk.gif
988 ms
bg_globalfooter.gif
1011 ms
18114250481007650603
55 ms
expansion_embed.js
28 ms
15055960544229962649
36 ms
6614414820925421680
58 ms
osd.js
25 ms
abg.js
33 ms
m_js_controller.js
39 ms
googlelogo_color_112x36dp.png
32 ms
13250232331523409936
52 ms
s
26 ms
x_button_blue2.png
19 ms
ADTECH;cfp=1;rndc=1456746280;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1456746281404
297 ms
uif_area_chk.js
617 ms
aceUAC.js
12 ms
getuid
18 ms
pixel
20 ms
generic
14 ms
AdId=6709455;BnId=1;ct=749178099;st=137495;adcid=1;itime=746280977;reqtype=5;;key=key1%2Bkey2%2Bkey3%2Bkey4;
178 ms
sync
11 ms
mapuser
294 ms
dref=http%253A%252F%252Fekitan.com%252F
19 ms
generic
5 ms
mapuser
296 ms
mapuser
297 ms
mapuser
300 ms
dref=http%253A%252F%252Fekitan.com%252F
17 ms
j2gcc2caaoct14_B_300x250.gif
74 ms
adchoicesJP_white.png
81 ms
moatad.js
33 ms
n.js
22 ms
usermatch
18 ms
pixel.htm
69 ms
usermatch
14 ms
pixel
15 ms
VtQvKsAoJHIAAHN3eOUAAAB-%26395
48 ms
gr
10 ms
casale
5 ms
cs
22 ms
mapuser
301 ms
rum
34 ms
rum
33 ms
pixel
58 ms
rum
35 ms
rum
30 ms
crum
61 ms
rum
8 ms
ddc.htm
25 ms
Pug
31 ms
getuid
16 ms
rtset
47 ms
rum
29 ms
u.php
95 ms
60 ms
pixel
25 ms
m
40 ms
sd
20 ms
xrefid.xgi
23 ms
sync
27 ms
mapuser
23 ms
bd
36 ms
tap.php
27 ms
NAX3077465624500780308
48 ms
crum
8 ms
lr.gif
7 ms
merge
40 ms
pixel.gif
5 ms
0.gif
174 ms
mapuser
6 ms
ui_api
164 ms
activeview
15 ms
activeview
15 ms
activeview
16 ms
ekitan.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ekitan.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ekitan.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekitan.com 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 Ekitan.com 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.
ekitan.com
Open Graph description is not detected on the main page of Ekitan. 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: