Tools & Wizards About Us
go.nexcess.net screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

go.nexcess.net

Fully Managed Hosting Services | Nexcess

Page Load Speed

2.9 sec in total

First Response

562 ms

Resources Loaded

1.6 sec

Page Rendered

745 ms

go.nexcess.net screenshot

About Website

Visit go.nexcess.net now to see the best up-to-date Go Nexcess content for India and also check out these interesting facts you probably never knew about go.nexcess.net

Managed hosting services optimized for WordPress, Magento, and ecommerce. Elevate your business, scale without upsells. Fast speeds, 24/7/365 support.

Visit go.nexcess.net

Key Findings

We analyzed Go.nexcess.net page load time and found that the first response time was 562 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

go.nexcess.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value30,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value41.2 s

0/100

10%

Network Requests Diagram

www.nexcess.net

562 ms

gtm.js

761 ms

polyfill-d3e6fea304b271f97f38.js

363 ms

app-8f52a253df4aa74c40a2.js

363 ms

framework-85e20d176838d80991d7.js

372 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Go.nexcess.net, 6% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (761 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.6 kB (62%)

Content Size

598.0 kB

After Optimization

229.4 kB

  • HTML
  • Images

In fact, the total size of Go.nexcess.net main page is 598.0 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. 65% of websites need less resources to load. HTML takes 587.8 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 368.1 kB

  • Original 587.8 kB
  • After minification 587.1 kB
  • After compression 219.7 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 368.1 kB or 63% of the original size.

Image Optimization

-5%

Potential reduce by 481 B

  • Original 10.2 kB
  • After minification 9.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. Go Nexcess images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 4 (44%)

Requests Now

9

After Optimization

5

  • Images
  • JavaScript

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

Network Requests Diagram

www.nexcess.net

www.nexcess.net

562 ms

gtm.js

gtm.js

761 ms

polyfill-d3e6fea304b271f97f38.js

polyfill-d3e6fea304b271f97f38.js

363 ms

app-8f52a253df4aa74c40a2.js

app-8f52a253df4aa74c40a2.js

363 ms

framework-85e20d176838d80991d7.js

framework-85e20d176838d80991d7.js

372 ms

webpack-runtime-5143be3167da2d3d77f4.js

webpack-runtime-5143be3167da2d3d77f4.js

381 ms

avatar-joe-howard-fbb36d4cbe1c7c12eb72cd9c163eab79.png

avatar-joe-howard-fbb36d4cbe1c7c12eb72cd9c163eab79.png

379 ms

LW-family-logo-1b40c079e94d73114548673494ca923f.svg

LW-family-logo-1b40c079e94d73114548673494ca923f.svg

375 ms

lw-logo-6b43a943c71c1ff39eb608d6c83dde05.svg

lw-logo-6b43a943c71c1ff39eb608d6c83dde05.svg

372 ms

stellarwp-b7193b0fa53948a8b253fe0c6a28885b.svg

stellarwp-b7193b0fa53948a8b253fe0c6a28885b.svg

364 ms

Inter-Regular-8c206db99195777c67691cbba9d64393.woff

Inter-Regular-8c206db99195777c67691cbba9d64393.woff

265 ms

Inter-SemiBold-cca62d21c8c555c392e580a52e0d4426.woff

Inter-SemiBold-cca62d21c8c555c392e580a52e0d4426.woff

263 ms

PPRadioGrotesk-Medium-81b9e7ef87767de9960e5f8d22cbd427.woff

PPRadioGrotesk-Medium-81b9e7ef87767de9960e5f8d22cbd427.woff

261 ms

PPRadioGrotesk-Regular-80aa346c394ebf891aa894d2401c7b66.woff

PPRadioGrotesk-Regular-80aa346c394ebf891aa894d2401c7b66.woff

262 ms

PPRadioGrotesk-Bold-adc76931b62f6b8e933f409f45340aad.woff

PPRadioGrotesk-Bold-adc76931b62f6b8e933f409f45340aad.woff

262 ms

montserrat-all-400-normal-aa917f2f47304e192c88bd6ce6170eb3.woff

montserrat-all-400-normal-aa917f2f47304e192c88bd6ce6170eb3.woff

263 ms

montserrat-all-500-normal-598ec45d84be8894cb1a64032f501cb0.woff

montserrat-all-500-normal-598ec45d84be8894cb1a64032f501cb0.woff

265 ms

montserrat-all-600-normal-b2ade74aea584fdcaa5612cb31ed3abd.woff

montserrat-all-600-normal-b2ade74aea584fdcaa5612cb31ed3abd.woff

266 ms

Accessibility Review

go.nexcess.net accessibility score

86

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

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

Heading elements are not in a sequentially-descending order

Best Practices

go.nexcess.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

go.nexcess.net SEO score

99

Search Engine Optimization Advices

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 Go.nexcess.net 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 Go.nexcess.net 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

go.nexcess.net

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