Tools & Wizards About Us
imn.canon.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

imn.canon.jp

キヤノン：iVIS mini X SDKIT スペシャルサイト

Page Load Speed

573 ms in total

First Response

59 ms

Resources Loaded

389 ms

Page Rendered

125 ms

imn.canon.jp screenshot

About Website

Click here to check amazing Imn Canon content for Japan. Otherwise, check out these important facts you probably never knew about imn.canon.jp

キヤノンのiVIS mini Xのスペシャルサイトです。超広角&高音質の新感覚小型ムービーカメラ、iVIS mini Xで撮影した動画、静止画をご覧いただけます。

Visit imn.canon.jp

Key Findings

We analyzed Imn.canon.jp page load time and found that the first response time was 59 ms and then it took 514 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

imn.canon.jp performance score

0

Network Requests Diagram

imn.canon.jp

59 ms

reset.css

38 ms

style.css

27 ms

css

25 ms

jquery-1.10.2.min.js

114 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 68% of them (15 requests) were addressed to the original Imn.canon.jp, 9% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (139 ms) belongs to the original domain Imn.canon.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.8 kB (55%)

Content Size

266.6 kB

After Optimization

120.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imn.canon.jp main page is 266.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. 15% of websites need less resources to load. Javascripts take 254.4 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 4.2 kB

  • Original 6.4 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. This page needs HTML code to be minified as it can gain 891 B, which is 14% 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 4.2 kB or 66% of the original size.

Image Optimization

-19%

Potential reduce by 1.0 kB

  • Original 5.5 kB
  • After minification 4.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. Obviously, Imn Canon needs image optimization as it can save up to 1.0 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 140.4 kB

  • Original 254.4 kB
  • After minification 253.1 kB
  • After compression 114.0 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 140.4 kB or 55% of the original size.

CSS Optimization

-29%

Potential reduce by 83 B

  • Original 286 B
  • After minification 264 B
  • After compression 203 B

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. Imn.canon.jp needs all CSS files to be minified and compressed as it can save up to 83 B or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (65%)

Requests Now

20

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imn.canon.jp

imn.canon.jp

59 ms

reset.css

reset.css

38 ms

style.css

style.css

27 ms

css

css

25 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

114 ms

run.js

run.js

105 ms

jquery.mousewheel.js

jquery.mousewheel.js

56 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

33 ms

jquery.masonry.min.js

jquery.masonry.min.js

91 ms

grid.js

grid.js

89 ms

ajaxzip3-https.js

ajaxzip3-https.js

111 ms

conversion.js

conversion.js

17 ms

jquery.pageslide.min.js

jquery.pageslide.min.js

96 ms

googleanalytics.js

googleanalytics.js

70 ms

pc.css

pc.css

139 ms

sp.css

sp.css

127 ms

74 ms

ga.js

ga.js

40 ms

logo_ivismini.png

logo_ivismini.png

31 ms

pic_scrolltop.png

pic_scrolltop.png

50 ms

__utm.gif

__utm.gif

15 ms

33 ms

SEO Factors

imn.canon.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

imn.canon.jp

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