9.8 sec in total
538 ms
8.9 sec
438 ms
Welcome to osaka-motorshow.com homepage info - get ready to check Osaka Motorshow best content for Japan right away, or after learning these important things about osaka-motorshow.com
2019年12月6日(金)~12月9日(月)にインテックス大阪にて開催の第11回 大阪モーターショー 出展者を募集しています。「Restart! ~新たなステージへ~」
Visit osaka-motorshow.comWe analyzed Osaka-motorshow.com page load time and found that the first response time was 538 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
osaka-motorshow.com performance score
538 ms
653 ms
340 ms
315 ms
346 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 41% of them (64 requests) were addressed to the original Osaka-motorshow.com, 13% (20 requests) were made to Abs.twimg.com and 12% (19 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Eqb088mzwq.eq.webcdn.stream.ne.jp.
Page size can be reduced by 681.7 kB (31%)
2.2 MB
1.5 MB
In fact, the total size of Osaka-motorshow.com main page is 2.2 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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 26.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. 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 26.1 kB or 76% of the original size.
Potential reduce by 4.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. Osaka Motorshow images are well optimized though.
Potential reduce by 635.5 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 635.5 kB or 79% of the original size.
Potential reduce by 15.6 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. Osaka-motorshow.com needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 73% of the original size.
Number of requests can be reduced by 58 (38%)
154
96
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Osaka Motorshow. 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 13 to 1 for CSS and as a result speed up the page load time.
osaka-motorshow.com
538 ms
www.osaka-motorshow.com
653 ms
reset.css
340 ms
common.css
315 ms
top.css
346 ms
top_media.css
324 ms
ui.tabs.css
315 ms
colorbox.css
343 ms
jquery-1.8.2.min.js
1025 ms
jquery.colorbox-min.js
499 ms
scrolltopcontrol.js
507 ms
flexcroll.js
549 ms
jquery-ui.min.js
1351 ms
ui.core.js
574 ms
ui.tabs.js
803 ms
obj.js
2555 ms
top_logo_e.gif
178 ms
top_logo_j.gif
170 ms
top_muryo.gif
151 ms
top_date.gif
178 ms
top_intex.gif
174 ms
top_chach.gif
172 ms
nav01.gif
331 ms
nav02.gif
333 ms
nav03.gif
334 ms
nav04.gif
337 ms
nav05.gif
334 ms
nav06.gif
335 ms
ttl_zenkai.gif
460 ms
btn_zen.gif
462 ms
p_zen01_thum.jpg
637 ms
p_zen02_thum.jpg
642 ms
p_zen03_thum.jpg
511 ms
p_zen04_thum.jpg
647 ms
p_zen05_thum.jpg
616 ms
raijyosya.gif
604 ms
ttl_ticket.gif
697 ms
ticket_pp.gif
782 ms
ttl_news.gif
761 ms
ttl_movie.gif
786 ms
bnr_tr342_manpuku.jpg
962 ms
ttl_sns_fb.gif
789 ms
ttl_sns_tw.gif
850 ms
bnr_s01_180-60.gif
908 ms
bnr_nms2015_180-60.gif
987 ms
bnr_hms_108-60.jpg
928 ms
bnr_tms2016_180-60.gif
1024 ms
sdk.js
269 ms
top_visual_fin.jpg
1322 ms
nav_bg.gif
1038 ms
nav01_on.gif
1059 ms
nav02_on.gif
1088 ms
nav03_on.gif
1121 ms
nav04_on.gif
1063 ms
nav05_on.gif
1059 ms
nav06_on.gif
1083 ms
nav_top_light.gif
1101 ms
bg_cont.gif
1145 ms
ttl_info.gif
1169 ms
mov_nav05.gif
1042 ms
mov_nav04.gif
1087 ms
mov_nav03.gif
1144 ms
140 ms
xd_arbiter.php
211 ms
xd_arbiter.php
415 ms
object.css
3052 ms
service.jsonp
2952 ms
top_bg_sns.gif
168 ms
637.jsonp
231 ms
top_kage.png
165 ms
widgets.js
83 ms
analytics.js
43 ms
btn_pt.png
156 ms
collect
15 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
126 ms
page.php
281 ms
e_ico.png
174 ms
hl.png
197 ms
hr.png
373 ms
bl.png
357 ms
br.png
354 ms
syndication
99 ms
627011697639731200
282 ms
service.jsonp
256 ms
SjqsVDvTIBF.css
419 ms
AAMYCR68qe3.css
427 ms
MKiDk2JIhZf.css
547 ms
jPzGNhmtg40.css
613 ms
_rx8naC75Dy.js
691 ms
3o1espZ6Mhb.js
614 ms
nfTYZZc0iSn.js
750 ms
SFuJyO56WQT.js
614 ms
pJPDNGWM_rf.js
775 ms
1f697.png
64 ms
1f493.png
57 ms
2728.png
59 ms
1f4aa.png
59 ms
1f495.png
86 ms
1f3bb.png
86 ms
1f3b9.png
94 ms
1f3b6.png
86 ms
2600.png
94 ms
1f601.png
95 ms
2757.png
98 ms
1f64a.png
95 ms
1f353.png
95 ms
2665.png
96 ms
1f31f.png
124 ms
1f698.png
123 ms
1f3c1.png
123 ms
1f62d.png
123 ms
1f49b.png
122 ms
203c.png
118 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
36 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
212 ms
637.jsonp
230 ms
h9EWkvBO_normal.png
309 ms
f1ULs480_normal.jpg
295 ms
Avu_HqLB_normal.jpg
192 ms
e_fBmkaD_normal.jpg
295 ms
VeVSu0E2_normal.jpeg
192 ms
J1NVV_Jd_normal.png
303 ms
UOJiTZMa_normal.jpg
187 ms
WQ6XP_gV_normal.jpg
188 ms
CVlkQI9UwAAWuTh.jpg:large
378 ms
CVhqE0XUwAAEWq8.jpg
299 ms
CVhQrimU8AASFS7.jpg
388 ms
CVhLEeXUAAA9vUn.jpg
378 ms
CVa5RQCWcAAAFAh.jpg
468 ms
CVgMtyPUYAAzrgu.jpg
410 ms
CVek-OfUAAE3WaR.jpg
742 ms
CVXfy8yUsAAjQKf.jpg
741 ms
CVXhQbvU4AAwA6J.jpg
585 ms
CVWFr0AVEAELOfR.jpg
520 ms
CVSYch9UEAA3kY7.jpg
742 ms
service.jsonp
180 ms
639.jsonp
280 ms
jot
25 ms
10277792_433425323506375_6205089767428395307_n.jpg
346 ms
safe_image.php
515 ms
12341163_490839331098307_4199859907621726818_n.jpg
465 ms
12345600_490773134438260_4533552075305263758_n.jpg
666 ms
12316381_490773174438256_1820738864670465219_n.jpg
667 ms
12341140_490765854438988_304008888939548448_n.jpg
668 ms
12316518_490742724441301_8154893963678261071_n.jpg
666 ms
wL6VQj7Ab77.png
163 ms
s7jcwEQH7Sx.png
165 ms
bNvHN6v1NeH.png
165 ms
b53Ajb4ihCP.gif
166 ms
LT9rONw9UJp.png
165 ms
lRyN50VcaFW.js
79 ms
R9a_DtVRZgv.js
73 ms
cUDgRFxaoIk.js
72 ms
0JBr1QHp8Gi.js
69 ms
kDOzhTr2W91.js
69 ms
bg_scroller.gif
230 ms
osaka-motorshow.com SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osaka-motorshow.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 Osaka-motorshow.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.
osaka-motorshow.com
Open Graph data is detected on the main page of Osaka Motorshow. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: