32.9 sec in total
421 ms
30.6 sec
1.8 sec
Welcome to censtry.pt homepage info - get ready to check Censtry best content right away, or after learning these important things about censtry.pt
Censtry Electronics é um distribuidor global de componentes eletrônicos, nosso site é uma plataforma de fornecimento on-line completa. Fornecemos componentes eletrônicos com o melhor preço, novo origi...
Visit censtry.ptWe analyzed Censtry.pt page load time and found that the first response time was 421 ms and then it took 32.4 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
censtry.pt performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value11.0 s
0/100
25%
Value22.9 s
0/100
10%
Value380 ms
69/100
30%
Value0.002
100/100
15%
Value11.4 s
19/100
10%
421 ms
1241 ms
53 ms
862 ms
2589 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.pt, 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.4 sec) belongs to the original domain Censtry.pt.
Page size can be reduced by 344.9 kB (19%)
1.8 MB
1.4 MB
In fact, the total size of Censtry.pt main page is 1.8 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 997.2 kB which makes up the majority of the site volume.
Potential reduce by 252.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. 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 252.0 kB or 80% of the original size.
Potential reduce by 64.9 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 27.7 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. This website has mostly compressed JavaScripts.
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.pt has all CSS files already compressed.
Number of requests can be reduced by 31 (22%)
139
108
The browser has sent 139 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.pt
421 ms
www.censtry.pt
1241 ms
js
53 ms
all.min.css
862 ms
bootstrap.min.css
2589 ms
swiper-bundle.min.css
941 ms
iconfont.css
1162 ms
site.min.css
18541 ms
layout.min.css
612 ms
home.min.css
1295 ms
slick.css
938 ms
logo.png
1185 ms
70dbe0b1-240d-45a2-986a-ffa853511679.webp
1355 ms
9fa2bc71eb4a4e17b85460503d57e3b0.webp
1226 ms
f97dac10-61da-4b7c-b5ff-c405832d6fd0.webp
1330 ms
dd6d2744-885c-4478-4e7f-08dbbf1058dd.webp
1301 ms
ca22ffb1-a0c0-40a7-dcb4-08dbc6589f1f.webp
1437 ms
f2ac2465-e255-412e-b0c7-08dbc6589f1f.webp
1728 ms
c8149105be6e46c9b65a76ec17a9065c.webp
1788 ms
1296696d-e882-4d1d-093f-08dbb33edd15.webp
2335 ms
45f4b1d3-71d8-4f64-2bc1-08dbc6589f1f.webp
1849 ms
f6a62989-d5e6-4e97-0ab4-08dbb33edd15.webp
2884 ms
3458815a-d96f-4d88-2dc2-08dbbf1058dd.webp
4257 ms
6ebd09fd-2c9d-42ec-9e5a-08dbbf1058dd.webp
2318 ms
e9af8bb7-c310-4211-1b69-08dbb33edd15.webp
2472 ms
05b5804c-b8fe-49f5-edad-08dbbf1058dd.webp
3198 ms
fce7fcfb-af9d-4b34-9f19-08dbc6589f1e.webp
2885 ms
ef40cb82-fc1e-48b5-8c14-08dbc6589f1e.webp
2889 ms
e8f4e6c8177f459684bb7e552e5ab28a.webp
3033 ms
42f58576-c8bd-461c-9557-08dbc6589f1e.webp
3038 ms
8adefa99-a4b9-4491-913f-08dbc6589f1e.webp
3173 ms
9795e7f9-2448-4fe8-7ae0-08dbc6589f1e.webp
3453 ms
739903bd-f7dc-4146-71ca-08dbbf1058dd.webp
3288 ms
f88d24a0-afe6-47c2-8b46-08dbbf1058dd.webp
3322 ms
856ff777-eb6d-4480-80bb-b5c212d5f9d7.webp
3423 ms
c3284f4f5713466fadcfb266fd4b67c4.webp
4109 ms
996819f8-c857-4b5b-0988-08dbbf1058de.webp
3472 ms
56c8cb44b14849999dd1713a67970db3.webp
3574 ms
js
26 ms
analytics.js
62 ms
collect
18 ms
all.min.js
6420 ms
collect
26 ms
ga-audiences
83 ms
iconfont.js
4029 ms
swiper-bundle.min.js
4058 ms
bootstrap.bundle.min.js
3617 ms
layout.js
3409 ms
site.js
3921 ms
home.js
3445 ms
slick.min.js
4390 ms
a3647c00-a974-4463-1aeb-08dbb33edd15.webp
4473 ms
51635bcd-782e-426a-1e81-08dbbf1058dd.webp
3868 ms
ed796a3a-e632-4c88-6217-08dbbf1058dd.webp
3895 ms
9fba081f-2324-4a5a-605c-08dbbf1058dd.webp
4511 ms
home-iso9001.png
4748 ms
home-iso14001.png
4781 ms
home-da.png
5317 ms
home-iaf.png
5231 ms
home-cnas.png
4096 ms
home-ukas.png
4898 ms
home-category-banner.png
5663 ms
microchip-log.png
4839 ms
infineon-log.png
4347 ms
xilinx-log.png
4609 ms
analog-log.png
4491 ms
onsemi-log.png
4624 ms
tdk.gif
4418 ms
dingtalk-20220510150912.jpg
4396 ms
c0fe827e-f36e-4384-119e-08dbb33edd15.webp
4410 ms
efe1b6be-9297-4b2c-6a05-08dbbf1058de.webp
4356 ms
7bf898cb-150e-414e-c9cd-08dbbf1058dd.webp
5051 ms
f9c0ee83797a41b7a6e99814ece0f609.webp
4259 ms
eb72570a-5025-4456-26f7-08dbbf1058de.webp
4958 ms
bb14cd1d01704139aa38f7024d020cee.webp
4335 ms
44b81fe6d74f4125b8ff2e8c9a59a539.webp
4184 ms
av02-0662en.jpg
3727 ms
av02-0662en.jpg
3631 ms
bta26600b.jpg
4111 ms
20210310104241-2158.jpg
3503 ms
20210113143117-3401.jpg
3674 ms
stm32g071g8u6tr.jpg
3663 ms
stch02tr.jpg
3455 ms
30120215-c4ef-4f1a-fd99-08dbc6589f1e.webp
3788 ms
b03a96fe-6bb5-4845-203b-08dbb33edd15.webp
3530 ms
33100b9a-f8fd-4d1f-b7d7-08dbc6589f1e.webp
3398 ms
60d21464-c911-44c3-ae24-08dbbf1058dd.webp
3043 ms
61da2f2d-0280-447d-c876-08dbbf1058dd.webp
3945 ms
f752c41c-3fc2-4d18-d97f-08dbbf1058dd.webp
2909 ms
3f914e2d-d7b3-40e4-8910-08dbbf1058dd.webp
2867 ms
1401f4a1-8ed5-4bfd-f6b2-08dbbf1058dc.webp
2535 ms
0d9f3babb7c5476b943aa36cfd2df124.webp
2416 ms
20200827115549-0433.jpg
2946 ms
edip-24-t.jpg
1921 ms
4f97b2ba8a384d11836863506b6133cb.webp
1999 ms
e686b94da0514668a26ba2b2e36e717b.webp
1846 ms
home-quality-equipment1.png
3665 ms
home-quality-equipment2.png
3200 ms
home-quality-equipment3.png
2526 ms
home-quality-equipment4.png
2939 ms
home-quality-projects1.png
7706 ms
home-quality-projects2.png
3666 ms
home-quality-projects3.png
5714 ms
home-quality-projects4.png
8117 ms
integrated-circuit-codes-and-ic-code-list.png
19591 ms
integrated-circuits-definition-and-meaning.png
19564 ms
pnp-transistor-symbol.png
7795 ms
transistor-npn-vs-pnp.png
11663 ms
nmos-vs-pmos-new.png
8507 ms
how-many-transistor-in-a-cpu.png
20360 ms
ukas.png
8379 ms
iso.png
8366 ms
cnas.png
8289 ms
iaf.png
9025 ms
pb.png
10314 ms
da.png
10305 ms
visa.png
10504 ms
mastercard.png
10236 ms
unionpay.png
10138 ms
wu.png
10181 ms
paypal.png
10222 ms
product-default.png
11368 ms
layer.css
684 ms
home-banner1.jpg
4514 ms
home-banner2.jpg
7022 ms
home-banner3.jpg
7106 ms
home-banner4.jpg
9388 ms
home-blogs-bg.png
10109 ms
iconfont.woff
7687 ms
default
101 ms
SelectLang
7124 ms
us.jpg
1321 ms
pt.jpg
1277 ms
twk-arr-find-polyfill.js
58 ms
twk-object-values-polyfill.js
177 ms
twk-event-polyfill.js
197 ms
twk-entries-polyfill.js
58 ms
twk-iterator-polyfill.js
184 ms
twk-promise-polyfill.js
65 ms
twk-main.js
69 ms
twk-vendor.js
153 ms
twk-chunk-vendors.js
199 ms
twk-chunk-common.js
83 ms
twk-runtime.js
94 ms
twk-app.js
105 ms
censtry.pt 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.pt 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.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Censtry.pt 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 Portuguese language. Our system also found out that Censtry.pt 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.pt
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: