Tools & Wizards About Us
shizenkaragenki.hamazo.tv screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

shizenkaragenki.hamazo.tv

自然から元気 サプリメント（健康補助食品）・スキンケア用品・美容雑貨・健康サポート用品・光触媒グッズのお店

Page Load Speed

6.4 sec in total

First Response

1.4 sec

Resources Loaded

4.5 sec

Page Rendered

488 ms

shizenkaragenki.hamazo.tv screenshot

About Website

Visit shizenkaragenki.hamazo.tv now to see the best up-to-date Shizenkaragenki Hamazo content for Japan and also check out these interesting facts you probably never knew about shizenkaragenki.hamazo.tv

サプリメント（健康補助食品）・スキンケア用品・光触媒関連グッズ・雑貨小物のお店「自然から元気」です。体の中から外から健康に美しくがキーワード☆ サプリメント管理士マスターの資格を持つ店長が皆さまのお悩みをサポートします　浜松市浜北区染地台3丁目20-20 ☎053-587-3118 shizenkaragenki@gmail.com

Visit shizenkaragenki.hamazo.tv

Key Findings

We analyzed Shizenkaragenki.hamazo.tv page load time and found that the first response time was 1.4 sec and then it took 5 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

shizenkaragenki.hamazo.tv performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value8,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.467

19/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

shizenkaragenki.hamazo.tv

1377 ms

header.css

534 ms

style.css

873 ms

gpt.js

99 ms

adsbygoogle.js

233 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 11% of them (12 requests) were addressed to the original Shizenkaragenki.hamazo.tv, 7% (8 requests) were made to Gstatic.com and 6% (7 requests) were made to Hamazo.tv. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Shizenkaragenki.hamazo.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 225.0 kB (17%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shizenkaragenki.hamazo.tv main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 89.1 kB

  • Original 111.7 kB
  • After minification 106.6 kB
  • After compression 22.6 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 89.1 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 13.3 kB

  • Original 94.6 kB
  • After minification 81.3 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, Shizenkaragenki Hamazo needs image optimization as it can save up to 13.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-10%

Potential reduce by 107.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 977.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. This website has mostly compressed JavaScripts.

CSS Optimization

-81%

Potential reduce by 15.5 kB

  • Original 19.3 kB
  • After minification 15.3 kB
  • After compression 3.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. Shizenkaragenki.hamazo.tv needs all CSS files to be minified and compressed as it can save up to 15.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (61%)

Requests Now

101

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

shizenkaragenki.hamazo.tv

shizenkaragenki.hamazo.tv

1377 ms

header.css

header.css

534 ms

style.css

style.css

873 ms

gpt.js

gpt.js

99 ms

adsbygoogle.js

adsbygoogle.js

233 ms

script.php

script.php

1154 ms

ticker.css

ticker.css

967 ms

ticker-ad.js

ticker-ad.js

513 ms

jsapi

jsapi

33 ms

t13n

t13n

36 ms

brand

brand

33 ms

clog_ad.js

clog_ad.js

1045 ms

adsbygoogle.js

adsbygoogle.js

321 ms

loader.js

loader.js

23 ms

brandjs.js

brandjs.js

27 ms

t13n

t13n

113 ms

pubads_impl.js

pubads_impl.js

27 ms

plusone.js

plusone.js

28 ms

greybox.js

greybox.js

344 ms

gb_styles.css

gb_styles.css

350 ms

counter.php

counter.php

748 ms

widgets.js

widgets.js

27 ms

loader.min.js

loader.min.js

118 ms

jquery.min.js

jquery.min.js

27 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

1107 ms

analytics.js

analytics.js

86 ms

a_01.gif

a_01.gif

83 ms

20080705_120620_41752500.jpg

20080705_120620_41752500.jpg

1094 ms

blog_subscription.png

blog_subscription.png

173 ms

admin_line_button.png

admin_line_button.png

174 ms

message.gif

message.gif

172 ms

social_twitter.png

social_twitter.png

174 ms

social_facebook.png

social_facebook.png

361 ms

arrow_right.png

arrow_right.png

581 ms

profile.JPG

profile.JPG

719 ms

blog_qr.png

blog_qr.png

885 ms

ticker_logo.gif

ticker_logo.gif

224 ms

icon_hamazo.gif

icon_hamazo.gif

719 ms

258.gif

258.gif

883 ms

149.gif

149.gif

887 ms

075.gif

075.gif

900 ms

show_ads_impl.js

show_ads_impl.js

290 ms

collect

collect

21 ms

collect

collect

31 ms

js

js

99 ms

js

js

51 ms

search32.png

search32.png

385 ms

link_icon.png

link_icon.png

564 ms

branding.png

branding.png

357 ms

hama07_03date.gif

hama07_03date.gif

412 ms

zrt_lookup.html

zrt_lookup.html

267 ms

ads

ads

866 ms

like.php

like.php

594 ms

ads

ads

658 ms

like.php

like.php

428 ms

ads

ads

173 ms

ads

ads

313 ms

container.html

container.html

200 ms

like.php

like.php

366 ms

like.php

like.php

492 ms

like.php

like.php

495 ms

ads

ads

511 ms

ga.js

ga.js

123 ms

ads

ads

350 ms

88_31.gif

88_31.gif

34 ms

88_31.gif

88_31.gif

93 ms

__utm.gif

__utm.gif

68 ms

__utm.gif

__utm.gif

68 ms

ads

ads

317 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

64 ms

a1393470.js

a1393470.js

1000 ms

ufs_web_display.js

ufs_web_display.js

54 ms

rm_bg.png

rm_bg.png

358 ms

XjQ1X4X-N6a.js

XjQ1X4X-N6a.js

163 ms

FEppCFCt76d.png

FEppCFCt76d.png

158 ms

sdk.js

sdk.js

109 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

114 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

89 ms

fastbutton

fastbutton

106 ms

settings

settings

140 ms

sdk.js

sdk.js

30 ms

postmessageRelay

postmessageRelay

118 ms

qr.png

qr.png

402 ms

reactive_library.js

reactive_library.js

199 ms

ca-pub-1829762579874733

ca-pub-1829762579874733

131 ms

developers.google.com

developers.google.com

645 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

50 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

83 ms

rpc:shindig_random.js

rpc:shindig_random.js

36 ms

embeds

embeds

107 ms

embeds

embeds

175 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

33 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

load_preloaded_resource.js

load_preloaded_resource.js

65 ms

abg_lite.js

abg_lite.js

61 ms

s

s

19 ms

window_focus.js

window_focus.js

103 ms

qs_click_protection.js

qs_click_protection.js

94 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

19 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

64 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

69 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

41 ms

f27db4b15126913483f917d94bc6c6c8.js

f27db4b15126913483f917d94bc6c6c8.js

67 ms

02bf16ec69b6c5aeb7fd4da5326fa0e5.js

02bf16ec69b6c5aeb7fd4da5326fa0e5.js

91 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

86 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

283 ms

activeview

activeview

94 ms

Accessibility Review

shizenkaragenki.hamazo.tv accessibility score

67

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.

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

shizenkaragenki.hamazo.tv best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

shizenkaragenki.hamazo.tv SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Shizenkaragenki.hamazo.tv 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 Shizenkaragenki.hamazo.tv 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

shizenkaragenki.hamazo.tv

Open Graph data is detected on the main page of Shizenkaragenki Hamazo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: