30.4 sec in total
237 ms
21.1 sec
9 sec
Visit nexusdirectory.com now to see the best up-to-date Nexus Directory content for India and also check out these interesting facts you probably never knew about nexusdirectory.com
A quality web directory where you can submit a site, add urls or submit links to the the web directory
Visit nexusdirectory.comWe analyzed Nexusdirectory.com page load time and found that the first response time was 237 ms and then it took 30.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
nexusdirectory.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value3.7 s
59/100
25%
Value2.4 s
98/100
10%
Value40 ms
100/100
30%
Value0.03
100/100
15%
Value2.9 s
96/100
10%
237 ms
886 ms
101 ms
200 ms
402 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 48% of them (35 requests) were addressed to the original Nexusdirectory.com, 14% (10 requests) were made to Contextual.media.net and 8% (6 requests) were made to Simage2.pubmatic.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Cm.g.doubleclick.net.
Page size can be reduced by 845.9 kB (61%)
1.4 MB
544.6 kB
In fact, the total size of Nexusdirectory.com main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.3 kB or 77% of the original size.
Potential reduce by 10.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. Obviously, Nexus Directory needs image optimization as it can save up to 10.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 788.3 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 788.3 kB or 62% of the original size.
Potential reduce by 19.9 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. Nexusdirectory.com needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 82% of the original size.
Number of requests can be reduced by 47 (68%)
69
22
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nexus Directory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
nexusdirectory.com
237 ms
www.nexusdirectory.com
886 ms
main.css
101 ms
ie8.css
200 ms
jquery-1.3.2.min.js
402 ms
ajaxupload.js
552 ms
jquery-ui-1.7.2.custom.min.js
522 ms
jquery.validate.js
447 ms
formtool.js
500 ms
prototype.js
500 ms
scriptaculous.js
788 ms
thickbox.js
869 ms
ThickBox.css
869 ms
categ_selection.js
858 ms
nmedianet.js
836 ms
infolinks_main.js
820 ms
builder.js
81 ms
effects.js
115 ms
dragdrop.js
230 ms
controls.js
229 ms
slider.js
210 ms
image.aspx
634 ms
body_bg.jpg
213 ms
logo.png
269 ms
button.jpg
416 ms
searchBtn.jpg
351 ms
hMenuContainerBg.jpg
333 ms
hMenuContainerLeft.jpg
585 ms
hMenuContainerRight.jpg
583 ms
hMenuInactive.jpg
584 ms
boxTop.jpg
584 ms
boxMiddle.jpg
709 ms
liBul.jpg
551 ms
boxBottom.jpg
709 ms
maincontentC.jpg
709 ms
maincontentT.jpg
708 ms
maincontentB.jpg
699 ms
px.gif
497 ms
px.gif
423 ms
bping.php
158 ms
fcmdynet.js
147 ms
checksync.php
644 ms
mediamain.html
1860 ms
ga.js
244 ms
__utm.gif
370 ms
bping.php
168 ms
fcmdynet.js
639 ms
cksync.html
396 ms
nrr.js
1649 ms
cksync.php
2609 ms
mediamain.html
2057 ms
user_sync.html
3111 ms
usersyncup-an.html
2706 ms
ice.js
2638 ms
AdChoices.png
2889 ms
loadingAnimation.gif
2392 ms
bql.php
1398 ms
showad.js
1337 ms
bql.php
1161 ms
PugMaster
860 ms
bqi.php
249 ms
p-P7x87XHnVfbWr.gif
3471 ms
pixel
4070 ms
generic
3556 ms
Pug
3414 ms
Pug
3039 ms
Pug
2402 ms
Pug
2831 ms
Pug
2121 ms
Pug
2255 ms
receive
1127 ms
Pug
1574 ms
jstag
115 ms
nexusdirectory.com accessibility score
nexusdirectory.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
nexusdirectory.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nexusdirectory.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 Nexusdirectory.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.
nexusdirectory.com
Open Graph description is not detected on the main page of Nexus Directory. 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: