Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

humhug.net

はむはぐ 休止のご案内

Page Load Speed

5.1 sec in total

First Response

1 sec

Resources Loaded

3.8 sec

Page Rendered

214 ms

humhug.net screenshot

About Website

Click here to check amazing Humhug content. Otherwise, check out these important facts you probably never knew about humhug.net

食と農から家族みんなの元気なココロとカラダづくりを応援します。

Visit humhug.net

Key Findings

We 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.

Performance Metrics

humhug.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

www.humhug.net

1040 ms

cssreset-min.css

11 ms

style.css

751 ms

show_ads.js

9 ms

ga.js

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 Optimization Overview & Recommendations

Page size can be reduced by 282.7 kB (20%)

Content Size

1.4 MB

After Optimization

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.

HTML Optimization

-70%

Potential reduce by 17.0 kB

  • Original 24.2 kB
  • After minification 20.3 kB
  • After compression 7.2 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.

Image Optimization

-15%

Potential reduce by 184.1 kB

  • Original 1.3 MB
  • After minification 1.1 MB

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.

JavaScript Optimization

-41%

Potential reduce by 26.5 kB

  • Original 65.5 kB
  • After minification 65.3 kB
  • After compression 38.9 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.

CSS Optimization

-86%

Potential reduce by 55.0 kB

  • Original 63.6 kB
  • After minification 51.4 kB
  • After compression 8.7 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.

Requests Breakdown

Number of requests can be reduced by 13 (22%)

Requests Now

59

After Optimization

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.

Accessibility Review

humhug.net accessibility score

100

Accessibility Issues

Best Practices

humhug.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

humhug.net SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: