6.1 sec in total
430 ms
3.7 sec
2 sec
Visit g-matome.com now to see the best up-to-date G Matome content for Japan and also check out these interesting facts you probably never knew about g-matome.com
ガンダムシリーズを中心にまとめている2ちゃんねるまとめブログです。アニメ最新作、最新ガンプラ、関連ゲーム等の情報を幅広く扱っています!
Visit g-matome.comWe analyzed G-matome.com page load time and found that the first response time was 430 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
g-matome.com performance score
430 ms
321 ms
329 ms
77 ms
56 ms
Our browser made a total of 192 requests to load all elements on the main page. We found that 14% of them (26 requests) were addressed to the original G-matome.com, 20% (39 requests) were made to Resize.blogsys.jp and 12% (23 requests) were made to Livedoor.blogimg.jp. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Livedoor.blogimg.jp.
Page size can be reduced by 377.8 kB (15%)
2.5 MB
2.1 MB
In fact, the total size of G-matome.com main page is 2.5 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. 70% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 175.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. This page needs HTML code to be minified as it can gain 25.3 kB, which is 13% 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 175.1 kB or 87% of the original size.
Potential reduce by 28.2 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. G Matome images are well optimized though.
Potential reduce by 142.6 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 142.6 kB or 54% of the original size.
Potential reduce by 32.0 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. G-matome.com needs all CSS files to be minified and compressed as it can save up to 32.0 kB or 83% of the original size.
Number of requests can be reduced by 90 (47%)
191
101
The browser has sent 191 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G Matome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
g-matome.com
430 ms
template.css
321 ms
site.css
329 ms
jquery.min.js
77 ms
jquery.min.js
56 ms
c2.js
382 ms
smartphone.js
385 ms
ad.js
387 ms
popular_articles_with_image_plugin.js
530 ms
blogroll.js
722 ms
default2.css
462 ms
widgets.js
11 ms
bookmark_button.js
387 ms
rank.php
949 ms
rank.php
378 ms
recent_comments.js
377 ms
ga.js
36 ms
b98a14be.jpg
1177 ms
b98a14be.jpg
513 ms
c4fff929.jpg
590 ms
08583393.jpg
590 ms
0cc1fc67-s.jpg
590 ms
0f6e1ed5.jpg
590 ms
99d54e6a.jpg
593 ms
50084481.jpg
663 ms
6b1e9fb5-s.jpg
685 ms
993da7b6-s.jpg
686 ms
6b48d783.jpg
699 ms
8b98a0f8.jpg
699 ms
b66e77f8-s.jpg
721 ms
2baffade.jpg
823 ms
0f9a7879.jpg
895 ms
609163a3-s.jpg
978 ms
c4fff929.jpg
986 ms
08583393.jpg
1161 ms
0cc1fc67-s.jpg
1161 ms
0f6e1ed5.jpg
1055 ms
99d54e6a.jpg
1338 ms
50084481.jpg
1377 ms
6b1e9fb5-s.jpg
1661 ms
993da7b6-s.jpg
1510 ms
6b48d783.jpg
1509 ms
8b98a0f8.jpg
1510 ms
b66e77f8-s.jpg
1880 ms
2baffade.jpg
1979 ms
0f9a7879.jpg
2116 ms
609163a3-s.jpg
1980 ms
03f04015.jpg
1986 ms
918ceb36.jpg
1933 ms
b41f0346-s.jpg
2389 ms
e473d3ab-s.jpg
2433 ms
3dc9d915.jpg
2139 ms
db3221c1.jpg
2138 ms
19dc98c7.jpg
2785 ms
d93b78e6.jpg
2909 ms
rranking.gif
177 ms
button-only.gif
183 ms
rranking.gif
585 ms
c
326 ms
__utm.gif
13 ms
popular_articles.json
416 ms
line_r_top_right.gif
177 ms
line_r_bottom_right.gif
169 ms
line_r_top_left.gif
189 ms
line_r_bottom_left.gif
170 ms
roll_data
238 ms
roll_data
397 ms
roll_data
328 ms
r_bottom_right.gif
232 ms
r_bottom_left.gif
230 ms
r_top_left.gif
232 ms
r_top_right.gif
229 ms
category.gif
225 ms
show_ads.js
6 ms
222 ms
show_ads_impl.js
56 ms
ads
274 ms
osd.js
91 ms
info.json
405 ms
info.json
404 ms
info.json
404 ms
info.json
403 ms
info.json
457 ms
6b48d783.jpg
476 ms
0f9a7879.jpg
761 ms
2baffade.jpg
773 ms
0f6e1ed5.jpg
579 ms
50084481.jpg
761 ms
ads
210 ms
reset.css
22 ms
entry-button.css
20 ms
7fa8ae0a8e.png
200 ms
1.gif
198 ms
moro7.jpg
761 ms
blank.gif
408 ms
button-counter.gif
22 ms
aula.jpg
616 ms
blank.gif
342 ms
tukiichi5.jpg
584 ms
blank.gif
306 ms
side_top.gif
211 ms
side_bottom.gif
194 ms
side_body.gif
252 ms
popular_articles.json
497 ms
recent_comments.json
565 ms
0_yOXfyb1q.jpg
521 ms
a.gif
233 ms
bcs0
243 ms
creative_add_on.js
513 ms
creative_add_on.js
511 ms
bcs0
229 ms
0_yOXfyb1q.jpg
514 ms
a.gif
235 ms
ads
420 ms
u.js
405 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
55 ms
328 ms
329 ms
340 ms
324 ms
336 ms
343 ms
710 ms
444 ms
403 ms
444 ms
483 ms
679 ms
678 ms
706 ms
682 ms
824 ms
849 ms
850 ms
1014 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
157 ms
a.gif
89 ms
bcs0
87 ms
creative_add_on.js
89 ms
0_zVU9U9ia.jpg
89 ms
info.json
208 ms
info.json
409 ms
info.json
409 ms
info.json
413 ms
info.json
437 ms
info.json
406 ms
info.json
530 ms
info.json
711 ms
info.json
714 ms
info.json
718 ms
info.json
738 ms
info.json
721 ms
info.json
879 ms
info.json
1038 ms
info.json
1038 ms
6b48d783.jpg
192 ms
0f9a7879.jpg
404 ms
2baffade.jpg
404 ms
0f6e1ed5.jpg
208 ms
50084481.jpg
402 ms
6b1e9fb5-s.jpg
205 ms
99d54e6a.jpg
401 ms
b66e77f8-s.jpg
401 ms
8b98a0f8.jpg
405 ms
609163a3-s.jpg
550 ms
e473d3ab-s.jpg
682 ms
918ceb36.jpg
550 ms
03f04015.jpg
700 ms
993da7b6-s.jpg
551 ms
2f5664a3-s.jpg
556 ms
948b4a32-s.jpg
697 ms
6542b605-s.jpg
702 ms
1619eaf5.jpg
705 ms
c4fff929.jpg
736 ms
surly.js
132 ms
dvtp_src.js
74 ms
surly.js
143 ms
ba.html
55 ms
4.gif
183 ms
dvtp_src_internal26.js
42 ms
t2tv7.html
189 ms
visit.js
93 ms
2532.js
67 ms
avs5639.js
14 ms
event.gif
73 ms
query.js
64 ms
event.jpg
47 ms
box_19_top-right.png
37 ms
ci.png
40 ms
query.js
43 ms
jot.html
8 ms
event.gif
50 ms
g-matome.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G-matome.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 G-matome.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.
g-matome.com
Open Graph description is not detected on the main page of G Matome. 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: