Tools & Wizards About Us
dowsing.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

dowsing.jp

日本ダウジング協会 - ダウジング.jp

Page Load Speed

5.1 sec in total

First Response

686 ms

Resources Loaded

4 sec

Page Rendered

418 ms

dowsing.jp screenshot

About Website

Click here to check amazing Dowsing content for Japan. Otherwise, check out these important facts you probably never knew about dowsing.jp

世界最先端のダウジング技術を学ぶことができる、各専門分野を持つ優れたダウザーたちが集まる日本ダウジング協会

Visit dowsing.jp

Key Findings

We analyzed Dowsing.jp page load time and found that the first response time was 686 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

dowsing.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value15.0 s

8/100

10%

Network Requests Diagram

dowsing.jp

686 ms

main.css

230 ms

acctag.js

644 ms

logo.jpg

491 ms

00-menu07.jpg

487 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Dowsing.jp, 28% (24 requests) were made to Static.xx.fbcdn.net and 15% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Dowsing.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.0 kB (9%)

Content Size

505.6 kB

After Optimization

461.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dowsing.jp main page is 505.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. 40% of websites need less resources to load. Images take 446.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.4 kB

  • Original 34.2 kB
  • After minification 30.3 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 3.8 kB, which is 11% 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 26.4 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 10.5 kB

  • Original 446.1 kB
  • After minification 435.6 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. Dowsing images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-86%

Potential reduce by 7.1 kB

  • Original 8.2 kB
  • After minification 6.4 kB
  • After compression 1.1 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. Dowsing.jp needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dowsing.jp

dowsing.jp

686 ms

main.css

main.css

230 ms

acctag.js

acctag.js

644 ms

logo.jpg

logo.jpg

491 ms

00-menu07.jpg

00-menu07.jpg

487 ms

00-menu08.jpg

00-menu08.jpg

488 ms

space.gif

space.gif

488 ms

00-menu00.jpg

00-menu00.jpg

501 ms

00-menu01.jpg

00-menu01.jpg

704 ms

00-menu02.jpg

00-menu02.jpg

690 ms

00-menu03.jpg

00-menu03.jpg

691 ms

00-menu04.jpg

00-menu04.jpg

692 ms

00-menu05.jpg

00-menu05.jpg

694 ms

00-menu06.jpg

00-menu06.jpg

729 ms

0txt2.gif

0txt2.gif

827 ms

new.gif

new.gif

866 ms

0txt1.gif

0txt1.gif

886 ms

0txt3.gif

0txt3.gif

902 ms

0txt4.gif

0txt4.gif

922 ms

top201504a.jpg

top201504a.jpg

2028 ms

0txt7.gif

0txt7.gif

1073 ms

20151204.jpg

20151204.jpg

2027 ms

to-top.gif

to-top.gif

1114 ms

201404level2b.jpg

201404level2b.jpg

1772 ms

201404level1b.jpg

201404level1b.jpg

2098 ms

bg3s.jpg

bg3s.jpg

1455 ms

bg1s.jpg

bg1s.jpg

2029 ms

bg2s.jpg

bg2s.jpg

2023 ms

space.gif

space.gif

2098 ms

sdk.js

sdk.js

409 ms

line2013.gif

line2013.gif

2086 ms

top-navi2.gif

top-navi2.gif

2098 ms

point.gif

point.gif

2108 ms

test1.gif

test1.gif

2128 ms

top-navi.gif

top-navi.gif

2301 ms

head7px.gif

head7px.gif

2312 ms

widgets.js

widgets.js

257 ms

point_cate.gif

point_cate.gif

2186 ms

ga.js

ga.js

448 ms

like.php

like.php

349 ms

202 ms

xd_arbiter.php

xd_arbiter.php

282 ms

xd_arbiter.php

xd_arbiter.php

567 ms

Of-YZRAFweH.js

Of-YZRAFweH.js

819 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

644 ms

button.65b4bc8f0d6592fdc51d322b3f197660.js

button.65b4bc8f0d6592fdc51d322b3f197660.js

285 ms

__utm.gif

__utm.gif

68 ms

page.php

page.php

272 ms

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

107 ms

N5keFt2bFAu.css

N5keFt2bFAu.css

372 ms

NRhzQHyZYbs.css

NRhzQHyZYbs.css

460 ms

MKiDk2JIhZf.css

MKiDk2JIhZf.css

521 ms

XCdv7aD40Gm.js

XCdv7aD40Gm.js

653 ms

IGjVwCaq5H5.js

IGjVwCaq5H5.js

765 ms

nw0sMxy_KfY.js

nw0sMxy_KfY.js

647 ms

hNf_FhaQk_d.js

hNf_FhaQk_d.js

585 ms

In4aku49oAV.js

In4aku49oAV.js

813 ms

jot

jot

269 ms

1381815_431415906964025_1054966021_n.jpg

1381815_431415906964025_1054966021_n.jpg

326 ms

safe_image.php

safe_image.php

401 ms

69164_302353833203567_120444100_n.jpg

69164_302353833203567_120444100_n.jpg

360 ms

10352891_873905506089079_4603810930620030973_n.jpg

10352891_873905506089079_4603810930620030973_n.jpg

412 ms

11138136_665890100183229_5920868156887092245_n.jpg

11138136_665890100183229_5920868156887092245_n.jpg

460 ms

10653563_662851587161264_6949940610248231905_n.jpg

10653563_662851587161264_6949940610248231905_n.jpg

498 ms

12832323_996251217120455_1576238452066170342_n.jpg

12832323_996251217120455_1576238452066170342_n.jpg

466 ms

12509865_1679512348999512_6898047009589579213_n.jpg

12509865_1679512348999512_6898047009589579213_n.jpg

459 ms

12920487_847601465345465_3625878538798960082_n.jpg

12920487_847601465345465_3625878538798960082_n.jpg

530 ms

12931113_847538448685100_2555120738491033838_n.jpg

12931113_847538448685100_2555120738491033838_n.jpg

749 ms

12931196_847538508685094_4254863187468387820_n.jpg

12931196_847538508685094_4254863187468387820_n.jpg

508 ms

12439166_847538515351760_2158172614975751528_n.jpg

12439166_847538515351760_2158172614975751528_n.jpg

526 ms

12814792_839626322809646_628457706548975144_n.jpg

12814792_839626322809646_628457706548975144_n.jpg

512 ms

10264639_838148172957461_5682771209741561956_n.jpg

10264639_838148172957461_5682771209741561956_n.jpg

553 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

179 ms

WTZ_Jhk-ooC.png

WTZ_Jhk-ooC.png

178 ms

mbF8ssTVP_5.png

mbF8ssTVP_5.png

179 ms

Fe6g47SXw-8.png

Fe6g47SXw-8.png

178 ms

L5AOQ9vzKfo.png

L5AOQ9vzKfo.png

249 ms

oULnqcel5Nm.png

oULnqcel5Nm.png

249 ms

q2ibvFgTxmh.png

q2ibvFgTxmh.png

247 ms

A2JLtDOGyCJ.png

A2JLtDOGyCJ.png

247 ms

YdFQSHGYJ82.png

YdFQSHGYJ82.png

328 ms

Qo6jLTrNZQ5.js

Qo6jLTrNZQ5.js

98 ms

R9GKCzjAnbk.js

R9GKCzjAnbk.js

79 ms

AWWjhOengNF.js

AWWjhOengNF.js

80 ms

YnSasnyq68i.js

YnSasnyq68i.js

81 ms

kQf_jlUv-kX.js

kQf_jlUv-kX.js

88 ms

Accessibility Review

dowsing.jp accessibility score

68

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

dowsing.jp best practices score

58

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dowsing.jp SEO score

87

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dowsing.jp 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 Dowsing.jp 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

dowsing.jp

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