Tools & Wizards About Us
telnavi.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

telnavi.jp

電話番号検索なら「電話帳ナビ」

Page Load Speed

3.8 sec in total

First Response

26 ms

Resources Loaded

3.7 sec

Page Rendered

104 ms

telnavi.jp screenshot

About Website

Welcome to telnavi.jp homepage info - get ready to check Telnavi best content for Japan right away, or after learning these important things about telnavi.jp

電話帳ナビは電話番号から相手先を検索する事ができる電話番号検索サイトです。

Visit telnavi.jp

Key Findings

We analyzed Telnavi.jp page load time and found that the first response time was 26 ms and then it took 3.8 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

telnavi.jp performance score

0

Network Requests Diagram

telnavi.jp

26 ms

www.telnavi.jp

729 ms

bootstrap.min.css

698 ms

open-sans.css

729 ms

email-decode.min.js

20 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that all of those requests were addressed to Telnavi.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (749 ms) belongs to the original domain Telnavi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 kB (22%)

Content Size

14.9 kB

After Optimization

11.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Telnavi.jp main page is 14.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 5.4 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 3.0 kB

  • Original 4.9 kB
  • After minification 4.4 kB
  • After compression 1.9 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 3.0 kB or 62% of the original size.

Image Optimization

-1%

Potential reduce by 30 B

  • Original 4.0 kB
  • After minification 3.9 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. Telnavi images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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

-3%

Potential reduce by 188 B

  • Original 5.4 kB
  • After minification 5.4 kB
  • After compression 5.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. Telnavi.jp has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Telnavi. According to our analytics all requests are already optimized.

Network Requests Diagram

telnavi.jp

telnavi.jp

26 ms

www.telnavi.jp

www.telnavi.jp

729 ms

bootstrap.min.css

bootstrap.min.css

698 ms

open-sans.css

open-sans.css

729 ms

email-decode.min.js

email-decode.min.js

20 ms

apache_pb.gif

apache_pb.gif

698 ms

poweredby.png

poweredby.png

723 ms

OpenSans-Light.woff

OpenSans-Light.woff

702 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

749 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

683 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

696 ms

OpenSans-ExtraBold.woff

OpenSans-ExtraBold.woff

738 ms

OpenSans-Semibold.ttf

OpenSans-Semibold.ttf

689 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

708 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

686 ms

OpenSans-ExtraBold.ttf

OpenSans-ExtraBold.ttf

705 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

724 ms

OpenSans-Semibold.svg

OpenSans-Semibold.svg

703 ms

OpenSans-Light.svg

OpenSans-Light.svg

693 ms

OpenSans-Bold.svg

OpenSans-Bold.svg

681 ms

OpenSans-ExtraBold.svg

OpenSans-ExtraBold.svg

701 ms

OpenSans-Regular.svg

OpenSans-Regular.svg

704 ms

SEO Factors

telnavi.jp 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 Telnavi.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 Telnavi.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

telnavi.jp

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