Tools & Wizards About Us
onsemi.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onsemi.jp

インテリジェントな電力およびセンシングのテクノロジ | オンセミ

Page Load Speed

2.9 sec in total

First Response

307 ms

Resources Loaded

2.5 sec

Page Rendered

114 ms

onsemi.jp screenshot

About Website

Welcome to onsemi.jp homepage info - get ready to check Onsemi best content for India right away, or after learning these important things about onsemi.jp

The leader in intelligent power and image sensing technologies that build a better future for the automotive, industrial, cloud, medical, and IoT markets

Visit onsemi.jp

Key Findings

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

Performance Metrics

onsemi.jp performance score

0

Network Requests Diagram

onsemi.jp

307 ms

www.onsemi.jp

288 ms

style.ncv20150630.css

123 ms

styleHome.css

115 ms

newProducts.css

122 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 92% of them (108 requests) were addressed to the original Onsemi.jp, 3% (4 requests) were made to Onsemi.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (826 ms) belongs to the original domain Onsemi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (20%)

Content Size

5.0 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onsemi.jp main page is 5.0 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. 45% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 316.6 kB

  • Original 354.8 kB
  • After minification 303.4 kB
  • After compression 38.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 51.4 kB, 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 316.6 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 170.7 kB

  • Original 3.9 MB
  • After minification 3.7 MB

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. Onsemi images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 421.2 kB

  • Original 611.0 kB
  • After minification 573.1 kB
  • After compression 189.8 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 421.2 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 94.6 kB

  • Original 112.7 kB
  • After minification 84.0 kB
  • After compression 18.1 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. Onsemi.jp needs all CSS files to be minified and compressed as it can save up to 94.6 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

115

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onsemi.jp

onsemi.jp

307 ms

www.onsemi.jp

www.onsemi.jp

288 ms

style.ncv20150630.css

style.ncv20150630.css

123 ms

styleHome.css

styleHome.css

115 ms

newProducts.css

newProducts.css

122 ms

homePageProductsFloatingMenu.css

homePageProductsFloatingMenu.css

122 ms

jquery.ui.theme.css

jquery.ui.theme.css

119 ms

jquery-ui-1.8.17.custom.css

jquery-ui-1.8.17.custom.css

137 ms

login.css

login.css

167 ms

headerProductsFloatingMenu.css

headerProductsFloatingMenu.css

172 ms

preload.js

preload.js

173 ms

scripts.js

scripts.js

178 ms

scriptHome.js

scriptHome.js

169 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

252 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

351 ms

homePageProductsFloatingMenu.js

homePageProductsFloatingMenu.js

226 ms

jquery.autocomplete.js

jquery.autocomplete.js

226 ms

login.js

login.js

223 ms

hoverIntent.js

hoverIntent.js

226 ms

headerProductsFloatingMenu.js

headerProductsFloatingMenu.js

277 ms

cookieconsent.min.js

cookieconsent.min.js

281 ms

edge.6.0.0.min.js

edge.6.0.0.min.js

355 ms

jquery.mcdropdown.js

jquery.mcdropdown.js

237 ms

jquery.mcdropdown.css

jquery.mcdropdown.css

256 ms

conversion.js

conversion.js

16 ms

chapter_open.gif

chapter_open.gif

159 ms

chapter.gif

chapter.gif

163 ms

minus.gif

minus.gif

166 ms

plus.gif

plus.gif

223 ms

BGs.png

BGs.png

223 ms

chapter_open.gif

chapter_open.gif

170 ms

chapter.gif

chapter.gif

164 ms

minus.gif

minus.gif

166 ms

plus.gif

plus.gif

166 ms

analytics.js

analytics.js

31 ms

ON-Semiconductor-JP.jpg

ON-Semiconductor-JP.jpg

108 ms

energy-efficient-innovations-JP.jpg

energy-efficient-innovations-JP.jpg

114 ms

tabs.png

tabs.png

64 ms

ui-icons_ffffff_256x240.png

ui-icons_ffffff_256x240.png

64 ms

btn_icon_login.gif

btn_icon_login.gif

70 ms

btn_icon_register.gif

btn_icon_register.gif

70 ms

ajax-loader.gif

ajax-loader.gif

111 ms

feedback.png

feedback.png

116 ms

rating.png

rating.png

119 ms

product-box-center.jpg

product-box-center.jpg

125 ms

ajax-loader2.gif

ajax-loader2.gif

162 ms

App-Auto.jpg

App-Auto.jpg

164 ms

App-Circuit.jpg

App-Circuit.jpg

168 ms

App-Computing.jpg

App-Computing.jpg

171 ms

App-Consumer.jpg

App-Consumer.jpg

173 ms

App-LED.jpg

App-LED.jpg

179 ms

App-Medical.jpg

App-Medical.jpg

215 ms

App-Industrial.jpg

App-Industrial.jpg

217 ms

App-Aero.jpg

App-Aero.jpg

222 ms

App-Motor.jpg

App-Motor.jpg

226 ms

App-Comm.jpg

App-Comm.jpg

227 ms

App-Wireless.jpg

App-Wireless.jpg

233 ms

App-Power.jpg

App-Power.jpg

268 ms

vertical_line.jpg

vertical_line.jpg

270 ms

btn_icon_simulate.jpg

btn_icon_simulate.jpg

275 ms

btn_icon_analyze.jpg

btn_icon_analyze.jpg

280 ms

Product-Recommendation-Tool-graphic-Green.jpg

Product-Recommendation-Tool-graphic-Green.jpg

281 ms

IBD-Graphic-Green.jpg

IBD-Graphic-Green.jpg

287 ms

linkedin-icon.gif

linkedin-icon.gif

322 ms

YouTube-footer.jpg

YouTube-footer.jpg

324 ms

twitter-icon.gif

twitter-icon.gif

328 ms

google-icon.gif

google-icon.gif

321 ms

linkid.js

linkid.js

11 ms

homePageBannerJP_edge.js

homePageBannerJP_edge.js

293 ms

gray-bar-shadow.jpg

gray-bar-shadow.jpg

298 ms

green-tab-shadow-left.jpg

green-tab-shadow-left.jpg

333 ms

green-tab-shadow-mid.jpg

green-tab-shadow-mid.jpg

332 ms

collect

collect

30 ms

green-tab-shadow-right.jpg

green-tab-shadow-right.jpg

322 ms

footer-background.jpg

footer-background.jpg

397 ms

47 ms

preloader5.gif

preloader5.gif

306 ms

42 ms

homePageBannerJP_edge.js

homePageBannerJP_edge.js

57 ms

hppc_v1.png

hppc_v1.png

330 ms

hppc_bg.jpg

hppc_bg.jpg

225 ms

hppc_block.jpg

hppc_block.jpg

176 ms

hppc_motor.png

hppc_motor.png

532 ms

hppc_txt.png

hppc_txt.png

62 ms

hppc_CTA.png

hppc_CTA.png

124 ms

arrowLeft.svg

arrowLeft.svg

122 ms

iiot_robots.jpg

iiot_robots.jpg

533 ms

iiot_block.jpg

iiot_block.jpg

233 ms

iiot_SurveillanceCamera.png

iiot_SurveillanceCamera.png

342 ms

iiot_securitycamera_1.png

iiot_securitycamera_1.png

331 ms

iiot_wireless_camera_text.png

iiot_wireless_camera_text.png

292 ms

iiot_CTA.png

iiot_CTA.png

348 ms

wireless_bg.jpg

wireless_bg.jpg

447 ms

smartphone_block.jpg

smartphone_block.jpg

462 ms

wireless_smartphone_txt.png

wireless_smartphone_txt.png

420 ms

dashedline2.svg

dashedline2.svg

416 ms

wireless_camera_image.png

wireless_camera_image.png

592 ms

wireless_camera.png

wireless_camera.png

474 ms

wireless_smartphone_v1.png

wireless_smartphone_v1.png

621 ms

wireless_CTA.png

wireless_CTA.png

524 ms

automotive_road_v1.png

automotive_road_v1.png

675 ms

automotive_block.png

automotive_block.png

589 ms

dashedline.svg

dashedline.svg

594 ms

automotive_cameraview_v1.png

automotive_cameraview_v1.png

684 ms

automotive_camera_v1.png

automotive_camera_v1.png

648 ms

automotive_adas_v1.png

automotive_adas_v1.png

650 ms

automotive_v1.png

automotive_v1.png

826 ms

automotive_CTA.png

automotive_CTA.png

675 ms

hppc_off.svg

hppc_off.svg

710 ms

IIoT_off.svg

IIoT_off.svg

707 ms

wireless_off.svg

wireless_off.svg

728 ms

automotive_off.svg

automotive_off.svg

731 ms

hppc_on.svg

hppc_on.svg

737 ms

iiot_on.svg

iiot_on.svg

760 ms

wireless_on.svg

wireless_on.svg

755 ms

automotive_on.svg

automotive_on.svg

730 ms

cookieconsent-dark-top.css

cookieconsent-dark-top.css

222 ms

mcdd_select_button_sprite.gif

mcdd_select_button_sprite.gif

60 ms

SEO Factors

onsemi.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 Onsemi.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 Onsemi.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

onsemi.jp

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