Tools & Wizards About Us
implantnavi.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

implantnavi.net

Top - 歯医者の窓口

Page Load Speed

4.1 sec in total

First Response

595 ms

Resources Loaded

3.3 sec

Page Rendered

177 ms

implantnavi.net screenshot

About Website

Click here to check amazing Implantnavi content for Japan. Otherwise, check out these important facts you probably never knew about implantnavi.net

インプラントや矯正・審美治療に最適な信頼できる歯医者を検索できる、自費診療特化の歯科予約サイトです。

Visit implantnavi.net

Key Findings

We analyzed Implantnavi.net page load time and found that the first response time was 595 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

implantnavi.net performance score

0

Network Requests Diagram

implantnavi.net

595 ms

www.implantnavi.net

907 ms

default.css

748 ms

home.css

388 ms

jquery.min.js

8 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 89% of them (32 requests) were addressed to the original Implantnavi.net, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Implantnavi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.2 kB (30%)

Content Size

219.0 kB

After Optimization

153.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Implantnavi.net main page is 219.0 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. 25% of websites need less resources to load. Images take 119.1 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 12.1 kB

  • Original 17.7 kB
  • After minification 17.3 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. 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 12.1 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-32%

Potential reduce by 9.4 kB

  • Original 28.9 kB
  • After minification 26.6 kB
  • After compression 19.5 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 9.4 kB or 32% of the original size.

CSS Optimization

-82%

Potential reduce by 43.8 kB

  • Original 53.2 kB
  • After minification 43.1 kB
  • After compression 9.5 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. Implantnavi.net needs all CSS files to be minified and compressed as it can save up to 43.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

34

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

implantnavi.net

implantnavi.net

595 ms

www.implantnavi.net

www.implantnavi.net

907 ms

default.css

default.css

748 ms

home.css

home.css

388 ms

jquery.min.js

jquery.min.js

8 ms

rpslider.js

rpslider.js

404 ms

jquery.rwdImageMaps.min.js

jquery.rwdImageMaps.min.js

216 ms

logo.gif

logo.gif

204 ms

japanmap.jpg

japanmap.jpg

192 ms

zyoken.jpg

zyoken.jpg

975 ms

searchclick.gif

searchclick.gif

198 ms

picup_ad_dentist.jpg

picup_ad_dentist.jpg

390 ms

picup_periodontal-disease.jpg

picup_periodontal-disease.jpg

398 ms

picup_faq.jpg

picup_faq.jpg

383 ms

picup_medicaldeduction.jpg

picup_medicaldeduction.jpg

388 ms

picup_ninki.jpg

picup_ninki.jpg

403 ms

special_1001740.jpg

special_1001740.jpg

566 ms

picup_ranking.jpg

picup_ranking.jpg

573 ms

picup_cost.jpg

picup_cost.jpg

587 ms

picup_case.jpg

picup_case.jpg

595 ms

picup_whatis.jpg

picup_whatis.jpg

600 ms

1000006_212_75.gif

1000006_212_75.gif

758 ms

1000612_212_75.jpg

1000612_212_75.jpg

949 ms

1001740_185_263.gif

1001740_185_263.gif

1174 ms

btn_entrytext.gif

btn_entrytext.gif

793 ms

btn_kutikomi_senddefa.gif

btn_kutikomi_senddefa.gif

795 ms

btn_info.gif

btn_info.gif

959 ms

btn_footer_general.gif

btn_footer_general.gif

1003 ms

gtm.js

gtm.js

93 ms

bg-sub-ht.gif

bg-sub-ht.gif

989 ms

anchor_orange.gif

anchor_orange.gif

1123 ms

gn_bg.jpg

gn_bg.jpg

1133 ms

gn_btn1.gif

gn_btn1.gif

1156 ms

gn_btn2.gif

gn_btn2.gif

1187 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

14 ms

SEO Factors

implantnavi.net SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Implantnavi.net 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 Implantnavi.net main page’s claimed encoding is euc-jp. 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

implantnavi.net

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