Tools & Wizards About Us
divingnavi.info screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

divingnavi.info

レックログプロジェクト | レックログプロジェクト

Page Load Speed

6.9 sec in total

First Response

838 ms

Resources Loaded

5.7 sec

Page Rendered

325 ms

divingnavi.info screenshot

About Website

Click here to check amazing Divingnavi content. Otherwise, check out these important facts you probably never knew about divingnavi.info

レックログプロジェクト,ログブック,ダイビング,スタンプ,レカッシュ,ステッカー,シール,東京都中央区日本橋本町4-6-10サトービル５F,

Visit divingnavi.info

Key Findings

We analyzed Divingnavi.info page load time and found that the first response time was 838 ms and then it took 6 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

divingnavi.info performance score

0

Network Requests Diagram

divingnavi.info

838 ms

base.css

315 ms

main.css

323 ms

base_new.css

344 ms

jquery.js

664 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 87% of them (71 requests) were addressed to the original Divingnavi.info, 4% (3 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Divingnavi.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.1 kB (37%)

Content Size

828.6 kB

After Optimization

521.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Divingnavi.info main page is 828.6 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. 50% of websites need less resources to load. Images take 444.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 42.9 kB

  • Original 54.4 kB
  • After minification 53.7 kB
  • After compression 11.5 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 42.9 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 34.2 kB

  • Original 444.7 kB
  • After minification 410.5 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. Divingnavi images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 171.2 kB

  • Original 257.8 kB
  • After minification 232.2 kB
  • After compression 86.6 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 171.2 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 58.9 kB

  • Original 71.7 kB
  • After minification 54.5 kB
  • After compression 12.8 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. Divingnavi.info needs all CSS files to be minified and compressed as it can save up to 58.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (41%)

Requests Now

78

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

divingnavi.info

divingnavi.info

838 ms

base.css

base.css

315 ms

main.css

main.css

323 ms

base_new.css

base_new.css

344 ms

jquery.js

jquery.js

664 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

529 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

466 ms

common.js

common.js

770 ms

utility.css

utility.css

682 ms

skin.css

skin.css

889 ms

bx_styles.css

bx_styles.css

787 ms

jcarousellite.css

jcarousellite.css

860 ms

style.css

style.css

995 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1549 ms

current.js

current.js

1103 ms

jquery.jfeed.pack.js

jquery.jfeed.pack.js

1131 ms

rss_top.js

rss_top.js

1201 ms

rss_top_event.js

rss_top_event.js

1216 ms

smoothScroll.js

smoothScroll.js

1327 ms

opacity-rollover2.1.js

opacity-rollover2.1.js

1443 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

1467 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1515 ms

jcarousellite_1.0.1.js

jcarousellite_1.0.1.js

1576 ms

jquery.mousewheel.js

jquery.mousewheel.js

1647 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

1785 ms

ga.js

ga.js

41 ms

rss.gif

rss.gif

813 ms

b11.ugo2.jp

b11.ugo2.jp

368 ms

getImage.php

getImage.php

527 ms

frek.jpg

frek.jpg

471 ms

bane_197.jpg

bane_197.jpg

318 ms

micro_s.jpg

micro_s.jpg

515 ms

jinbei_log.jpg

jinbei_log.jpg

523 ms

torack.jpg

torack.jpg

347 ms

clocks.jpg

clocks.jpg

823 ms

TREC-013_240.jpg

TREC-013_240.jpg

666 ms

recosh_197.jpg

recosh_197.jpg

977 ms

bookl.jpg

bookl.jpg

1138 ms

ture.jpg

ture.jpg

990 ms

kpy_020.jpg

kpy_020.jpg

847 ms

newpen.jpg

newpen.jpg

1171 ms

toursearch.jpg

toursearch.jpg

1362 ms

btn_01_off.gif

btn_01_off.gif

1177 ms

btn_02_off.gif

btn_02_off.gif

1305 ms

btn_03_off.gif

btn_03_off.gif

1311 ms

getImage.php

getImage.php

1459 ms

getImage.php

getImage.php

1510 ms

getImage.php

getImage.php

1545 ms

getImage.php

getImage.php

1626 ms

getImage.php

getImage.php

1637 ms

login_box.gif

login_box.gif

1690 ms

membe_regist.gif

membe_regist.gif

1790 ms

getLogoImage.php

getLogoImage.php

1870 ms

getImage.php

getImage.php

1935 ms

getImage.php

getImage.php

1992 ms

getImage.php

getImage.php

2188 ms

getImage.php

getImage.php

2244 ms

getImage.php

getImage.php

2259 ms

getImage.php

getImage.php

2299 ms

getImage.php

getImage.php

2510 ms

bt_07_of.gif

bt_07_of.gif

2323 ms

bt_10_of.gif

bt_10_of.gif

2515 ms

bt_08_of.gif

bt_08_of.gif

2599 ms

all.js

all.js

27 ms

bt_09_of.gif

bt_09_of.gif

2566 ms

widgets.js

widgets.js

89 ms

__utm.gif

__utm.gif

24 ms

92 ms

xd_arbiter.php

xd_arbiter.php

43 ms

xd_arbiter.php

xd_arbiter.php

55 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

144 ms

news

news

2339 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

45 ms

event

event

2290 ms

bg_top_red.png

bg_top_red.png

2390 ms

jot

jot

96 ms

arr_right.jpg

arr_right.jpg

2345 ms

bg_top_blue.png

bg_top_blue.png

2388 ms

bg_top_green.png

bg_top_green.png

2415 ms

slide_next.jpg

slide_next.jpg

2287 ms

slide_prev.jpg

slide_prev.jpg

2175 ms

haikei.jpg

haikei.jpg

2356 ms

SEO Factors

divingnavi.info SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Divingnavi.info 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 Divingnavi.info main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

divingnavi.info

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