Tools & Wizards About Us
saien-navi.jp screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

saien-navi.jp

菜園ナビ｜家庭菜園ナビゲーター

Page Load Speed

6.7 sec in total

First Response

618 ms

Resources Loaded

5.9 sec

Page Rendered

183 ms

saien-navi.jp screenshot

About Website

Visit saien-navi.jp now to see the best up-to-date Saien Navi content for Japan and also check out these interesting facts you probably never knew about saien-navi.jp

菜園ナビ｜家庭菜園ナビゲーター 野菜の育て方を「学ぶ」、家庭菜園で野菜を「育てる」、菜園仲間と「つながりあう」。家庭菜園SNSの菜園ナビでもっと家庭菜園を楽しもう！

Visit saien-navi.jp

Key Findings

We analyzed Saien-navi.jp page load time and found that the first response time was 618 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

saien-navi.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

saien-navi.jp

618 ms

saien-navi.jp

1734 ms

jquery-1.8.3.js

683 ms

jquery-ui-1.9.2.custom.min.js

648 ms

jquery.ui.datepicker-ja.js

644 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 94% of them (77 requests) were addressed to the original Saien-navi.jp, 2% (2 requests) were made to Pagead2.googlesyndication.com and 2% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Saien-navi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 496.8 kB (43%)

Content Size

1.2 MB

After Optimization

669.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saien-navi.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. 40% of websites need less resources to load. Images take 670.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 117.2 kB

  • Original 141.0 kB
  • After minification 132.1 kB
  • After compression 23.8 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 117.2 kB or 83% of the original size.

Image Optimization

-50%

Potential reduce by 335.3 kB

  • Original 670.6 kB
  • After minification 335.4 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, Saien Navi needs image optimization as it can save up to 335.3 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 43.1 kB

  • Original 347.1 kB
  • After minification 347.1 kB
  • After compression 304.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 43.1 kB or 12% of the original size.

CSS Optimization

-17%

Potential reduce by 1.2 kB

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

Requests Breakdown

Number of requests can be reduced by 15 (19%)

Requests Now

80

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saien Navi. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

saien-navi.jp

saien-navi.jp

618 ms

saien-navi.jp

saien-navi.jp

1734 ms

jquery-1.8.3.js

jquery-1.8.3.js

683 ms

jquery-ui-1.9.2.custom.min.js

jquery-ui-1.9.2.custom.min.js

648 ms

jquery.ui.datepicker-ja.js

jquery.ui.datepicker-ja.js

644 ms

jquery.colorbox.js

jquery.colorbox.js

661 ms

jquery.balloon.js

jquery.balloon.js

697 ms

css.css

css.css

1138 ms

jquery.ui.all.css

jquery.ui.all.css

852 ms

colorbox.css

colorbox.css

853 ms

styles.css

styles.css

878 ms

js

js

79 ms

adsbygoogle.js

adsbygoogle.js

167 ms

jquery.elastic.js

jquery.elastic.js

684 ms

jquery.ui.base.css

jquery.ui.base.css

210 ms

jquery.ui.theme.css

jquery.ui.theme.css

209 ms

jquery.ui.core.css

jquery.ui.core.css

224 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

209 ms

header_main_bg.png

header_main_bg.png

235 ms

header_saien_logo.png

header_saien_logo.png

220 ms

s_icon.png

s_icon.png

219 ms

qaicon.png

qaicon.png

232 ms

menu_bg.png

menu_bg.png

233 ms

home80.png

home80.png

220 ms

saien80.png

saien80.png

414 ms

blog80.png

blog80.png

415 ms

saien_book80.png

saien_book80.png

436 ms

guide80.png

guide80.png

440 ms

go.png

go.png

444 ms

index_newregister_btn.png

index_newregister_btn.png

445 ms

beginner_btn.png

beginner_btn.png

621 ms

fb.png

fb.png

623 ms

tw.png

tw.png

655 ms

yt.png

yt.png

659 ms

plus_login.png

plus_login.png

666 ms

comment_icon.png

comment_icon.png

667 ms

icondirect.php

icondirect.php

828 ms

icondirect.php

icondirect.php

832 ms

wakaba_icon.png

wakaba_icon.png

875 ms

icondirect.php

icondirect.php

880 ms

icondirect.php

icondirect.php

888 ms

40_40.png

40_40.png

890 ms

today's_column_icon.png

today's_column_icon.png

1036 ms

thumbnail.php

thumbnail.php

1089 ms

everyone_contribute_icon.png

everyone_contribute_icon.png

1092 ms

content_titile.png

content_titile.png

1099 ms

news_header.png

news_header.png

1111 ms

event.png

event.png

1112 ms

info.png

info.png

1243 ms

tv.png

tv.png

1296 ms

magazin.png

magazin.png

1310 ms

radio.png

radio.png

1318 ms

saien_log_b.png

saien_log_b.png

1555 ms

show_ads_impl.js

show_ads_impl.js

245 ms

nouken.png

nouken.png

1202 ms

chlorella_specialpage_b2.png

chlorella_specialpage_b2.png

1442 ms

saicon_all.png

saicon_all.png

1289 ms

11th_contest_b.png

11th_contest_b.png

1739 ms

seedball.png

seedball.png

1530 ms

cp03_b.png

cp03_b.png

1330 ms

matome_site.png

matome_site.png

1483 ms

zrt_lookup.html

zrt_lookup.html

19 ms

ads

ads

84 ms

off_bn.png

off_bn.png

1370 ms

orec_virtual.png

orec_virtual.png

1372 ms

footer_illust.png

footer_illust.png

1430 ms

matome.png

matome.png

1484 ms

fb.png

fb.png

1538 ms

tw.png

tw.png

1560 ms

yt.png

yt.png

1388 ms

orec.png

orec.png

1449 ms

green_bg.png

green_bg.png

1476 ms

youkoso.png

youkoso.png

1529 ms

fukidashi2.png

fukidashi2.png

1535 ms

link_sprouts_mini.png

link_sprouts_mini.png

1559 ms

link_planter.png

link_planter.png

1401 ms

tsuchidukuri.png

tsuchidukuri.png

1445 ms

guide.png

guide.png

1464 ms

n_news.png

n_news.png

1525 ms

footer_bg.png

footer_bg.png

1531 ms

pagetop.png

pagetop.png

1560 ms

overlay.png

overlay.png

1416 ms

Accessibility Review

saien-navi.jp accessibility score

65

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

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

saien-navi.jp best practices score

67

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

High

Page has valid source maps

SEO Factors

saien-navi.jp SEO score

92

Search Engine Optimization Advices

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 Saien-navi.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 Saien-navi.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

saien-navi.jp

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