Tools & Wizards About Us
enoshima-yacht-harbor.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

enoshima-yacht-harbor.jp

Index of /

Page Load Speed

15.4 sec in total

First Response

616 ms

Resources Loaded

13.8 sec

Page Rendered

896 ms

enoshima-yacht-harbor.jp screenshot

About Website

Visit enoshima-yacht-harbor.jp now to see the best up-to-date Enoshima Yacht Harbor content for Japan and also check out these interesting facts you probably never knew about enoshima-yacht-harbor.jp

神奈川県藤沢市の湘南海岸で、8つの駐車場を運営しています。駐車場の空き状況や、周辺のテニスコート・湘南スケートパーク・江の島ヨットハーバー・湘南海岸公園・江の島観光の情報が満載。湘南行くならまずチェック!

Visit enoshima-yacht-harbor.jp

Key Findings

We analyzed Enoshima-yacht-harbor.jp page load time and found that the first response time was 616 ms and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

enoshima-yacht-harbor.jp performance score

0

Network Requests Diagram

enoshima-yacht-harbor.jp

616 ms

2347 ms

common.css

458 ms

common.css

646 ms

AllUnits.css

979 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Enoshima-yacht-harbor.jp, 94% (84 requests) were made to S-n-p.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (8.8 sec) relates to the external source S-n-p.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (13%)

Content Size

8.7 MB

After Optimization

7.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Enoshima-yacht-harbor.jp main page is 8.7 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. 55% of websites need less resources to load. Images take 7.6 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 148.0 kB

  • Original 162.1 kB
  • After minification 148.6 kB
  • After compression 14.1 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 148.0 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 265.2 kB

  • Original 7.6 MB
  • After minification 7.3 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. Enoshima Yacht Harbor images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 504.2 kB

  • Original 686.2 kB
  • After minification 611.1 kB
  • After compression 181.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 504.2 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 223.8 kB

  • Original 253.0 kB
  • After minification 189.3 kB
  • After compression 29.2 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. Enoshima-yacht-harbor.jp needs all CSS files to be minified and compressed as it can save up to 223.8 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (44%)

Requests Now

86

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

enoshima-yacht-harbor.jp

enoshima-yacht-harbor.jp

616 ms

2347 ms

common.css

common.css

458 ms

common.css

common.css

646 ms

AllUnits.css

AllUnits.css

979 ms

common.css

common.css

326 ms

common_skin.css

common_skin.css

986 ms

lightbox.css

lightbox.css

455 ms

jquery-ui-1.8.23.custom.css

jquery-ui-1.8.23.custom.css

812 ms

mobiscroll-2.0.1.custom.min.css

mobiscroll-2.0.1.custom.min.css

609 ms

jquery.poplayer.css

jquery.poplayer.css

607 ms

fontello-ie7.css

fontello-ie7.css

759 ms

jquery.bbgscroll.css

jquery.bbgscroll.css

759 ms

imported.min.js

imported.min.js

804 ms

prototype-old.js

prototype-old.js

1515 ms

scriptaculous.js

scriptaculous.js

910 ms

livepipe.js

livepipe.js

964 ms

tabs.js

tabs.js

972 ms

device.min.js

device.min.js

1063 ms

modernizr.custom.js

modernizr.custom.js

1126 ms

jquery-min.js

jquery-min.js

1458 ms

jquery-ui.custom.min.js

jquery-ui.custom.min.js

1622 ms

jquery.easing.js

jquery.easing.js

1143 ms

jquery.inview.min.js

jquery.inview.min.js

1214 ms

lightbox.js

lightbox.js

1284 ms

flipsnap.min.js

flipsnap.min.js

1308 ms

mobiscroll-2.0.1.custom.min.js

mobiscroll-2.0.1.custom.min.js

1366 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

1446 ms

jquery.backgroundSize.js

jquery.backgroundSize.js

1472 ms

bingo_bg_video.js

bingo_bg_video.js

1521 ms

extCatList.js

extCatList.js

1467 ms

coverFade.js

coverFade.js

1327 ms

coverSlide.js

coverSlide.js

1345 ms

jquery.bscroller.js

jquery.bscroller.js

1369 ms

jquery.bfixer.js

jquery.bfixer.js

1380 ms

jquery.bhover.js

jquery.bhover.js

1476 ms

ddsmoothmenu.js

ddsmoothmenu.js

1489 ms

skin.js

skin.js

1489 ms

effects.js

effects.js

283 ms

builder.js

builder.js

295 ms

webfont.js

webfont.js

13 ms

analytics.js

analytics.js

19 ms

btn_header02.png

btn_header02.png

381 ms

btn_header01.png

btn_header01.png

376 ms

7-logo.gif

7-logo.gif

375 ms

img_gnavi01.jpg

img_gnavi01.jpg

373 ms

img_gnavi02.jpg

img_gnavi02.jpg

374 ms

img_gnavi03.jpg

img_gnavi03.jpg

373 ms

img_gnavi04.jpg

img_gnavi04.jpg

375 ms

img_gnavi05.jpg

img_gnavi05.jpg

375 ms

img_gnavi06.jpg

img_gnavi06.jpg

376 ms

852-10-20151203155003_b565fe61b3341c.jpg

852-10-20151203155003_b565fe61b3341c.jpg

665 ms

tmpimg.php

tmpimg.php

400 ms

4888-1-20151029101252_b5631729435ef0.png

4888-1-20151029101252_b5631729435ef0.png

376 ms

c343-0-20151023130351_b5629b1a7212a9.jpg

c343-0-20151023130351_b5629b1a7212a9.jpg

6252 ms

2232-1-20151026143937_b562dbc9964668.jpg

2232-1-20151026143937_b562dbc9964668.jpg

1065 ms

2232-1-20151022185510_b5628b27e0e509.png

2232-1-20151022185510_b5628b27e0e509.png

490 ms

2231-1-20151022185554_b5628b2aabae2f.png

2231-1-20151022185554_b5628b2aabae2f.png

496 ms

2231-1-20151022185554_b5628b2aabb602.png

2231-1-20151022185554_b5628b2aabb602.png

552 ms

2230-1-20151023104403_b562990e3150ab.jpg

2230-1-20151023104403_b562990e3150ab.jpg

1290 ms

2230-1-20151022185448_b5628b2684fbbc.png

2230-1-20151022185448_b5628b2684fbbc.png

663 ms

2234-1-20151023154318_b5629d70653a4e.jpg

2234-1-20151023154318_b5629d70653a4e.jpg

1033 ms

2234-1-20151022185524_b5628b28c52d5b.png

2234-1-20151022185524_b5628b28c52d5b.png

816 ms

1536-1-20151124162946_b565411eaef7f0.jpg

1536-1-20151124162946_b565411eaef7f0.jpg

828 ms

8205-1-20151124163008_b565412001bd03.jpg

8205-1-20151124163008_b565412001bd03.jpg

979 ms

2006-1-20151022163503_b562891a765449.jpg

2006-1-20151022163503_b562891a765449.jpg

993 ms

1989-1-20151022164726_b5628948ea32d6.png

1989-1-20151022164726_b5628948ea32d6.png

1144 ms

2013-1-20151022165302_b562895de0695a.png

2013-1-20151022165302_b562895de0695a.png

1157 ms

2015-1-20151022171933_b56289c153dc94.png

2015-1-20151022171933_b56289c153dc94.png

1195 ms

2016-1-20151022173914_b5628a0b2cc230.png

2016-1-20151022173914_b5628a0b2cc230.png

1214 ms

2048-1-20151022170943_b562899c715c30.png

2048-1-20151022170943_b562899c715c30.png

1307 ms

2007-1-20151022172534_b56289d7ef4069.png

2007-1-20151022172534_b56289d7ef4069.png

1321 ms

2014-1-20151022173244_b56289f2cad75c.png

2014-1-20151022173244_b56289f2cad75c.png

1358 ms

2012-1-20151022171546_b56289b321adc2.png

2012-1-20151022171546_b56289b321adc2.png

1365 ms

2864-1-20151026110410_b562d8a1ab714e.png

2864-1-20151026110410_b562d8a1ab714e.png

1448 ms

5907-1-20151029171434_b5631d56a89aaf.png

5907-1-20151029171434_b5631d56a89aaf.png

1468 ms

6516-1-20151029190835_b5631f02378573.png

6516-1-20151029190835_b5631f02378573.png

1486 ms

6516-1-20151029183608_b5631e8886a2e4.gif

6516-1-20151029183608_b5631e8886a2e4.gif

1520 ms

css

css

51 ms

collect

collect

34 ms

ico_arrow.gif

ico_arrow.gif

1070 ms

295-20160218092003.JPG

295-20160218092003.JPG

7113 ms

www.s-n-p.jp

www.s-n-p.jp

1888 ms

288-20160205100903.JPG

288-20160205100903.JPG

1520 ms

287-20160205082659.JPG

287-20160205082659.JPG

8788 ms

265-20151223165544.JPG

265-20151223165544.JPG

6426 ms

img_footer_logo01.png

img_footer_logo01.png

1547 ms

loading.gif

loading.gif

1655 ms

close.gif

close.gif

1821 ms

SEO Factors

enoshima-yacht-harbor.jp SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enoshima-yacht-harbor.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Enoshima-yacht-harbor.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

enoshima-yacht-harbor.jp

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