5.1 sec in total
1 sec
3.8 sec
214 ms
Click here to check amazing Humhug content. Otherwise, check out these important facts you probably never knew about humhug.net
食と農から家族みんなの元気なココロとカラダづくりを応援します。
Visit humhug.netWe analyzed Humhug.net page load time and found that the first response time was 1 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
humhug.net performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.1 s
100/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
1040 ms
11 ms
751 ms
9 ms
114 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 30% of them (18 requests) were addressed to the original Humhug.net, 37% (22 requests) were made to Pbs.twimg.com and 8% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Humhug.net.
Page size can be reduced by 282.7 kB (20%)
1.4 MB
1.1 MB
In fact, the total size of Humhug.net main page is 1.4 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. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 17.0 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 4.0 kB, which is 16% 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 17.0 kB or 70% of the original size.
Potential reduce by 184.1 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, Humhug needs image optimization as it can save up to 184.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 26.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 26.5 kB or 41% of the original size.
Potential reduce by 55.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. Humhug.net needs all CSS files to be minified and compressed as it can save up to 55.0 kB or 86% of the original size.
Number of requests can be reduced by 13 (22%)
59
46
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Humhug. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.humhug.net
1040 ms
cssreset-min.css
11 ms
style.css
751 ms
show_ads.js
9 ms
ga.js
114 ms
wp-emoji-release.min.js
792 ms
rogo_humhug.png
247 ms
get_flash_player.gif
89 ms
vertical_line.png
401 ms
top_twitter.jpg
372 ms
top_twitter_on.gif
373 ms
topics.png
451 ms
top_menu.png
1692 ms
0404_TOPgienkin.gif
435 ms
banner_mamakoe.gif
585 ms
fan_banner.gif
534 ms
banner_kame_95_50.gif
538 ms
homama234_60.png
1066 ms
top_banner_kosegare.gif
590 ms
bnr.jpg
1077 ms
onigokko.png
1054 ms
trippi-kids.banner_230_98.png
1323 ms
__utm.gif
45 ms
widgets.js
33 ms
ca-pub-6286839980949991.js
303 ms
zrt_lookup.html
240 ms
show_ads_impl.js
81 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
167 ms
osd.js
60 ms
syndication
94 ms
378322983900569601
220 ms
proxy.jpg
106 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
8 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
26 ms
bf477cd507a261b1d481a46a054fe4a3_normal.jpeg
189 ms
humhug_normal.jpg
232 ms
twitter_icon_normal.gif
221 ms
326286e6f20f212a93a3be2a8a04c021_normal.png
221 ms
l2roUGUl_normal.png
223 ms
sinboru_normal.gif
226 ms
64b682b7e937f4e764bc4c2081e680c0_normal.jpeg
222 ms
fu6qgxa6l4troz53xho7_normal.jpeg
342 ms
elZRgRtr_normal.jpeg
358 ms
hokuwalk_07_normal.jpg
342 ms
02-042-05C_normal.JPG
341 ms
1kbbd-PN_normal.jpeg
345 ms
P55VpaPg_normal.jpg
341 ms
n544536943_151798_4645_normal.jpg
340 ms
CdJ-MKhUAAIZo1J.jpg:small
341 ms
CYKowyMVAAA2qyB.jpg:small
353 ms
CYKoEuxVAAA5Ox4.png:small
361 ms
CWKowMUU4AAus0W.jpg:small
352 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
173 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
210 ms
CdJ-MKhUAAIZo1J.jpg:large
184 ms
CYKowyMVAAA2qyB.jpg:large
181 ms
CYKoEuxVAAA5Ox4.png:large
244 ms
CWKowMUU4AAus0W.jpg:large
4 ms
proxy.jpg
26 ms
jot.html
2 ms
humhug.net accessibility score
humhug.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
humhug.net SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Humhug.net 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 Humhug.net 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.
humhug.net
Open Graph description is not detected on the main page of Humhug. 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: