Tools & Wizards About Us
nexus.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nexus.com

Amphenol NEXUS: Advanced Telecommunications Manufacturing

Page Load Speed

1.2 sec in total

First Response

241 ms

Resources Loaded

742 ms

Page Rendered

253 ms

nexus.com screenshot

About Website

Visit nexus.com now to see the best up-to-date NEXUS content for United States and also check out these interesting facts you probably never knew about nexus.com

Amphenol NEXUS Technologies is a leader in telecommunications manufacturing, offering advanced solutions for connectivity and communication. Explore today.

Visit nexus.com

Key Findings

We analyzed Nexus.com page load time and found that the first response time was 241 ms and then it took 995 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

nexus.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

nexus.com

241 ms

nexus.com

207 ms

autoptimize_0550f780135bc116d85eb9c18c760db6.css

17 ms

js

128 ms

js

164 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 78% of them (36 requests) were addressed to the original Nexus.com, 9% (4 requests) were made to Googletagmanager.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (241 ms) belongs to the original domain Nexus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.6 kB (11%)

Content Size

340.1 kB

After Optimization

301.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nexus.com main page is 340.1 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 175.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 38.2 kB

  • Original 49.2 kB
  • After minification 49.1 kB
  • After compression 11.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 38.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 175.6 kB
  • After minification 175.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. NEXUS images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 478 B

  • Original 79.1 kB
  • After minification 79.1 kB
  • After compression 78.6 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

-0%

Potential reduce by 0 B

  • Original 36.3 kB
  • After minification 36.3 kB
  • After compression 36.3 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. Nexus.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (43%)

Requests Now

40

After Optimization

23

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NEXUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

nexus.com

nexus.com

241 ms

nexus.com

nexus.com

207 ms

autoptimize_0550f780135bc116d85eb9c18c760db6.css

autoptimize_0550f780135bc116d85eb9c18c760db6.css

17 ms

js

js

128 ms

js

js

164 ms

email-decode.min.js

email-decode.min.js

12 ms

lazysizes.min.js

lazysizes.min.js

208 ms

autoptimize_4cc8f52d2cfa955ba52f1b2fe328b496.js

autoptimize_4cc8f52d2cfa955ba52f1b2fe328b496.js

41 ms

gtm.js

gtm.js

176 ms

gtm.js

gtm.js

149 ms

webfont.js

webfont.js

127 ms

ico-search.svg

ico-search.svg

92 ms

hero-bg-shape.png

hero-bg-shape.png

93 ms

email.svg

email.svg

93 ms

phone.svg

phone.svg

116 ms

search.svg

search.svg

114 ms

scroll-down.svg

scroll-down.svg

113 ms

product-bg-shape.png

product-bg-shape.png

130 ms

autoptimize_single_1f3f0656eb654e30353bf1571e1d7483.css

autoptimize_single_1f3f0656eb654e30353bf1571e1d7483.css

114 ms

ico-exit.svg

ico-exit.svg

49 ms

hamburger-menu.svg

hamburger-menu.svg

45 ms

telephone-plugs-and-jacks.png

telephone-plugs-and-jacks.png

45 ms

m55116-mil-spec-and-mil-spec-type-connectors.png

m55116-mil-spec-and-mil-spec-type-connectors.png

47 ms

7-and-10-pin-waterproof-breakaway-connectors.png

7-and-10-pin-waterproof-breakaway-connectors.png

77 ms

tac-connectors.png

tac-connectors.png

74 ms

microphone-plugs-and-jacks.png

microphone-plugs-and-jacks.png

74 ms

push-button-switches.png

push-button-switches.png

75 ms

photo-for-website.jpg

photo-for-website.jpg

75 ms

about-us-image.jpg

about-us-image.jpg

91 ms

military.jpg

military.jpg

91 ms

download_w_trans-1.png

download_w_trans-1.png

90 ms

dropdown-arrow-black.png

dropdown-arrow-black.png

91 ms

ampheno-nexus-logo.png

ampheno-nexus-logo.png

88 ms

1-telephone.png

1-telephone.png

91 ms

css

css

53 ms

shape.png

shape.png

14 ms

product-overlay-border.png

product-overlay-border.png

11 ms

about-us-bg-shape.png

about-us-bg-shape.png

15 ms

location.svg

location.svg

15 ms

phone-hover.svg

phone-hover.svg

15 ms

fax.svg

fax.svg

15 ms

email-hover.svg

email-hover.svg

42 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

40 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

41 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

53 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

54 ms

Accessibility Review

nexus.com accessibility score

98

Accessibility Issues

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.

Best Practices

nexus.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nexus.com SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nexus.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nexus.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

nexus.com

Open Graph data is detected on the main page of NEXUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: