Tools & Wizards About Us
digion.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

digion.com

株式会社デジオン | DigiOn

Page Load Speed

7.3 sec in total

First Response

485 ms

Resources Loaded

6.6 sec

Page Rendered

212 ms

digion.com screenshot

About Website

Welcome to digion.com homepage info - get ready to check Digi On best content for Japan right away, or after learning these important things about digion.com

株式会社デジオンは、マルチメディアホームネットワーク、セキュリティ、IoTプラットフォームの3つの事業を中心に、「ひとりひとりの未来の暮らしを豊かにする」ことを目指すソフトウェアカンパニーです。

Visit digion.com

Key Findings

We analyzed Digion.com page load time and found that the first response time was 485 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

digion.com performance score

0

Network Requests Diagram

digion.com

485 ms

www.digion.com

926 ms

base.css

608 ms

top.css

409 ms

slideshow.js

415 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 81% of them (61 requests) were addressed to the original Digion.com, 12% (9 requests) were made to Google.com and 4% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Digion.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.4 kB (24%)

Content Size

1.1 MB

After Optimization

819.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digion.com main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 777.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 20.0 kB

  • Original 26.1 kB
  • After minification 21.8 kB
  • After compression 6.0 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 4.2 kB, which is 16% 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 20.0 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 81.3 kB

  • Original 777.9 kB
  • After minification 696.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. Digi On images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 118.2 kB

  • Original 228.5 kB
  • After minification 216.0 kB
  • After compression 110.3 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 118.2 kB or 52% of the original size.

CSS Optimization

-85%

Potential reduce by 35.9 kB

  • Original 42.3 kB
  • After minification 34.6 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. Digion.com needs all CSS files to be minified and compressed as it can save up to 35.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (35%)

Requests Now

69

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digion.com

digion.com

485 ms

www.digion.com

www.digion.com

926 ms

base.css

base.css

608 ms

top.css

top.css

409 ms

slideshow.js

slideshow.js

415 ms

jquery-1.4.min.js

jquery-1.4.min.js

1027 ms

jquery.ticker.js

jquery.ticker.js

621 ms

site.js

site.js

604 ms

smooth.pack.js

smooth.pack.js

816 ms

jquery.scrollable.js

jquery.scrollable.js

827 ms

scrollable.js

scrollable.js

1008 ms

jquery.mousewheel.js

jquery.mousewheel.js

1022 ms

rollover2.js

rollover2.js

1040 ms

scrolltopcontrol.js

scrolltopcontrol.js

1225 ms

bg.png

bg.png

836 ms

analytics.js

analytics.js

94 ms

logo.png

logo.png

206 ms

bt_soft24_rollout.png

bt_soft24_rollout.png

413 ms

bt_soft25_rollout.png

bt_soft25_rollout.png

412 ms

bt_soft22_rollout.png

bt_soft22_rollout.png

415 ms

bt_soft23_rollout.png

bt_soft23_rollout.png

418 ms

bt_soft19_rollout.png

bt_soft19_rollout.png

614 ms

bt_soft1_rollout.png

bt_soft1_rollout.png

826 ms

bt_soft18_rollout.png

bt_soft18_rollout.png

816 ms

bt_soft3_rollout.png

bt_soft3_rollout.png

1027 ms

ba_adpt_rollout.png

ba_adpt_rollout.png

1029 ms

ba_recruit_rollout.png

ba_recruit_rollout.png

828 ms

ba_blog_rollout.png

ba_blog_rollout.png

1029 ms

ba_3_rollout.png

ba_3_rollout.png

1224 ms

cse.js

cse.js

91 ms

navi.png

navi.png

1631 ms

bg_images.png

bg_images.png

1224 ms

img23.jpg

img23.jpg

2155 ms

img24.jpg

img24.jpg

1953 ms

img20.jpg

img20.jpg

2176 ms

img1.jpg

img1.jpg

1744 ms

bg_images_under.png

bg_images_under.png

1549 ms

bt_corp.png

bt_corp.png

2163 ms

bt_cons.png

bt_cons.png

2169 ms

bt_twitter.png

bt_twitter.png

2151 ms

news_bar.png

news_bar.png

2363 ms

news_ti.png

news_ti.png

2561 ms

news_bt.png

news_bt.png

2566 ms

scroll_bt_l.png

scroll_bt_l.png

2570 ms

scroll_bt_r.png

scroll_bt_r.png

2575 ms

bg_ft.png

bg_ft.png

2789 ms

ti_pro_ser.png

ti_pro_ser.png

2769 ms

bg_line.png

bg_line.png

2966 ms

controls.png

controls.png

2971 ms

bt_up.png

bt_up.png

2976 ms

scroll_point.png

scroll_point.png

2988 ms

cse.js

cse.js

89 ms

collect

collect

24 ms

jsapi

jsapi

44 ms

default+ja.css

default+ja.css

5 ms

default.css

default.css

38 ms

default+ja.I.js

default+ja.I.js

17 ms

default.css

default.css

33 ms

async-ads.js

async-ads.js

70 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

29 ms

small-logo.png

small-logo.png

15 ms

search_box_icon.png

search_box_icon.png

16 ms

clear.gif

clear.gif

17 ms

bt_soft24_rollover.png

bt_soft24_rollover.png

208 ms

bt_soft25_rollover.png

bt_soft25_rollover.png

408 ms

bt_soft22_rollover.png

bt_soft22_rollover.png

413 ms

bt_soft23_rollover.png

bt_soft23_rollover.png

413 ms

bt_soft19_rollover.png

bt_soft19_rollover.png

414 ms

bt_soft1_rollover.png

bt_soft1_rollover.png

616 ms

bt_soft18_rollover.png

bt_soft18_rollover.png

621 ms

bt_soft3_rollover.png

bt_soft3_rollover.png

1018 ms

ba_adpt_rollover.png

ba_adpt_rollover.png

818 ms

ba_recruit_rollover.png

ba_recruit_rollover.png

820 ms

ba_blog_rollover.png

ba_blog_rollover.png

826 ms

ba_3_rollover.png

ba_3_rollover.png

1024 ms

SEO Factors

digion.com 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 Digion.com 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 Digion.com 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

digion.com

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