Tools & Wizards About Us
hohoem.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hohoem.jp

「ほほえみ生活」公式通販サイト |　気になるお悩みをサポートする健康食品・サプリメントがお求め頂けます。

Page Load Speed

5.5 sec in total

First Response

595 ms

Resources Loaded

4.5 sec

Page Rendered

420 ms

hohoem.jp screenshot

About Website

Welcome to hohoem.jp homepage info - get ready to check Hohoem best content right away, or after learning these important things about hohoem.jp

ほほえみ生活は、気になるお悩みをサポートする健康食品・サプリメントがお求め頂けます。

Visit hohoem.jp

Key Findings

We analyzed Hohoem.jp page load time and found that the first response time was 595 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

hohoem.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.285

42/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

hohoem.jp

595 ms

hohoem.jp

699 ms

default.css

178 ms

jquery-1.7.2.min.js

543 ms

common.css

712 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 93% of them (50 requests) were addressed to the original Hohoem.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Hohoem.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.9 kB (7%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hohoem.jp main page is 2.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. 25% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 11.0 kB

  • Original 15.4 kB
  • After minification 14.0 kB
  • After compression 4.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.0 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 117.7 kB

  • Original 2.1 MB
  • After minification 2.0 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. Hohoem images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 32.0 kB

  • Original 116.9 kB
  • After minification 116.9 kB
  • After compression 84.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 32.0 kB or 27% of the original size.

CSS Optimization

-26%

Potential reduce by 1.2 kB

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 3.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. Hohoem.jp needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (6%)

Requests Now

52

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hohoem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

hohoem.jp

hohoem.jp

595 ms

hohoem.jp

hohoem.jp

699 ms

default.css

default.css

178 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

543 ms

common.css

common.css

712 ms

jquery.min.js

jquery.min.js

18 ms

analytics.js

analytics.js

68 ms

hd_logo.png

hd_logo.png

353 ms

hd_tel.png

hd_tel.png

363 ms

top_tn.jpg

top_tn.jpg

1061 ms

tamenasihi_pkg.png

tamenasihi_pkg.png

869 ms

name_15.png

name_15.png

546 ms

btn_kwsk.png

btn_kwsk.png

703 ms

menou.png

menou.png

1077 ms

name_12.png

name_12.png

760 ms

rakusuta.png

rakusuta.png

1164 ms

name_03.png

name_03.png

881 ms

gokurakusuta.png

gokurakusuta.png

1511 ms

name_gr.png

name_gr.png

1048 ms

kikuluck.png

kikuluck.png

1397 ms

name_14.png

name_14.png

1225 ms

rakuonrakuwa.png

rakuonrakuwa.png

1248 ms

name_02.png

name_02.png

1259 ms

otopita.png

otopita.png

1553 ms

name_06.png

name_06.png

1401 ms

komuraex100.png

komuraex100.png

1433 ms

name_08.png

name_08.png

1441 ms

komurakiwami.png

komurakiwami.png

1746 ms

name_kmk.png

name_kmk.png

1590 ms

meikyoshisui.png

meikyoshisui.png

1617 ms

name_09.png

name_09.png

1625 ms

fuwaris.png

fuwaris.png

1709 ms

name_13.png

name_13.png

1752 ms

locoraku.png

locoraku.png

1936 ms

name_01.png

name_01.png

1799 ms

sakekasunonagomi.png

sakekasunonagomi.png

1983 ms

name_10.png

name_10.png

1903 ms

hyakusaimeiseki.png

hyakusaimeiseki.png

2093 ms

name_04.png

name_04.png

1951 ms

side_new.png

side_new.png

1982 ms

btn_new.png

btn_new.png

2101 ms

btn_login.png

btn_login.png

2115 ms

btn_pw.png

btn_pw.png

2148 ms

collect

collect

13 ms

js

js

69 ms

side_teiki.png

side_teiki.png

1821 ms

bnr_tel.png

bnr_tel.png

1806 ms

btn_newb.png

btn_newb.png

1728 ms

btn_loginb.png

btn_loginb.png

1594 ms

btn_pwb.png

btn_pwb.png

1539 ms

teiki.png

teiki.png

1486 ms

bnr_telb.png

bnr_telb.png

1471 ms

atobarai_newbanner468x64.png

atobarai_newbanner468x64.png

1308 ms

card.png

card.png

1393 ms

Accessibility Review

hohoem.jp accessibility score

77

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hohoem.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hohoem.jp SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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

Social Sharing Optimization

hohoem.jp

Open Graph description is not detected on the main page of Hohoem. 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: