7.8 sec in total
592 ms
6.7 sec
446 ms
Click here to check amazing Mediatope content. Otherwise, check out these important facts you probably never knew about mediatope.com
NTT Smart ConnectはIX直結の高速バックボーンを備えた西日本最大級のデータセンターで、ハウジング、ホスティング、クラウド、ストリーミングなど、お客さまのインターネットビジネスにあわせた多様なサービスをご提供します。
Visit mediatope.comWe analyzed Mediatope.com page load time and found that the first response time was 592 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mediatope.com performance score
592 ms
794 ms
328 ms
525 ms
397 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mediatope.com, 77% (44 requests) were made to Smartstream.ne.jp and 5% (3 requests) were made to Analytics.fs-bdash.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Smartstream.ne.jp.
Page size can be reduced by 589.3 kB (54%)
1.1 MB
492.9 kB
In fact, the total size of Mediatope.com main page is 1.1 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. 35% of websites need less resources to load. Images take 644.6 kB which makes up the majority of the site volume.
Potential reduce by 18.6 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 3.7 kB, which is 15% 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 18.6 kB or 76% of the original size.
Potential reduce by 281.0 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, Mediatope needs image optimization as it can save up to 281.0 kB or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 214.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 214.4 kB or 66% of the original size.
Potential reduce by 75.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. Mediatope.com needs all CSS files to be minified and compressed as it can save up to 75.2 kB or 83% of the original size.
Number of requests can be reduced by 24 (45%)
53
29
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mediatope. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
mediatope.com
592 ms
794 ms
fontello.css
328 ms
base.css
525 ms
header.css
397 ms
footer.css
400 ms
top.css
420 ms
mediatope.css
753 ms
print.css
695 ms
typesquare.js
297 ms
jquery.js
1316 ms
jquery.easing.js
770 ms
jquery.sliderPro.min.js
1387 ms
jquery.tile.min.js
917 ms
common.js
1067 ms
mediatope.js
1124 ms
prettyPhoto.css
397 ms
img_logo.gif
329 ms
header_phonenumber.png
348 ms
gheader_logo01.png
355 ms
gheader_logo02.png
375 ms
gheader_logo03.png
377 ms
gheader_logo04.png
400 ms
label.png
680 ms
logo.png
700 ms
index_img01.png
941 ms
index_img02.png
903 ms
index_img03.png
773 ms
index_img04.png
808 ms
index_img04_pc.png
1706 ms
pagetop.png
1076 ms
cvBox_tel.png
1136 ms
ftr_btn_contact_of.png
1858 ms
ftr_img_mark_01.gif
1272 ms
ftr_img_mark_02.gif
1317 ms
ftr_img_mark_03.gif
1450 ms
gtm.js
97 ms
mainvisual_bg.png
2469 ms
icon01.png
1660 ms
news_list_line.gif
1681 ms
cvBox_bg.png
1937 ms
pix-smartconnect-min.js
86 ms
fontello.woff
1946 ms
analytics.js
6 ms
s_retargeting.js
383 ms
conversion.js
20 ms
bd-TIG3QO-1.js
358 ms
collect
3 ms
collect
63 ms
ecotag.php
683 ms
bdash.js
618 ms
ftr_btn_contact_ov.png
1715 ms
create
153 ms
s_base.css
356 ms
s_header.css
327 ms
s_footer.css
423 ms
s_mediatope.css
399 ms
mediatope.com SEO score
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mediatope.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 Mediatope.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.
mediatope.com
Open Graph description is not detected on the main page of Mediatope. 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: