4.7 sec in total
1.1 sec
2.8 sec
870 ms
Visit components76.com now to see the best up-to-date COMPONENTS 76 content for Japan and also check out these interesting facts you probably never knew about components76.com
「コンポーネンツ76」では高周波部品と光学部品の検索販売、商品数は業界最大規模の5000種類以上取り扱い!アッテネータ、カプラ、導波管製品、同軸ケーブル、アダプタなどの部品をはじめ、スペアナ、オシロ、マルチメータなどの計測機器・関連機器保証ありの優良中古在庫も取り扱っております!
Visit components76.comWe analyzed Components76.com page load time and found that the first response time was 1.1 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
components76.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value13.3 s
0/100
25%
Value9.0 s
14/100
10%
Value3,620 ms
1/100
30%
Value0.112
86/100
15%
Value13.6 s
11/100
10%
1051 ms
15 ms
70 ms
581 ms
38 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 49% of them (26 requests) were addressed to the original Components76.com, 21% (11 requests) were made to Platform.twitter.com and 6% (3 requests) were made to Contents.bownow.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Components76.com.
Page size can be reduced by 100.8 kB (27%)
373.0 kB
272.2 kB
In fact, the total size of Components76.com main page is 373.0 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. 55% of websites need less resources to load. Images take 217.5 kB which makes up the majority of the site volume.
Potential reduce by 29.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. 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 29.0 kB or 80% of the original size.
Potential reduce by 2.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. COMPONENTS 76 images are well optimized though.
Potential reduce by 16.2 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 16.2 kB or 27% of the original size.
Potential reduce by 53.0 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. Components76.com needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 88% of the original size.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COMPONENTS 76. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
components76.com
1051 ms
font-awesome.min.css
15 ms
normalize.min.css
70 ms
style.css
581 ms
widgets.js
38 ms
conversion_async.js
38 ms
jquery-1.10.2.min.js
33 ms
underscore-min.js
26 ms
ajaxzip3.js
27 ms
utility.js
208 ms
components76.js
593 ms
analytics.js
264 ms
trace.js
618 ms
hd_logo.png
336 ms
mail01.png
336 ms
tel01.png
337 ms
menu01.png
526 ms
regist.png
520 ms
mail02.png
528 ms
user01.png
526 ms
fav01.png
530 ms
cart01.png
528 ms
147580262257f6f5fe7df49-thumb.jpg
715 ms
147580258957f6f5dd7f8a8-thumb.JPG
723 ms
noimage.png
724 ms
147581992457f73994db367-thumb.JPG
734 ms
contact.png
734 ms
147615688657fc5dd682513.jpg
1125 ms
147766618058136584f0544.jpg
1277 ms
illust01.png
914 ms
illust02.png
914 ms
illust03.png
921 ms
illust04.png
922 ms
logo.png
1109 ms
gotop.png
1110 ms
fontawesome-webfont.woff
76 ms
widget_iframe.c4bdc17e77719578b594d5555bee90db.html
75 ms
collect
36 ms
collect
91 ms
settings
99 ms
horizon_timeline.4836f7a62ef55f5880337b3b6602854f.js
3 ms
embeds
27 ms
Components7676
305 ms
trace.js
156 ms
polyfills-57d3feabe8bfd4ee389c.js
5 ms
runtime-c5040a30986fc1d092cc.js
8 ms
modules.c7def0268c66f6a548ed.js
17 ms
main-e9db78f5e7b3d83edd5e.js
18 ms
_app-6b59be76f6e3292c4dd6.js
17 ms
%5BscreenName%5D-568c81a96d7917ec4ebb.js
18 ms
_buildManifest.js
16 ms
_ssgManifest.js
21 ms
trace.js
156 ms
components76.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
components76.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
components76.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Components76.com 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 Components76.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.
components76.com
Open Graph description is not detected on the main page of COMPONENTS 76. 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: