Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

cor.com

EMI Filters and Compliance | TE Connectivity

Page Load Speed

13.1 sec in total

First Response

52 ms

Resources Loaded

12.8 sec

Page Rendered

247 ms

cor.com screenshot

About Website

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.com

Key Findings

We 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.

Performance Metrics

cor.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value14,390 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.9 s

0/100

10%

Network Requests Diagram

cor.com

52 ms

emi-filters.html

1701 ms

c3fcd7874ee0ce5071ad60d0fb57d4017100113b9c14

755 ms

ruxitagentjs_ICA237Vdefghijmoqrtuvx_10247220811100421.js

280 ms

notice

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 Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (76%)

Content Size

2.0 MB

After Optimization

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.

HTML Optimization

-84%

Potential reduce by 262.3 kB

  • Original 312.9 kB
  • After minification 251.1 kB
  • After compression 50.6 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.

Image Optimization

-0%

Potential reduce by 54 B

  • Original 37.7 kB
  • After minification 37.6 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. Cor images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 16.9 kB

  • Original 277.0 kB
  • After minification 276.6 kB
  • After compression 260.1 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.

CSS Optimization

-91%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 128.7 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. 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.

Requests Breakdown

Number of requests can be reduced by 56 (58%)

Requests Now

96

After Optimization

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.

Accessibility Review

cor.com accessibility score

74

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

cor.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

cor.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: