3.2 sec in total
227 ms
1.8 sec
1.2 sec
Welcome to nehakakkar.in homepage info - get ready to check Nehakakkar best content for India right away, or after learning these important things about nehakakkar.in
Buy and Sell Domains with Dan.com. Discover millions of domain names available for sale. Dan.com keeps you safe.
Visit nehakakkar.inWe analyzed Nehakakkar.in page load time and found that the first response time was 227 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
nehakakkar.in performance score
227 ms
26 ms
125 ms
95 ms
94 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 40% of them (38 requests) were addressed to the original Nehakakkar.in, 39% (37 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Nehakakkar.in.
Page size can be reduced by 460.9 kB (19%)
2.5 MB
2.0 MB
In fact, the total size of Nehakakkar.in main page is 2.5 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.9 MB which makes up the majority of the site volume.
Potential reduce by 8.8 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 2.4 kB, which is 22% 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 8.8 kB or 81% of the original size.
Potential reduce by 58.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. Nehakakkar images are well optimized though.
Potential reduce by 169.9 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 169.9 kB or 64% of the original size.
Potential reduce by 223.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. Nehakakkar.in needs all CSS files to be minified and compressed as it can save up to 223.4 kB or 83% of the original size.
Number of requests can be reduced by 42 (46%)
91
49
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nehakakkar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
nehakakkar.in
227 ms
css
26 ms
nehakakkar.css
125 ms
skrollr.css
95 ms
colorbox.css
94 ms
index.html
118 ms
jquery.min.js
37 ms
skrollr.stylesheets.min.js
112 ms
skrollr.min.js
233 ms
jquery.colorbox-min.js
344 ms
nehakakkar.js
341 ms
loading.gif
340 ms
neha.png
376 ms
iamnehakakkar.png
371 ms
albums-title.png
375 ms
albums-1.jpg
521 ms
albums-2.jpg
727 ms
albums-3.jpg
725 ms
videos-title.png
469 ms
gallery-title.png
473 ms
th-1.jpg
724 ms
th-2.jpg
950 ms
th-3.jpg
949 ms
th-4.jpg
949 ms
th-5.jpg
1000 ms
th-6.jpg
1000 ms
th-7.jpg
1000 ms
th-8.jpg
1057 ms
social-title.png
1119 ms
likebox.php
305 ms
izEpCJdx7QA
317 ms
jquery-1.5.min.js
168 ms
jquery.carouFredSel-5.5.0.js
964 ms
1.jpg
1067 ms
2.jpg
1067 ms
3.jpg
1084 ms
4.jpg
1182 ms
5.jpg
1069 ms
6.jpg
1232 ms
sprite.png
1083 ms
down.png
1106 ms
lL2b34Z7dj7.css
75 ms
guHxiHaOfJH.css
79 ms
Czh0gDTFcBt.css
88 ms
OdWyTz8_-9A.css
123 ms
X9dDyMj4aHt.css
84 ms
YLftRg8N9Nf.css
108 ms
hDFRPrtWemz.css
132 ms
_rx8naC75Dy.js
148 ms
b94UUzHjapV.js
171 ms
0wM5s1Khldu.js
143 ms
TTCre3391I0.js
141 ms
njO1TPvGzoR.js
188 ms
b_6HNn_J2BZ.js
192 ms
6kb4qPGfoPa.js
197 ms
ezSeJz80WmZ.js
206 ms
B9x7unvN8Hn.js
191 ms
OCkothPJhqg.js
196 ms
D6JJJzT-tB6.js
196 ms
hQyBJD7FRta.js
249 ms
ThxFh2GztJe.js
243 ms
_UYztdBNTjs.js
248 ms
VpVLc1dkyZp.js
248 ms
DULOQLY-aiv.js
247 ms
-AWXRi4rrMJ.js
261 ms
3totTz2IHMG.js
246 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
131 ms
N9KSa305HxlY5zk6XisHxw.ttf
187 ms
www-embed-player-vflQrT_sR.css
545 ms
www-embed-player.js
649 ms
base.js
755 ms
12717786_1061736770516276_4073179473892871354_n.jpg
327 ms
12065656_994592060564081_8883398280668964966_n.jpg
333 ms
10934034_1069590676397552_8945583795507550991_n.jpg
372 ms
12672423_1069559689733984_473630640_n.jpg
365 ms
12672711_10153368812200911_974099939_n.jpg
366 ms
12594393_1068486846507935_1385839186_n.jpg
371 ms
12798840_1068476276508992_6134015117540015633_n.jpg
368 ms
HEyyDkPknAC.png
88 ms
wL6VQj7Ab77.png
88 ms
s7jcwEQH7Sx.png
88 ms
aeO1ik7i7-T.png
308 ms
QDwYpIaRyfG.png
86 ms
pimRBh7B6ER.png
86 ms
l5aPruN9xMM.png
89 ms
sOQnlBB68lt.png
89 ms
tIFXiEZJgab.js
158 ms
Fl1c2TVhCj-.png
60 ms
I6-MnjEovm5.js
67 ms
f6T91Deal_q.js
67 ms
1.png
377 ms
4.png
463 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
59 ms
ad_status.js
131 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
127 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
138 ms
nehakakkar.in SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nehakakkar.in 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 Nehakakkar.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.
nehakakkar.in
Open Graph description is not detected on the main page of Nehakakkar. 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: