Tools & Wizards About Us
silex.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

silex.jp

サイレックス・テクノロジー株式会社｜silex technology

Page Load Speed

7 sec in total

First Response

1 sec

Resources Loaded

5.7 sec

Page Rendered

182 ms

silex.jp screenshot

About Website

Click here to check amazing Silex content for Japan. Otherwise, check out these important facts you probably never knew about silex.jp

サイレックス・テクノロジーは、培ったハードウェア・ソフトウェア組込みノウハウを活かして、実証された確実な接続性をもつワイヤレスとコネクティビティ技術を、産業・医療・商業分野のお客様の機器やシステムに提供し、新しいユーザ価値を創造します。

Visit silex.jp

Key Findings

We analyzed Silex.jp page load time and found that the first response time was 1 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

silex.jp performance score

0

Network Requests Diagram

silex.jp

1047 ms

import.css

479 ms

indexnew.css

500 ms

rollover_indexnew.js

531 ms

jquery-1.9.1.min.js

1047 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 94% of them (112 requests) were addressed to the original Silex.jp, 3% (4 requests) were made to Google-analytics.com and 2% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Silex.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 244.8 kB (18%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Silex.jp main page is 1.3 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 39.9 kB

  • Original 48.3 kB
  • After minification 40.1 kB
  • After compression 8.5 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 8.2 kB, which is 17% 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 39.9 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 33.0 kB

  • Original 1.0 MB
  • After minification 988.7 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. Silex images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 100.5 kB

  • Original 180.1 kB
  • After minification 160.8 kB
  • After compression 79.6 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 100.5 kB or 56% of the original size.

CSS Optimization

-86%

Potential reduce by 71.5 kB

  • Original 82.8 kB
  • After minification 60.1 kB
  • After compression 11.3 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. Silex.jp needs all CSS files to be minified and compressed as it can save up to 71.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (25%)

Requests Now

118

After Optimization

88

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

silex.jp

silex.jp

1047 ms

import.css

import.css

479 ms

indexnew.css

indexnew.css

500 ms

rollover_indexnew.js

rollover_indexnew.js

531 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1047 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

547 ms

wideslider.js

wideslider.js

550 ms

jquery.Pc2Sp.js

jquery.Pc2Sp.js

625 ms

silex.js

silex.js

657 ms

bsn.AutoSuggest_c_2.0.js

bsn.AutoSuggest_c_2.0.js

875 ms

autosuggest_inquisitor.css

autosuggest_inquisitor.css

729 ms

logger_onload.js

logger_onload.js

421 ms

default.css

default.css

295 ms

layout.css

layout.css

339 ms

content.css

content.css

799 ms

ga.js

ga.js

44 ms

analytics.js

analytics.js

44 ms

bg.gif

bg.gif

174 ms

logo.gif

logo.gif

185 ms

gmenu_products-off.gif

gmenu_products-off.gif

176 ms

bn_app-education.jpg

bn_app-education.jpg

348 ms

btn_win10_support.gif

btn_win10_support.gif

149 ms

gmenu_solution-off.gif

gmenu_solution-off.gif

187 ms

gmenu_support-off.gif

gmenu_support-off.gif

297 ms

btn_login.jpg

btn_login.jpg

320 ms

bn_sxuvlcsdk.gif

bn_sxuvlcsdk.gif

349 ms

gmenu_company-off.gif

gmenu_company-off.gif

370 ms

bn_message.jpg

bn_message.jpg

371 ms

bn_amc.jpg

bn_amc.jpg

442 ms

bnr_recruit2017.gif

bnr_recruit2017.gif

478 ms

ico_navi.jpg

ico_navi.jpg

522 ms

gmenu_contact-off.gif

gmenu_contact-off.gif

522 ms

DeviceConnectivity.jpg

DeviceConnectivity.jpg

1104 ms

DisplayConnectivity.jpg

DisplayConnectivity.jpg

1096 ms

WirelessInfra.jpg

WirelessInfra.jpg

1466 ms

EmbeddedWireless.jpg

EmbeddedWireless.jpg

1426 ms

AMC.jpg

AMC.jpg

1556 ms

ttl_news.gif

ttl_news.gif

694 ms

btn_backnumber.gif

btn_backnumber.gif

869 ms

btn_rss.gif

btn_rss.gif

1042 ms

ico_news_blog.gif

ico_news_blog.gif

1215 ms

bg_news.gif

bg_news.gif

1278 ms

ico_news_support.gif

ico_news_support.gif

1287 ms

ico_news_product.gif

ico_news_product.gif

1389 ms

bn_ew_technical.jpg

bn_ew_technical.jpg

1460 ms

btn_contact.gif

btn_contact.gif

1470 ms

btn_mypage.gif

btn_mypage.gif

1562 ms

btn_aboutmypage.gif

btn_aboutmypage.gif

1582 ms

bnr_recruit2017.gif

bnr_recruit2017.gif

1642 ms

sxds3000wan_pt.jpg

sxds3000wan_pt.jpg

1611 ms

sxds3000wan_txt.gif

sxds3000wan_txt.gif

1652 ms

br300an_pt.jpg

br300an_pt.jpg

1727 ms

BeaconReceiver.jsp

BeaconReceiver.jsp

832 ms

br300an_txt.gif

br300an_txt.gif

1715 ms

plusone.js

plusone.js

94 ms

__utm.gif

__utm.gif

27 ms

collect

collect

16 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

24 ms

mvds_x5_pt.jpg

mvds_x5_pt.jpg

1598 ms

mvds_x5_txt.gif

mvds_x5_txt.gif

1593 ms

bg_footer_part.gif

bg_footer_part.gif

1654 ms

footer_products.gif

footer_products.gif

1659 ms

footer_dc.gif

footer_dc.gif

1722 ms

footer_ds.gif

footer_ds.gif

1616 ms

footer_ps.gif

footer_ps.gif

1584 ms

footer_lb.gif

footer_lb.gif

1564 ms

footer_sw.gif

footer_sw.gif

1663 ms

footer_dpc.gif

footer_dpc.gif

1658 ms

footer_mds.gif

footer_mds.gif

1692 ms

footer_wdsp.gif

footer_wdsp.gif

1639 ms

footer_nda.gif

footer_nda.gif

1580 ms

footer_wi.gif

footer_wi.gif

1563 ms

footer_ap.gif

footer_ap.gif

1671 ms

footer_wb.gif

footer_wb.gif

1516 ms

footer_survey.gif

footer_survey.gif

1336 ms

footer_ew.gif

footer_ew.gif

1177 ms

footer_wrm.gif

footer_wrm.gif

1157 ms

footer_im.gif

footer_im.gif

1156 ms

footer_kkhk.gif

footer_kkhk.gif

1160 ms

footer_others.gif

footer_others.gif

1073 ms

footer_hnns.gif

footer_hnns.gif

1107 ms

footer_snt.gif

footer_snt.gif

988 ms

footer_support.gif

footer_support.gif

1001 ms

footer_download.gif

footer_download.gif

970 ms

footer_model.gif

footer_model.gif

1035 ms

footer_faq.gif

footer_faq.gif

1087 ms

footer_company.gif

footer_company.gif

981 ms

footer_about.gif

footer_about.gif

1016 ms

footer_recruit.gif

footer_recruit.gif

1015 ms

footer_mypage.gif

footer_mypage.gif

992 ms

footer_partner.gif

footer_partner.gif

1003 ms

footer_contact.gif

footer_contact.gif

1040 ms

footer_sitemap.gif

footer_sitemap.gif

1012 ms

footer_english.gif

footer_english.gif

1026 ms

footer_legal.gif

footer_legal.gif

1031 ms

footer_policy.gif

footer_policy.gif

1017 ms

footer_privacy.gif

footer_privacy.gif

968 ms

bg_form500.gif

bg_form500.gif

1015 ms

footer_bg-search.gif

footer_bg-search.gif

1022 ms

footer_btn-search.gif

footer_btn-search.gif

1043 ms

footer_blog-press.gif

footer_blog-press.gif

1041 ms

footer_blog-wireless.gif

footer_blog-wireless.gif

1044 ms

footer_twitter.gif

footer_twitter.gif

932 ms

footer_facebook.gif

footer_facebook.gif

988 ms

footer_youtube.gif

footer_youtube.gif

1050 ms

footer_globalsite.gif

footer_globalsite.gif

1029 ms

ico_us.gif

ico_us.gif

1053 ms

ico_china.gif

ico_china.gif

1036 ms

ico_eu.gif

ico_eu.gif

934 ms

copyright.gif

copyright.gif

968 ms

print.css

print.css

161 ms

prev.jpg

prev.jpg

160 ms

next.jpg

next.jpg

186 ms

slidernavi_dc.png

slidernavi_dc.png

175 ms

slidernavi_display.png

slidernavi_display.png

176 ms

slidernavi_wi.png

slidernavi_wi.png

148 ms

slidernavi_ew.png

slidernavi_ew.png

184 ms

slidernavi_amc.png

slidernavi_amc.png

296 ms

slidernavi_dc-active.png

slidernavi_dc-active.png

316 ms

SEO Factors

silex.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 Silex.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 Silex.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

silex.jp

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