Tools & Wizards About Us
ichikoen.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ichikoen.com

ぶどう狩りは山梨県勝沼町のぶどう園一古園

Page Load Speed

6.6 sec in total

First Response

547 ms

Resources Loaded

5.7 sec

Page Rendered

386 ms

ichikoen.com screenshot

About Website

Welcome to ichikoen.com homepage info - get ready to check Ichikoen best content for Japan right away, or after learning these important things about ichikoen.com

"おいしいぶどうを食べて頂きたい" これが一古園のコンセプトです。ご来園いただく方の為に安心で安全な栽培を行い、丹精を込めて栽培しています。 ぶどうの産地しか味わう事の出来ない、新鮮で美味しいぶどう狩りをお楽しみください。

Visit ichikoen.com

Key Findings

We analyzed Ichikoen.com page load time and found that the first response time was 547 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 75% of websites can load faster.

Performance Metrics

ichikoen.com performance score

0

Network Requests Diagram

ichikoen.com

547 ms

www.ichikoen.com

703 ms

style.css

315 ms

AC_RunActiveContent.js

491 ms

swfobject_modified.js

732 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Ichikoen.com, 5% (3 requests) were made to Vip2.counter.yaboo.jp and 2% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Ichikoen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.6 kB (23%)

Content Size

272.9 kB

After Optimization

210.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ichikoen.com main page is 272.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 197.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 33.1 kB

  • Original 38.7 kB
  • After minification 29.0 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 25% 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 33.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 23 B

  • Original 197.2 kB
  • After minification 197.2 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. Ichikoen images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 26.6 kB

  • Original 33.4 kB
  • After minification 21.6 kB
  • After compression 6.8 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.6 kB or 80% of the original size.

CSS Optimization

-81%

Potential reduce by 2.9 kB

  • Original 3.6 kB
  • After minification 3.1 kB
  • After compression 693 B

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. Ichikoen.com needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ichikoen. 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

ichikoen.com

ichikoen.com

547 ms

www.ichikoen.com

www.ichikoen.com

703 ms

style.css

style.css

315 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

491 ms

swfobject_modified.js

swfobject_modified.js

732 ms

c.js

c.js

1318 ms

get_flash_player.gif

get_flash_player.gif

91 ms

www.ichikoen.com

www.ichikoen.com

334 ms

bn_header_2.gif

bn_header_2.gif

463 ms

bn_header_1.gif

bn_header_1.gif

659 ms

bn_header_2_1.jpg

bn_header_2_1.jpg

332 ms

spacer.gif

spacer.gif

358 ms

bn_header_2_2.jpg

bn_header_2_2.jpg

359 ms

bn_header_2_3.jpg

bn_header_2_3.jpg

668 ms

spacer.gif

spacer.gif

689 ms

menu_r1_c1.gif

menu_r1_c1.gif

663 ms

menu_r3_c2_f2.gif

menu_r3_c2_f2.gif

729 ms

menu_r5_c2.gif

menu_r5_c2.gif

788 ms

menu_r7_c2.gif

menu_r7_c2.gif

965 ms

menu_r9_c2.gif

menu_r9_c2.gif

976 ms

menu_r11_c2.gif

menu_r11_c2.gif

990 ms

menu_r13_c2.gif

menu_r13_c2.gif

1016 ms

menu_r15_c2.gif

menu_r15_c2.gif

1084 ms

menu_r17_c1.gif

menu_r17_c1.gif

1119 ms

bn_open.jpg

bn_open.jpg

1581 ms

spacer.gif

spacer.gif

1334 ms

contents_tabl_top_plan2.gif

contents_tabl_top_plan2.gif

1491 ms

contents_tableset_r2_c1.gif

contents_tableset_r2_c1.gif

1324 ms

contents_tableset_r2_c2.gif

contents_tableset_r2_c2.gif

1440 ms

line_dot.gif

line_dot.gif

1454 ms

komidashi_b_tabehoudai.gif

komidashi_b_tabehoudai.gif

1648 ms

sentaku_a.jpg

sentaku_a.jpg

2030 ms

komidashi_ktabeho.gif

komidashi_ktabeho.gif

1794 ms

sentaku_b.jpg

sentaku_b.jpg

1954 ms

bn_ganso.gif

bn_ganso.gif

1799 ms

contents_tableset_r2_c3.gif

contents_tableset_r2_c3.gif

1910 ms

contents_tableset_r4_c1.gif

contents_tableset_r4_c1.gif

1953 ms

contents_tabl_top_spplan.gif

contents_tabl_top_spplan.gif

2116 ms

special.jpg

special.jpg

2620 ms

komidashi_manpuku.gif

komidashi_manpuku.gif

2274 ms

komidashi_spa.gif

komidashi_spa.gif

2288 ms

contents_tabl_top_osyokuji_set.gif

contents_tabl_top_osyokuji_set.gif

2323 ms

komidashi_syokuji_a.gif

komidashi_syokuji_a.gif

2313 ms

komidashi_syokuji_b.gif

komidashi_syokuji_b.gif

2096 ms

bg_bentou.gif

bg_bentou.gif

2440 ms

bn_201308jpg.jpg

bn_201308jpg.jpg

3095 ms

bn_bottom.gif

bn_bottom.gif

2318 ms

bn_pg_bottom.gif

bn_pg_bottom.gif

2286 ms

546 ms

462 ms

menu_r5_c2_f2.gif

menu_r5_c2_f2.gif

169 ms

menu_r7_c2_f2.gif

menu_r7_c2_f2.gif

311 ms

menu_r9_c2_f2.gif

menu_r9_c2_f2.gif

335 ms

menu_r11_c2_f2.gif

menu_r11_c2_f2.gif

338 ms

menu_r13_c2_f2.gif

menu_r13_c2_f2.gif

356 ms

menu_r15_c2_f2.gif

menu_r15_c2_f2.gif

364 ms

SEO Factors

ichikoen.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ichikoen.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ichikoen.com 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

ichikoen.com

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