4.1 sec in total
150 ms
3.7 sec
318 ms
Welcome to nanoenergizer.in homepage info - get ready to check Nanoenergizer best content for India right away, or after learning these important things about nanoenergizer.in
Nanoenergizer,the power of the engine had increased and the noise significantly got reduced.The combination of Platinum coated ceramic nano powder has great advantage for engine restoration with endur...
Visit nanoenergizer.inWe analyzed Nanoenergizer.in page load time and found that the first response time was 150 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
nanoenergizer.in performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value3.2 s
71/100
25%
Value2.5 s
98/100
10%
Value140 ms
95/100
30%
Value0.227
55/100
15%
Value3.6 s
92/100
10%
150 ms
466 ms
84 ms
100 ms
88 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 39% of them (66 requests) were addressed to the original Nanoenergizer.in, 16% (27 requests) were made to Static.xx.fbcdn.net and 6% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.0 MB (33%)
3.0 MB
2.0 MB
In fact, the total size of Nanoenergizer.in main page is 3.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 39.9 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.5 kB, which is 11% 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 39.9 kB or 79% of the original size.
Potential reduce by 99.8 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. Nanoenergizer images are well optimized though.
Potential reduce by 516.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 516.3 kB or 68% of the original size.
Potential reduce by 344.5 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. Nanoenergizer.in needs all CSS files to be minified and compressed as it can save up to 344.5 kB or 83% of the original size.
Number of requests can be reduced by 73 (45%)
161
88
The browser has sent 161 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nanoenergizer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
nanoenergizer.in
150 ms
www.nanoenergizer.in
466 ms
style.css
84 ms
tooltipster.css
100 ms
index_pop_style.css
88 ms
media.css
98 ms
jquery.min.js
35 ms
navDock_1.2.min.js
93 ms
jquery.tooltipster.js
94 ms
jsMooTools.js
178 ms
js94bg88.js
135 ms
jquery-1.4.min.js
180 ms
jquery.speedometer.js
139 ms
jquery.jqcanvas-modified.js
146 ms
excanvas-modified.js
151 ms
jqueryslide.js
176 ms
jquery-1.10.2.min.js
5 ms
in.js
4 ms
global.css
114 ms
analytics.js
93 ms
bg-main.png
412 ms
logo.png
94 ms
close.png
52 ms
Rupee.jpg
54 ms
b1.png
50 ms
tanks.png
93 ms
btn_gif.gif
138 ms
layer3.png
411 ms
m1.png
155 ms
m10.png
160 ms
m2.png
160 ms
m9.png
168 ms
m3.png
256 ms
m8.png
255 ms
m4.png
255 ms
m7.png
256 ms
m5.png
285 ms
m6.png
285 ms
dl_brochure.png
327 ms
1.png
337 ms
2.png
408 ms
3.png
427 ms
arrow.png
335 ms
full_img.png
777 ms
a.png
425 ms
b.png
427 ms
c.png
427 ms
d.png
426 ms
e.png
496 ms
f.png
497 ms
g.png
495 ms
h.png
493 ms
i.png
493 ms
j.png
527 ms
k.png
527 ms
l.png
503 ms
collect
12 ms
cart.png
499 ms
menu_bg.png
486 ms
menu_moh.png
662 ms
widgets.js
114 ms
platform.js
146 ms
secureAnonymousFramework
139 ms
all.js
300 ms
facebook.png
616 ms
digifaw.ttf
622 ms
WebRupee.V2.0.ttf
556 ms
lXxJ4OSDll0
177 ms
OpenSans-Regular.ttf
890 ms
twitter.png
557 ms
googleplus.png
573 ms
likebox.php
608 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
165 ms
youtube.png
575 ms
cb=gapi.loaded_0
14 ms
cb=gapi.loaded_1
37 ms
page
461 ms
linkdein.png
521 ms
layer1.png
521 ms
layer2.png
523 ms
footer.png
791 ms
postmessageRelay
187 ms
www-embed-player-vflfNyN_r.css
125 ms
www-embed-player.js
149 ms
base.js
239 ms
syndication
139 ms
403411106200174592
369 ms
279 ms
xd_arbiter.php
306 ms
xd_arbiter.php
619 ms
3193398744-postmessagerelay.js
44 ms
rpc:shindig_random.js
61 ms
hDvwL1_H7g-.css
644 ms
56WNbrUYLbL.css
740 ms
yZ--Yu0PDbV.css
821 ms
GN27K_co9Wc.css
913 ms
QD6_ejUFoCN.css
975 ms
xxJgcoj8mOR.css
963 ms
q68gy-v_YMF.js
1024 ms
FJmpeSpHpjS.js
1056 ms
0wM5s1Khldu.js
910 ms
1bNoFZUdlYZ.js
971 ms
njO1TPvGzoR.js
960 ms
OloiM1PZafe.js
1074 ms
LTv6ZK-5zxz.js
1225 ms
1FCa-btixu2.js
1092 ms
Oagsvfb4VWi.js
1096 ms
pObvZSrFc_4.js
1091 ms
Kt4tkgSRvHH.js
1092 ms
H3EKDTObx05.js
1093 ms
eR-qA8bp1RM.js
1158 ms
1QuX41zDRrx.js
1161 ms
cb=gapi.loaded_0
136 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
396 ms
ad_status.js
445 ms
rs=AGLTcCPAX8LKrZaLueW3YbNkZxb4I97DVQ
71 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
126 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
170 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
309 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
436 ms
photo.jpg
557 ms
g.jpg
555 ms
proxy.jpg
472 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
76 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
134 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
279 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
279 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
278 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
198 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
124 ms
fUWXImGB_normal.jpeg
266 ms
B_4BLXJU0AAvc5Y.jpg:small
307 ms
B_4AwAxVEAAbM5_.jpg:small
373 ms
CE8OVM4VEAAO-xU.jpg:small
370 ms
CE8OVNXVIAAYxFH.jpg:small
455 ms
CE8N27qUEAEsW9O.jpg:small
371 ms
CE8N28eUUAAoPGH.jpg:small
368 ms
CE8N28qUUAAQgxY.jpg:small
370 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
121 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
160 ms
B_4BLXJU0AAvc5Y.jpg
283 ms
B_4AwAxVEAAbM5_.jpg
282 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
11 ms
proxy.jpg
4 ms
1911870_487544164707214_682493281_n.jpg
349 ms
safe_image.php
283 ms
1958199_487561788038785_1414743337_n.jpg
404 ms
1604823_969407546407056_7192889409618161792_n.jpg
472 ms
10354686_10150004552801856_220367501106153455_n.jpg
541 ms
12592395_571471223001627_6243207668592120290_n.jpg
538 ms
12079702_984801951542534_5578634607011276743_n.jpg
538 ms
1533931_482087688598482_4902449620864945967_n.jpg
545 ms
1379841_10150004552801901_469209496895221757_n.jpg
540 ms
11986475_769572866504341_6542018497336263620_n.jpg
540 ms
11062651_766492516812376_5295176033529912346_n.jpg
615 ms
wL6VQj7Ab77.png
148 ms
s7jcwEQH7Sx.png
145 ms
QDwYpIaRyfG.png
147 ms
K00K-UgnsKu.png
147 ms
gxbPuQdXIZP.png
70 ms
jot.html
31 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
72 ms
xdrpc.html
20 ms
profile
74 ms
css
48 ms
anonymoususerspace
11 ms
js
56 ms
css
84 ms
js
53 ms
2473a7b.png
77 ms
nanoenergizer.in 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.
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
<frame> or <iframe> elements do not have a title
nanoenergizer.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
nanoenergizer.in 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanoenergizer.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Nanoenergizer.in 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.
nanoenergizer.in
Open Graph description is not detected on the main page of Nanoenergizer. 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: