32.1 sec in total
265 ms
30.1 sec
1.8 sec
Visit censtry.it now to see the best up-to-date Censtry content and also check out these interesting facts you probably never knew about censtry.it
Censtry Electronics è un distributore globale di componenti elettronici, il nostro sito Web è una piattaforma di approvvigionamento online unica. Forniamo componenti elettronici con il miglior prezzo,...
Visit censtry.itWe analyzed Censtry.it page load time and found that the first response time was 265 ms and then it took 31.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
censtry.it performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.1 s
2/100
25%
Value18.3 s
0/100
10%
Value220 ms
87/100
30%
Value0.238
52/100
15%
Value13.4 s
11/100
10%
265 ms
1027 ms
68 ms
878 ms
1925 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 87% of them (126 requests) were addressed to the original Censtry.it, 9% (13 requests) were made to Embed.tawk.to and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Censtry.it.
Page size can be reduced by 618.4 kB (33%)
1.9 MB
1.3 MB
In fact, the total size of Censtry.it main page is 1.9 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. 60% of websites need less resources to load. Images take 827.2 kB which makes up the majority of the site volume.
Potential reduce by 251.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 94.5 kB, which is 30% 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 251.5 kB or 80% of the original size.
Potential reduce by 45.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. Censtry images are well optimized though.
Potential reduce by 320.9 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 320.9 kB or 48% of the original size.
Potential reduce by 275 B
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. Censtry.it has all CSS files already compressed.
Number of requests can be reduced by 31 (22%)
138
107
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Censtry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
censtry.it
265 ms
www.censtry.it
1027 ms
js
68 ms
all.min.css
878 ms
bootstrap.min.css
1925 ms
swiper-bundle.min.css
552 ms
iconfont.css
999 ms
site.min.css
504 ms
layout.min.css
583 ms
home.min.css
614 ms
slick.css
626 ms
logo.png
981 ms
70dbe0b1-240d-45a2-986a-ffa853511679.webp
678 ms
9fa2bc71eb4a4e17b85460503d57e3b0.webp
1397 ms
f97dac10-61da-4b7c-b5ff-c405832d6fd0.webp
1103 ms
dd6d2744-885c-4478-4e7f-08dbbf1058dd.webp
935 ms
ca22ffb1-a0c0-40a7-dcb4-08dbc6589f1f.webp
1702 ms
f2ac2465-e255-412e-b0c7-08dbc6589f1f.webp
1050 ms
c8149105be6e46c9b65a76ec17a9065c.webp
1392 ms
1296696d-e882-4d1d-093f-08dbb33edd15.webp
2620 ms
45f4b1d3-71d8-4f64-2bc1-08dbc6589f1f.webp
1178 ms
f6a62989-d5e6-4e97-0ab4-08dbb33edd15.webp
1252 ms
3458815a-d96f-4d88-2dc2-08dbbf1058dd.webp
1328 ms
6ebd09fd-2c9d-42ec-9e5a-08dbbf1058dd.webp
1403 ms
e9af8bb7-c310-4211-1b69-08dbb33edd15.webp
1624 ms
05b5804c-b8fe-49f5-edad-08dbbf1058dd.webp
2131 ms
fce7fcfb-af9d-4b34-9f19-08dbc6589f1e.webp
1797 ms
ef40cb82-fc1e-48b5-8c14-08dbc6589f1e.webp
1778 ms
e8f4e6c8177f459684bb7e552e5ab28a.webp
2086 ms
42f58576-c8bd-461c-9557-08dbc6589f1e.webp
1856 ms
8adefa99-a4b9-4491-913f-08dbc6589f1e.webp
2222 ms
9795e7f9-2448-4fe8-7ae0-08dbc6589f1e.webp
2264 ms
739903bd-f7dc-4146-71ca-08dbbf1058dd.webp
2362 ms
f88d24a0-afe6-47c2-8b46-08dbbf1058dd.webp
2466 ms
856ff777-eb6d-4480-80bb-b5c212d5f9d7.webp
3337 ms
c3284f4f5713466fadcfb266fd4b67c4.webp
3017 ms
996819f8-c857-4b5b-0988-08dbbf1058de.webp
2418 ms
56c8cb44b14849999dd1713a67970db3.webp
2513 ms
js
73 ms
analytics.js
18 ms
collect
35 ms
collect
26 ms
ga-audiences
98 ms
a3647c00-a974-4463-1aeb-08dbb33edd15.webp
2730 ms
all.min.js
5889 ms
iconfont.js
5963 ms
swiper-bundle.min.js
4984 ms
bootstrap.bundle.min.js
3916 ms
layout.js
2686 ms
site.js
2703 ms
home.js
2542 ms
slick.min.js
2649 ms
51635bcd-782e-426a-1e81-08dbbf1058dd.webp
2691 ms
ed796a3a-e632-4c88-6217-08dbbf1058dd.webp
2678 ms
9fba081f-2324-4a5a-605c-08dbbf1058dd.webp
3728 ms
home-iso9001.png
4113 ms
home-iso14001.png
4012 ms
home-da.png
3759 ms
home-iaf.png
5319 ms
home-cnas.png
4453 ms
home-ukas.png
4751 ms
home-category-banner.png
7778 ms
microchip-log.png
4372 ms
infineon-log.png
4821 ms
xilinx-log.png
5925 ms
analog-log.png
6904 ms
onsemi-log.png
4772 ms
tdk.gif
4618 ms
iconfont.woff
5233 ms
dingtalk-20220510150912.jpg
4744 ms
c0fe827e-f36e-4384-119e-08dbb33edd15.webp
4732 ms
efe1b6be-9297-4b2c-6a05-08dbbf1058de.webp
4762 ms
7bf898cb-150e-414e-c9cd-08dbbf1058dd.webp
4944 ms
f9c0ee83797a41b7a6e99814ece0f609.webp
5282 ms
eb72570a-5025-4456-26f7-08dbbf1058de.webp
5346 ms
bb14cd1d01704139aa38f7024d020cee.webp
4953 ms
44b81fe6d74f4125b8ff2e8c9a59a539.webp
4927 ms
av02-0662en.jpg
4601 ms
av02-0662en.jpg
4477 ms
bta26600b.jpg
4623 ms
20210310104241-2158.jpg
4514 ms
20210113143117-3401.jpg
4478 ms
stm32g071g8u6tr.jpg
4555 ms
stch02tr.jpg
5907 ms
30120215-c4ef-4f1a-fd99-08dbc6589f1e.webp
5479 ms
b03a96fe-6bb5-4845-203b-08dbb33edd15.webp
4855 ms
33100b9a-f8fd-4d1f-b7d7-08dbc6589f1e.webp
3757 ms
60d21464-c911-44c3-ae24-08dbbf1058dd.webp
3652 ms
61da2f2d-0280-447d-c876-08dbbf1058dd.webp
3652 ms
f752c41c-3fc2-4d18-d97f-08dbbf1058dd.webp
3478 ms
3f914e2d-d7b3-40e4-8910-08dbbf1058dd.webp
3526 ms
1401f4a1-8ed5-4bfd-f6b2-08dbbf1058dc.webp
3358 ms
0d9f3babb7c5476b943aa36cfd2df124.webp
2997 ms
20200827115549-0433.jpg
3277 ms
edip-24-t.jpg
3352 ms
layer.css
2562 ms
4f97b2ba8a384d11836863506b6133cb.webp
3419 ms
e686b94da0514668a26ba2b2e36e717b.webp
3095 ms
home-quality-equipment1.png
4212 ms
home-quality-equipment2.png
3515 ms
home-quality-equipment3.png
4496 ms
home-quality-equipment4.png
4223 ms
home-quality-projects1.png
3934 ms
home-quality-projects2.png
3579 ms
home-quality-projects3.png
4392 ms
home-quality-projects4.png
6376 ms
integrated-circuit-codes-and-ic-code-list.png
19537 ms
integrated-circuits-definition-and-meaning.png
20460 ms
pnp-transistor-symbol.png
4393 ms
transistor-npn-vs-pnp.png
9556 ms
nmos-vs-pmos-new.png
4368 ms
how-many-transistor-in-a-cpu.png
20301 ms
ukas.png
4609 ms
iso.png
4726 ms
cnas.png
4804 ms
iaf.png
4817 ms
pb.png
5205 ms
da.png
4982 ms
visa.png
4905 ms
mastercard.png
5154 ms
unionpay.png
5165 ms
wu.png
5123 ms
paypal.png
5407 ms
product-default.png
5759 ms
home-banner1.jpg
9894 ms
home-banner2.jpg
8538 ms
default
218 ms
home-banner3.jpg
10154 ms
SelectLang
8389 ms
home-banner4.jpg
19825 ms
home-blogs-bg.png
14705 ms
us.jpg
2435 ms
it.jpg
2513 ms
twk-arr-find-polyfill.js
64 ms
twk-object-values-polyfill.js
309 ms
twk-event-polyfill.js
76 ms
twk-entries-polyfill.js
187 ms
twk-iterator-polyfill.js
201 ms
twk-promise-polyfill.js
73 ms
twk-main.js
84 ms
twk-vendor.js
174 ms
twk-chunk-vendors.js
204 ms
twk-chunk-common.js
92 ms
twk-runtime.js
107 ms
twk-app.js
120 ms
censtry.it accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
censtry.it 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
censtry.it SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Censtry.it can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Italian language. Our system also found out that Censtry.it 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.
censtry.it
Open Graph description is not detected on the main page of Censtry. 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: