2.3 sec in total
87 ms
2 sec
168 ms
Click here to check amazing Docs Nexcess content for India. Otherwise, check out these important facts you probably never knew about docs.nexcess.net
Search our vast repository of web hosting help articles in the Nexcess Knowledge Base with expert guidance for optimizing your website and online store.
Visit docs.nexcess.netWe analyzed Docs.nexcess.net page load time and found that the first response time was 87 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
docs.nexcess.net performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.9 s
29/100
25%
Value5.4 s
56/100
10%
Value1,100 ms
24/100
30%
Value0.005
100/100
15%
Value12.1 s
16/100
10%
87 ms
1766 ms
78 ms
144 ms
157 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Docs.nexcess.net, 76% (34 requests) were made to Smhttp-nex.nexcesscdn.net and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Docs.nexcess.net.
Page size can be reduced by 257.3 kB (55%)
466.0 kB
208.8 kB
In fact, the total size of Docs.nexcess.net main page is 466.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. 35% of websites need less resources to load. Javascripts take 186.6 kB which makes up the majority of the site volume.
Potential reduce by 38.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 5.4 kB, which is 12% 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 38.0 kB or 84% of the original size.
Potential reduce by 3.4 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. Docs Nexcess images are well optimized though.
Potential reduce by 109.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 109.5 kB or 59% of the original size.
Potential reduce by 106.4 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. Docs.nexcess.net needs all CSS files to be minified and compressed as it can save up to 106.4 kB or 71% of the original size.
Number of requests can be reduced by 29 (74%)
39
10
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs 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 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
docs.nexcess.net
87 ms
docs.nexcess.net
1766 ms
css
78 ms
kbstyle.css
144 ms
bootstrap-3.3.2.min.css
157 ms
font-awesome-4.4.0.min.css
179 ms
nexcess.min-1445455052.css
173 ms
modernizr-2.7.1.nex.js
178 ms
modernizr.nex.js
193 ms
common.js
191 ms
ajax.js
197 ms
bg.png
71 ms
Nexcess_logo_tm.png
29 ms
nolines_plus.gif
55 ms
key.png
31 ms
address-book-blue.png
34 ms
chart_organisation.png
31 ms
globe-green.png
59 ms
email.png
61 ms
folder-open.png
63 ms
money-coin.png
64 ms
money_dollar.png
67 ms
folder.png
94 ms
database.png
94 ms
wall-brick.png
93 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
74 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
94 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
99 ms
fontawesome-webfont.woff
83 ms
code.png
45 ms
tableft1.png
209 ms
tabright1.png
45 ms
rss.png
42 ms
kb_article.gif
43 ms
jquery-1.11.0.min.js
36 ms
bootstrap-3.3.4.min.js
57 ms
script.min-1425912687.js
27 ms
inc5000_2014_new.png
54 ms
bbb.png
33 ms
fast500.png
66 ms
seal_js.php
20 ms
seal_image.php
30 ms
analytics.js
52 ms
collect
10 ms
collect
54 ms
docs.nexcess.net 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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.
docs.nexcess.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
docs.nexcess.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Docs.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 Docs.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.
docs.nexcess.net
Open Graph description is not detected on the main page of Docs Nexcess. 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: