3.3 sec in total
693 ms
2.4 sec
195 ms
Click here to check amazing Go Ekitan content for Japan. Otherwise, check out these important facts you probably never knew about go.ekitan.com
駅探(えきたん)では、高精度な乗り換え案内APIの他、乗り換え+徒歩ルート検索API、所要時間検索API、路線図AJAX、運行情報API、多言語に対応した駅データなどの法人向けサービス・ASP・APIを提供しています。一部無料トライアルをご利用頂けます。
Visit go.ekitan.comWe analyzed Go.ekitan.com page load time and found that the first response time was 693 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
go.ekitan.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value8.2 s
2/100
25%
Value5.6 s
53/100
10%
Value50 ms
100/100
30%
Value0.047
99/100
15%
Value6.3 s
61/100
10%
693 ms
326 ms
333 ms
335 ms
673 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 94% of them (45 requests) were addressed to the original Go.ekitan.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Go.ekitan.com.
Page size can be reduced by 117.2 kB (27%)
428.3 kB
311.1 kB
In fact, the total size of Go.ekitan.com main page is 428.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. 20% of websites need less resources to load. Images take 323.1 kB which makes up the majority of the site volume.
Potential reduce by 6.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 6.9 kB or 71% of the original size.
Potential reduce by 43.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. Obviously, Go Ekitan needs image optimization as it can save up to 43.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.2 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 32.2 kB or 60% of the original size.
Potential reduce by 34.9 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. Go.ekitan.com needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 83% of the original size.
Number of requests can be reduced by 11 (23%)
47
36
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go 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 5 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
go.ekitan.com
693 ms
common.css
326 ms
init.css
333 ms
layout.css
335 ms
main.css
673 ms
top_main.css
701 ms
ekitan_asp.log.js
354 ms
copyright.js
331 ms
ekitan_asp.atics.js
341 ms
header.css
178 ms
footer.css
207 ms
navi.css
329 ms
ekitan_asp_logo.png
177 ms
icon_ekitan.gif
178 ms
header_background.gif
177 ms
menu_homeOn.gif
179 ms
menu_home.gif
178 ms
menu_menuOn.gif
180 ms
menu_menu.gif
330 ms
menu_sampleOn.gif
333 ms
menu_sample.gif
335 ms
menu_exampleOn.gif
338 ms
menu_example.gif
351 ms
menu_ekitanOn.gif
353 ms
menu_ekitan.gif
494 ms
menu_contactOn.gif
497 ms
menu_contact.gif
501 ms
top_img.jpg
1007 ms
top_contact01.png
526 ms
top_contact02.png
528 ms
top_contact03.png
657 ms
camp01.png
1157 ms
top_content01_top.png
667 ms
top_content01_bottom.png
701 ms
top_content01_inside.png
704 ms
icon_link.png
820 ms
top_content02_top1.png
835 ms
top_content02_bottom1.png
877 ms
top_content02_inside1.png
878 ms
pr_express.png
984 ms
pr_banner_top.png
1168 ms
contact_background.png
1051 ms
contact_corporate.png
1055 ms
contact_dialnumber.png
1149 ms
contact_e-mail.png
1171 ms
gtm.js
71 ms
analytics.js
17 ms
collect
25 ms
go.ekitan.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
go.ekitan.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
go.ekitan.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Go.ekitan.com 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 Go.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.
go.ekitan.com
Open Graph description is not detected on the main page of Go 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: