Tools & Wizards About Us
all-navi.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

all-navi.jp

Page Load Speed

2.4 sec in total

First Response

313 ms

Resources Loaded

1.9 sec

Page Rendered

166 ms

all-navi.jp screenshot

About Website

Visit all-navi.jp now to see the best up-to-date All Navi content and also check out these interesting facts you probably never knew about all-navi.jp

賢い比較で価値ある選択　オールナビは、様々なジャンルの比較サイトを提供しています。オールナビの事業内容、運営サイト情報、広告掲載についてなど。

Visit all-navi.jp

Key Findings

We analyzed All-navi.jp page load time and found that the first response time was 313 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

all-navi.jp performance score

0

Network Requests Diagram

all-navi.jp

313 ms

www.all-navi.jp

349 ms

import.css

161 ms

common.js

295 ms

import2.css

160 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 30.9 kB (43%)

Content Size

71.7 kB

After Optimization

40.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of All-navi.jp main page is 71.7 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. Only 10% of websites need less resources to load. CSS take 32.8 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.8 kB

  • Original 6.0 kB
  • After minification 5.5 kB
  • After compression 2.2 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.8 kB or 63% of the original size.

Image Optimization

-0%

Potential reduce by 27 B

  • Original 31.8 kB
  • After minification 31.8 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. All Navi images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 655 B

  • Original 1.1 kB
  • After minification 1.0 kB
  • After compression 490 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 655 B or 57% of the original size.

CSS Optimization

-81%

Potential reduce by 26.4 kB

  • Original 32.8 kB
  • After minification 26.0 kB
  • After compression 6.4 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. All-navi.jp needs all CSS files to be minified and compressed as it can save up to 26.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (64%)

Requests Now

25

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

all-navi.jp

all-navi.jp

313 ms

www.all-navi.jp

www.all-navi.jp

349 ms

import.css

import.css

161 ms

common.js

common.js

295 ms

import2.css

import2.css

160 ms

base.css

base.css

163 ms

element.css

element.css

152 ms

okwave.css

okwave.css

296 ms

style.css

style.css

298 ms

footer_link.css

footer_link.css

315 ms

body_bg.jpg

body_bg.jpg

160 ms

wrapper_bg.gif

wrapper_bg.gif

151 ms

header_bg.gif

header_bg.gif

160 ms

logo.gif

logo.gif

152 ms

header_onepoint.gif

header_onepoint.gif

162 ms

visual_index.jpg

visual_index.jpg

439 ms

topicpath_bottom.gif

topicpath_bottom.gif

296 ms

topicpath_middle.gif

topicpath_middle.gif

298 ms

ico_topicpath.gif

ico_topicpath.gif

315 ms

top-box.gif

top-box.gif

317 ms

ico_a.gif

ico_a.gif

318 ms

p_mark.gif

p_mark.gif

442 ms

ico_pagetop.gif

ico_pagetop.gif

446 ms

topicpath_top.gif

topicpath_top.gif

472 ms

logoan.gif

logoan.gif

473 ms

logoec.gif

logoec.gif

476 ms

print.css

print.css

160 ms

SEO Factors

all-navi.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise All-navi.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that All-navi.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

all-navi.jp

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