3.8 sec in total
715 ms
2.9 sec
249 ms
Visit mogsnap.jp now to see the best up-to-date Mog Snap content and also check out these interesting facts you probably never knew about mogsnap.jp
もぐもぐエンターテイメント系Twitterクライアント/カメラアプリ「MogSnap」。「もぐもぐ」とはもちろん物を食べるときのあの幸せな音のこと。MogSnapはあなたのもぐもぐをTwitterで共有し、遊んでしまおうというiPhoneアプリです。
Visit mogsnap.jpWe analyzed Mogsnap.jp page load time and found that the first response time was 715 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mogsnap.jp performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value8.5 s
2/100
25%
Value7.6 s
25/100
10%
Value270 ms
82/100
30%
Value0.071
96/100
15%
Value7.6 s
46/100
10%
715 ms
354 ms
1033 ms
531 ms
533 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 56% of them (35 requests) were addressed to the original Mogsnap.jp, 16% (10 requests) were made to Static.xx.fbcdn.net and 6% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Mogsnap.jp.
Page size can be reduced by 418.0 kB (36%)
1.2 MB
734.6 kB
In fact, the total size of Mogsnap.jp main page is 1.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. 55% of websites need less resources to load. Images take 571.8 kB which makes up the majority of the site volume.
Potential reduce by 8.7 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 2.7 kB, which is 23% 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 8.7 kB or 72% of the original size.
Potential reduce by 7.9 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. Mog Snap images are well optimized though.
Potential reduce by 286.0 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 286.0 kB or 65% of the original size.
Potential reduce by 115.3 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. Mogsnap.jp needs all CSS files to be minified and compressed as it can save up to 115.3 kB or 88% of the original size.
Number of requests can be reduced by 33 (55%)
60
27
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mog Snap. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mogsnap.jp
715 ms
smartRollover.js
354 ms
jquery-1.3.2.js
1033 ms
jquery.page-scroller.js
531 ms
jquery.innerfade.js
533 ms
jquery.jscrollpane.min.js
748 ms
base.css
384 ms
main.css
525 ms
gAnalytics.js
435 ms
widgets.js
85 ms
widget.js
54 ms
tw.css
533 ms
ga.js
28 ms
bg_main.png
546 ms
toplogo.png
206 ms
btn_appstore_off.png
217 ms
btn_howto_off.png
207 ms
pht_iphone_01.jpg
703 ms
pht_iphone_02.jpg
774 ms
pht_iphone_03.jpg
553 ms
pht_iphone_04.jpg
730 ms
pht_iphone_05.jpg
769 ms
img_mooguu.png
728 ms
ttl_info.png
726 ms
btn_infolist_off.png
875 ms
mog_250_70.jpg
901 ms
bn_mogmag_off.jpg
903 ms
ttl_movie.png
904 ms
foot_logo.png
957 ms
btn_pagetop_off.png
966 ms
bg_iphone.png
1207 ms
bg_info_top.png
1059 ms
bg_info_bottom.png
1067 ms
bg_line_dot.png
1060 ms
icn_arrow_01.png
1122 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
158 ms
__utm.gif
26 ms
bg_movie.png
1095 ms
icn_twitter_off.png
1191 ms
icn_facebook_off.png
1193 ms
19890288
80 ms
likebox.php
269 ms
player.js
128 ms
player.css
102 ms
ga.js
72 ms
vuid.min.js
124 ms
__utm.gif
33 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
130 ms
proxy.html
65 ms
126529585.jpg
154 ms
hDvwL1_H7g-.css
35 ms
56WNbrUYLbL.css
38 ms
q68gy-v_YMF.js
43 ms
FJmpeSpHpjS.js
59 ms
0wM5s1Khldu.js
70 ms
1bNoFZUdlYZ.js
59 ms
227951_220440057974247_5992980_n.jpg
48 ms
wL6VQj7Ab77.png
9 ms
s7jcwEQH7Sx.png
6 ms
jot
93 ms
I6-MnjEovm5.js
14 ms
pQrUxxo5oQp.js
8 ms
mogsnap.jp accessibility score
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
mogsnap.jp 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
mogsnap.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mogsnap.jp 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 Mogsnap.jp 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.
mogsnap.jp
Open Graph description is not detected on the main page of Mog Snap. 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: