14.2 sec in total
2 sec
11.8 sec
420 ms
Welcome to tokyogamestation.com homepage info - get ready to check Tokyo Game Station best content for Japan right away, or after learning these important things about tokyogamestation.com
話題の人気ゲームや最新ガジェットから、トレンドニュース、定番の無料スマホアプリまで幅広くお届けする総合情報エンタメサイト。おすすめの人気ランキングも充実
Visit tokyogamestation.comWe analyzed Tokyogamestation.com page load time and found that the first response time was 2 sec and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tokyogamestation.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.8 s
15/100
25%
Value9.0 s
14/100
10%
Value530 ms
55/100
30%
Value0
100/100
15%
Value15.0 s
8/100
10%
1977 ms
1330 ms
1637 ms
1338 ms
1519 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 34% of them (43 requests) were addressed to the original Tokyogamestation.com, 19% (24 requests) were made to Ecx.images-amazon.com and 5% (6 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Tokyogamestation.com.
Page size can be reduced by 678.0 kB (42%)
1.6 MB
929.7 kB
In fact, the total size of Tokyogamestation.com main page is 1.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. 55% of websites need less resources to load. Javascripts take 709.1 kB which makes up the majority of the site volume.
Potential reduce by 83.2 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 83.2 kB or 84% of the original size.
Potential reduce by 6.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. Tokyo Game Station images are well optimized though.
Potential reduce by 446.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 446.3 kB or 63% of the original size.
Potential reduce by 142.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. Tokyogamestation.com needs all CSS files to be minified and compressed as it can save up to 142.2 kB or 75% of the original size.
Number of requests can be reduced by 50 (41%)
122
72
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyo Game Station. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
tokyogamestation.com
1977 ms
style.css
1330 ms
font-awesome.min.css
1637 ms
style.css
1338 ms
extension.css
1519 ms
responsive-pc.css
1368 ms
style.css
1924 ms
nendAdLoader.js
57 ms
screen.min.css
2346 ms
wpp.css
2361 ms
genericons.css
2751 ms
jetpack.css
2926 ms
jquery.js
3415 ms
jquery-migrate.min.js
2941 ms
show_ads.js
5 ms
ads.js
176 ms
javascript.js
3126 ms
javascript.js
2957 ms
photon.js
3362 ms
front.min.js
3699 ms
devicepx-jetpack.js
4 ms
gprofiles.js
58 ms
wpgroho.js
3532 ms
e-201611.js
4 ms
style.css
4170 ms
wp-emoji-release.min.js
1169 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-12-13-2.43.52.png
1380 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-18-0.38.42.png
1659 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-14-23.59.51.png
1649 ms
ir
120 ms
1654-featured-50x50.png
1358 ms
1233-featured-50x50.png
1319 ms
369-featured-50x50.png
1320 ms
1844-featured-50x50.png
1351 ms
1840-featured-50x50.png
1181 ms
2202-featured-50x50.png
2061 ms
2370-featured-50x50.png
2085 ms
2576-featured-50x50.png
2344 ms
2617-featured-50x50.png
2343 ms
2767-featured-50x50.png
2400 ms
2390-featured-50x50.png
2414 ms
2695-featured-50x50.png
2808 ms
2181-featured-50x50.png
2837 ms
2807-featured-50x50.png
3042 ms
1804-featured-50x50.png
3044 ms
2346-featured-50x50.png
3104 ms
2100-featured-50x50.png
3121 ms
1369-featured-50x50.png
3438 ms
3029-featured-50x50.png
3469 ms
2255-featured-50x50.png
3652 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-12-29-7.29.36.png
1612 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-06-14.39.10.png
1649 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-05-2.23.33.png
1664 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-12-08-0.12.24.png
1912 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-08-30-2.02.18.png
1834 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-12-19-22.20.54.png
2012 ms
IMG_3159.jpg
2595 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-12-20.09.30.png
2007 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-04-2.01.32.png
1304 ms
ir
167 ms
ir
181 ms
ir
184 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-19-0.39.25.png
2111 ms
IMG_3166-e1457788054972.jpg
2063 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-03-05-14.54.57.png
1423 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-11-04-1.52.59.png
1601 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2016-01-01-0.41.24.png
1639 ms
ca-pub-1775076322601858.js
45 ms
zrt_lookup.html
42 ms
show_ads_impl.js
58 ms
icomoon.woff
3781 ms
fontawesome-webfont.woff
4539 ms
ads-common.js
327 ms
ads
290 ms
osd.js
10 ms
ads
248 ms
ads
260 ms
41sbeKaWu5L._SL160_.jpg
10 ms
4106WZJVQCL._SL160_.jpg
10 ms
41FXZeRlZyL._SL160_.jpg
11 ms
61TGhfx%2Bp6L._SL160_.jpg
7 ms
cm
243 ms
cm
192 ms
cm
194 ms
sdk.js
275 ms
8937111602857308712
73 ms
abg.js
76 ms
m_js_controller.js
88 ms
googlelogo_color_112x36dp.png
66 ms
ga.js
32 ms
g.gif
61 ms
hovercard.css
48 ms
services.css
71 ms
__utm.gif
23 ms
s
20 ms
x_button_blue2.png
20 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
450x30-b-amzn.gif
10 ms
41v5MQEGEbL._SX60_SY90_.jpg
7 ms
buy-from-tan.gif
6 ms
410awytekzL._SX60_SY90_.jpg
6 ms
31+rGZKx41L._SX60_SY90_.jpg
12 ms
41e7ircmoTL._SX60_SY90_.jpg
11 ms
51Msu6HVAAL._SX60_SY90_.jpg
9 ms
41PYe008pVL._SX60_SY90_.jpg
13 ms
314qrrRlSqL._SX60_SY90_.jpg
14 ms
51o-qaE50SL._SX60_SY90_.jpg
9 ms
31pG0T94GcL._SX60_SY90_.jpg
11 ms
41yMoTp4BUL._SX60_SY90_.jpg
17 ms
180 ms
pv_assoc_General_300x250.jpg
6 ms
188 ms
primevideo_assoc_300x250.jpg
10 ms
51EihH7VSRL._SX60_SY90_.jpg
7 ms
208 ms
51gcXGk216L._SX60_SY90_.jpg
7 ms
123 ms
xd_arbiter.php
213 ms
xd_arbiter.php
422 ms
41e7ircmoTL._OU09_SL76_PI22-percent,BottomRight,0,0_CR0,0,60,76_.jpg
6 ms
41PYe008pVL._OU09_SL69_PI41-percent,BottomRight,0,0_CR0,0,60,69_.jpg
6 ms
314qrrRlSqL._OU09_SL60_PI28-percent,BottomRight,0,0_CR0,0,60,60_.jpg
7 ms
51gcXGk216L._OU09_SL77_PI31-percent,BottomRight,0,0_CR0,0,60,77_.jpg
8 ms
activeview
14 ms
print.css
432 ms
tokyogamestation.com accessibility score
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
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
tokyogamestation.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tokyogamestation.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyogamestation.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 Tokyogamestation.com 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.
tokyogamestation.com
Open Graph data is detected on the main page of Tokyo Game Station. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: