13.1 sec in total
52 ms
12.8 sec
247 ms
Visit cor.com now to see the best up-to-date Cor content and also check out these interesting facts you probably never knew about cor.com
TE offers Corcom EMI filters that can help control EMI signal issues and are recognized worldwide with approval from major safety agencies.
Visit cor.comWe analyzed Cor.com page load time and found that the first response time was 52 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cor.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.8 s
31/100
25%
Value9.0 s
14/100
10%
Value14,390 ms
0/100
30%
Value0
100/100
15%
Value30.9 s
0/100
10%
52 ms
1701 ms
755 ms
280 ms
148 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cor.com, 51% (55 requests) were made to Te.com and 8% (9 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Teconnectivity.o9trf8.net.
Page size can be reduced by 1.5 MB (76%)
2.0 MB
477.1 kB
In fact, the total size of Cor.com main page is 2.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. 70% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 262.3 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 61.7 kB, which is 20% 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 262.3 kB or 84% of the original size.
Potential reduce by 54 B
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. Cor images are well optimized though.
Potential reduce by 16.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.2 MB
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. Cor.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 91% of the original size.
Number of requests can be reduced by 56 (58%)
96
40
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
cor.com
52 ms
emi-filters.html
1701 ms
c3fcd7874ee0ce5071ad60d0fb57d4017100113b9c14
755 ms
ruxitagentjs_ICA237Vdefghijmoqrtuvx_10247220811100421.js
280 ms
notice
148 ms
fonts.css
129 ms
product-navigation.css
138 ms
te-global-components.css
258 ms
launch-b98ce4e2ccc2.min.js
157 ms
modernizr-custom.js
208 ms
cxbus.min.js
119 ms
require.js
127 ms
all.min.css
166 ms
flag-icon.min.css
199 ms
A1999995-e899-4833-b972-0c4891e19a8d1.js
1101 ms
gtm.js
1282 ms
827XA-7NWZT-CGSAU-WP5SG-7KSSA
1659 ms
AppMeasurement.min.js
129 ms
ip.json
1000 ms
te-connectivity-logo.svg
692 ms
te-connectivity-logo.png
665 ms
product-category.jpg
665 ms
product-category.jpg
664 ms
product-category.jpg
664 ms
product-category.jpg
663 ms
corcom-faclity-catalog-1.jpg
918 ms
promo-medium.jpg
916 ms
b8db69f9-df9e-480f-9c1c-d76a1bb29a62.woff
704 ms
874c8a3d-82cd-4b46-839b-521b49950be0.woff
704 ms
0b86525a-9c26-4c1d-9abe-c05fd31ecf2e.woff
701 ms
script.min.js
402 ms
analytics.js
793 ms
conversion_async.js
1223 ms
uwt.js
1212 ms
js
357 ms
pixel.js
1157 ms
loading-anim.gif
396 ms
rd
243 ms
dest5.html
1483 ms
id
1440 ms
widgets-core.min.js
2370 ms
config.json
1106 ms
collect
757 ms
1759 ms
1980 ms
rp.gif
1056 ms
collect
1834 ms
3905eff9719669f7.min.js
1694 ms
10771
3471 ms
RC06327f2dbbde43528227b63f7ee068de-source.min.js
442 ms
RCa3ee73b13d4a4435b27f1b13e015124e-source.min.js
1279 ms
elqCfg.min.js
3332 ms
main.js
1206 ms
AppMeasurement_Module_AudienceManagement.min.js
1202 ms
fa-solid-900.woff
1007 ms
fa-regular-400.woff
1006 ms
fa-light-300.woff
1086 ms
fa-brands-400.woff
944 ms
adsct
3125 ms
adsct
3150 ms
adsct
3146 ms
adsct
3128 ms
roboto.css
2341 ms
adsct
2336 ms
ga-audiences
2283 ms
ibs:dpid=21&dpuuid=213060604290007709906
2001 ms
2235 ms
2264 ms
region
1832 ms
info
851 ms
getAccessToken.do
488 ms
topNavBanner.json
607 ms
us.svg
304 ms
general-listing.js
382 ms
product-navigation.js
319 ms
rb_ccb92403-42aa-451e-af79-1039b3474bc6
351 ms
svrGP
336 ms
ip.json
146 ms
ibs:dpid=477&dpuuid=f4f56e1d5ccd4877b06a20d7189b7de796b7e9058cf228814015876a136a9bd2b0da87c991749652
38 ms
ibs:dpid=601&dpuuid=211992615464584&random=1664546774
54 ms
ibs:dpid=22052&dpuuid=3630423212827344900
42 ms
ibs:dpid=575&dpuuid=-7941823156958640274
13 ms
ibs:dpid=73426&dpuuid=33464372363322529652447962003850786708
19 ms
ibs:dpid=129099&dpuuid=0728a38d05c6ba4ac149971d6cf281d7
8 ms
validateCookie
10 ms
validateCookie
5 ms
ibs:dpid=121998&dpuuid=e643034f5b2e3e029a726a07b0ba972a
8 ms
svrGP.aspx
1011 ms
163 ms
product-details.png
657 ms
product-details.png
657 ms
product-details.png
660 ms
product-details.png
658 ms
product-details.png
654 ms
product-details.png
657 ms
product-details.png
654 ms
product-details.png
660 ms
product-details.png
657 ms
product-details.png
658 ms
product-details.png
659 ms
product-details.png
659 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
88 ms
twitter_circle_color.svg
130 ms
linkedin_circle_color.svg
123 ms
facebook_circle_color.svg
127 ms
add-this-more-icon-default_al.svg
125 ms
add-this-more-icon-hover_al.svg
45 ms
s49848729788791
63 ms
cor.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
cor.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cor.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cor.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cor.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.
cor.com
Open Graph data is detected on the main page of Cor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: