Tools & Wizards About Us
idec.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

idec.com

IDEC Corporation

Page Load Speed

3.4 sec in total

First Response

868 ms

Resources Loaded

2.4 sec

Page Rendered

74 ms

idec.com screenshot

About Website

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

We create the optimum environment for humans and machines, and achieve safety, ANSHIN, and well-being for people around the world.

Visit idec.com

Key Findings

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

Performance Metrics

idec.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

www.idec.com

868 ms

E930DD5F85B3EBB75.css

286 ms

style.min.css

54 ms

customerticketingaddon.css

124 ms

smarteditaddon.css

40 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 76% of them (70 requests) were addressed to the original Idec.com, 9% (8 requests) were made to and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Idec.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.6 kB (39%)

Content Size

148.5 kB

After Optimization

90.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Idec.com main page is 148.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 82.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 18.9 kB

  • Original 26.3 kB
  • After minification 25.6 kB
  • After compression 7.4 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 18.9 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-47%

Potential reduce by 38.7 kB

  • Original 82.0 kB
  • After minification 81.9 kB
  • After compression 43.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 38.7 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (88%)

Requests Now

81

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.idec.com

www.idec.com

868 ms

E930DD5F85B3EBB75.css

E930DD5F85B3EBB75.css

286 ms

style.min.css

style.min.css

54 ms

customerticketingaddon.css

customerticketingaddon.css

124 ms

smarteditaddon.css

smarteditaddon.css

40 ms

analyticsmediator.js

analyticsmediator.js

166 ms

generatedVariables.js

generatedVariables.js

40 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

119 ms

enquire.min.js

enquire.min.js

119 ms

Imager.min.js

Imager.min.js

148 ms

purify.min.js

purify.min.js

239 ms

jquery.blockUI-2.66.js

jquery.blockUI-2.66.js

120 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

141 ms

jquery.form.min.js

jquery.form.min.js

121 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

147 ms

jquery.pstrength.custom-1.2.0.js

jquery.pstrength.custom-1.2.0.js

218 ms

jquery.syncheight.custom.js

jquery.syncheight.custom.js

390 ms

jquery.tabs.custom.js

jquery.tabs.custom.js

160 ms

jquery-ui-1.12.1.min.js

jquery-ui-1.12.1.min.js

208 ms

jquery.zoom.custom.js

jquery.zoom.custom.js

177 ms

owl.carousel.custom.js

owl.carousel.custom.js

195 ms

jquery.tmpl-1.0.0pre.min.js

jquery.tmpl-1.0.0pre.min.js

419 ms

jquery.currencies.min.js

jquery.currencies.min.js

236 ms

jquery.waitforimages.min.js

jquery.waitforimages.min.js

233 ms

jquery.slideviewer.custom.1.2.js

jquery.slideviewer.custom.1.2.js

254 ms

jquery.validate.js

jquery.validate.js

249 ms

app.min.js

app.min.js

414 ms

node.webpack.497d48d2187a76f9b1da.js

node.webpack.497d48d2187a76f9b1da.js

271 ms

node.vuex.bb24f7652b452466e8dd.js

node.vuex.bb24f7652b452466e8dd.js

260 ms

node.vueperslides.2a9986c9f35369ef06b7.js

node.vueperslides.2a9986c9f35369ef06b7.js

269 ms

node.vuejs-paginate.d5ccc744f2cae02aa161.js

node.vuejs-paginate.d5ccc744f2cae02aa161.js

384 ms

node.vuejs-datepicker.af4bcb676768983c5068.js

node.vuejs-datepicker.af4bcb676768983c5068.js

411 ms

node.vue.5d67a25ce83c41ee461e.js

node.vue.5d67a25ce83c41ee461e.js

413 ms

node.vue-simple-svg.b7b01b9d59f45ac5bc85.js

node.vue-simple-svg.b7b01b9d59f45ac5bc85.js

415 ms

node.vue-good-table.511f0a07c21d4aa46858.js

node.vue-good-table.511f0a07c21d4aa46858.js

412 ms

node.vue-click-outside.d890da62fb9705da24f4.js

node.vue-click-outside.d890da62fb9705da24f4.js

449 ms

node.vue-bulma-accordion.6fb8b50cc05b44e5c4a1.js

node.vue-bulma-accordion.6fb8b50cc05b44e5c4a1.js

448 ms

node.vue-async-computed.cc6cc79c5b888e7b69e3.js

node.vue-async-computed.cc6cc79c5b888e7b69e3.js

421 ms

node.url-search-params-polyfill.72ef04d56fff521a9a36.js

node.url-search-params-polyfill.72ef04d56fff521a9a36.js

419 ms

node.timers-browserify.0c75a8afa68b6c9a2854.js

node.timers-browserify.0c75a8afa68b6c9a2854.js

341 ms

node.setimmediate.27592140ef267a07382b.js

node.setimmediate.27592140ef267a07382b.js

370 ms

node.regenerator-runtime.144f4f9a75c51723e900.js

node.regenerator-runtime.144f4f9a75c51723e900.js

396 ms

node.raf.236f918f7053cd71e638.js

node.raf.236f918f7053cd71e638.js

369 ms

node.querystring-es3.7d3116aa51392e56c1c4.js

node.querystring-es3.7d3116aa51392e56c1c4.js

370 ms

node.qs.beeea8fbb34083899ebe.js

node.qs.beeea8fbb34083899ebe.js

370 ms

node.process.9ef53fda559b4ee191ee.js

node.process.9ef53fda559b4ee191ee.js

347 ms

node.performance-now.fdca7d8a39e5102acf93.js

node.performance-now.fdca7d8a39e5102acf93.js

399 ms

node.lodash.1905c44a7b1b0259d1fa.js

node.lodash.1905c44a7b1b0259d1fa.js

401 ms

node.jspdf.a17f59d063f11d682251.js

node.jspdf.a17f59d063f11d682251.js

384 ms

node.jmespath.95b4d4dfddee7fada5d9.js

node.jmespath.95b4d4dfddee7fada5d9.js

350 ms

node.html2canvas.8d2be83733f88601a4b2.js

node.html2canvas.8d2be83733f88601a4b2.js

334 ms

node.fflate.233fb6e74ee65292a968.js

node.fflate.233fb6e74ee65292a968.js

319 ms

node.dompurify.ff3f17e9471188eef93c.js

node.dompurify.ff3f17e9471188eef93c.js

308 ms

node.dateformat.c0ae0561c4718b891fb9.js

node.dateformat.c0ae0561c4718b891fb9.js

328 ms

node.cssom.c2288f95b5795252778b.js

node.cssom.c2288f95b5795252778b.js

344 ms

node.core-js.d1320d52389a471b9b86.js

node.core-js.d1320d52389a471b9b86.js

350 ms

node.canvg.1b12a47a8fa4954f03c5.js

node.canvg.1b12a47a8fa4954f03c5.js

345 ms

node.babel.3b11c9024f0671b82f5c.js

node.babel.3b11c9024f0671b82f5c.js

387 ms

node.babel-polyfill.842c3beab68062df00a5.js

node.babel-polyfill.842c3beab68062df00a5.js

385 ms

node.axios.661e047aacc1e7d8449a.js

node.axios.661e047aacc1e7d8449a.js

317 ms

main.510b8f642e7fb24db8fd.js

main.510b8f642e7fb24db8fd.js

313 ms

34.e9133cd16ef99dfe4f2a.js

34.e9133cd16ef99dfe4f2a.js

309 ms

gtm.js

gtm.js

292 ms

ga.js

ga.js

217 ms

BJG5Y-GES32-LGF94-6JMEY-HKKVG

BJG5Y-GES32-LGF94-6JMEY-HKKVG

190 ms

customerticketingaddon.js

customerticketingaddon.js

206 ms

webApplicationInjector.js

webApplicationInjector.js

223 ms

smarteditaddon.js

smarteditaddon.js

224 ms

logo.jpg

logo.jpg

446 ms

IDEC-logo-color.jpg

IDEC-logo-color.jpg

492 ms

APEM-logo-tag.jpg

APEM-logo-tag.jpg

490 ms

TOKYO-SENSOR-logo.jpg

TOKYO-SENSOR-logo.jpg

642 ms

welcat-logo-tag.jpg

welcat-logo-tag.jpg

467 ms

9ie2ZRFIjk77IlqzoSJg2yMuBrdr0gac7MKWEfdfPEbJWKSkoFGbmIFw054sZSzqv3jBx0Bm5m9noFJRqATjIHvAcG5J3hGSANt4AqCV27YxqqgzpPsQMLlpcE1FxIh1rdqTmHiV+9QtynIRd6kTRwRK2whF5ZlgqVGfSyop0DAPVQTORJIvcqWJgrkG+1VeU5IIdCUCUd2KPAJNLowhVlL+eLbjYR63TUJTB7xF4fpcxBC7hxZE2FOuCkzlFwWaCpMjVuYRbrUilKISXtFjA79iEFBVdJRI2M2+25Uwmc0F4Ljbll1uTWeP1Jwr9VHFFpDAAAAA==

9ie2ZRFIjk77IlqzoSJg2yMuBrdr0gac7MKWEfdfPEbJWKSkoFGbmIFw054sZSzqv3jBx0Bm5m9noFJRqATjIHvAcG5J3hGSANt4AqCV27YxqqgzpPsQMLlpcE1FxIh1rdqTmHiV+9QtynIRd6kTRwRK2whF5ZlgqVGfSyop0DAPVQTORJIvcqWJgrkG+1VeU5IIdCUCUd2KPAJNLowhVlL+eLbjYR63TUJTB7xF4fpcxBC7hxZE2FOuCkzlFwWaCpMjVuYRbrUilKISXtFjA79iEFBVdJRI2M2+25Uwmc0F4Ljbll1uTWeP1Jwr9VHFFpDAAAAA==

11 ms

LqeIma7YDNcHwRwF4jzvkRRhwigS4cj6JiGmIS10FUWYhT4VPkVixY5IGUQEjerVHslBcpjIhTAYKUD+mSOoUKc5TXAce6ZI7BHYdbHqWiKbdD8ToA

LqeIma7YDNcHwRwF4jzvkRRhwigS4cj6JiGmIS10FUWYhT4VPkVixY5IGUQEjerVHslBcpjIhTAYKUD+mSOoUKc5TXAce6ZI7BHYdbHqWiKbdD8ToA

13 ms

iXRxh1ohpwLzaqinVISRxk0WRRSYWrUVu1YI57VgIx+Tig2jkfUlgwjRTMyFjVeXMKleeorw+JiWa+0X3ni49T1VA8KKohAAAA

iXRxh1ohpwLzaqinVISRxk0WRRSYWrUVu1YI57VgIx+Tig2jkfUlgwjRTMyFjVeXMKleeorw+JiWa+0X3ni49T1VA8KKohAAAA

13 ms

GgDfBJ2EdFJIezPwjOTkX9pZ1DmAIySkkl3YA8Emmun8leGX8JI2h4HLcNIDCOtIvHwyww5zQMxJYBViwCQHX9IyJ9PMieiaLdMTTypDSPnzwHbtFymEeJBkzCVjvn3tFOWPLviNkDFxFg0e7T99lA4++3Z1fAIA

GgDfBJ2EdFJIezPwjOTkX9pZ1DmAIySkkl3YA8Emmun8leGX8JI2h4HLcNIDCOtIvHwyww5zQMxJYBViwCQHX9IyJ9PMieiaLdMTTypDSPnzwHbtFymEeJBkzCVjvn3tFOWPLviNkDFxFg0e7T99lA4++3Z1fAIA

12 ms

OVdA4AAA==

OVdA4AAA==

13 ms

2vCvEEAAA=

2vCvEEAAA=

12 ms

SM6389TmNfb4YpdA4AAAA=

SM6389TmNfb4YpdA4AAAA=

12 ms

SkMeKv2yJw==

SkMeKv2yJw==

12 ms

__utm.gif

__utm.gif

103 ms

config.json

config.json

323 ms

collect

collect

286 ms

js

js

100 ms

analytics.js

analytics.js

77 ms

insight.min.js

insight.min.js

173 ms

munchkin.js

munchkin.js

172 ms

update.min.js

update.min.js

165 ms

ga-audiences

ga-audiences

138 ms

collect

collect

80 ms

munchkin.js

munchkin.js

9 ms

Accessibility Review

idec.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

idec.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

idec.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idec.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Idec.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

idec.com

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