3 sec in total
93 ms
2.6 sec
310 ms
Visit sourcekey.in now to see the best up-to-date Sourcekey content for India and also check out these interesting facts you probably never knew about sourcekey.in
B2B Portal – There are listing of global buyers and sellers, online business platform, b2b segment, global b2b segment, b2b organization, global sme segment, online traders, global marketplace
Visit sourcekey.inWe analyzed Sourcekey.in page load time and found that the first response time was 93 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
sourcekey.in performance score
93 ms
175 ms
13 ms
15 ms
84 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 35% of them (32 requests) were addressed to the original Sourcekey.in, 46% (42 requests) were made to B2b.sourcekey.in and 5% (5 requests) were made to Eprocurement.sourcekey.in. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Eprocurement.sourcekey.in.
Page size can be reduced by 371.6 kB (19%)
2.0 MB
1.6 MB
In fact, the total size of Sourcekey.in main page is 2.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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 73.2 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 12.6 kB, which is 15% 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 73.2 kB or 86% of the original size.
Potential reduce by 39.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. Sourcekey images are well optimized though.
Potential reduce by 75.4 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 75.4 kB or 52% of the original size.
Potential reduce by 183.7 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. Sourcekey.in needs all CSS files to be minified and compressed as it can save up to 183.7 kB or 83% of the original size.
Number of requests can be reduced by 23 (34%)
68
45
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sourcekey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sourcekey.in
93 ms
www.sourcekey.in
175 ms
ga.js
13 ms
bootstrap.min.css
15 ms
jquery.min.js
84 ms
bootstrap.min.js
12 ms
indexjs.js
59 ms
custom.css
112 ms
default.css
110 ms
nivo-slider.css
109 ms
jquery.min.js
53 ms
jquery.nivo.slider.js
109 ms
site.css
128 ms
jquery.bootstrap.newsbox.min.js
128 ms
jquery.mousewheel-3.1.12.js
129 ms
jquery.jcarousellite.js
129 ms
__utm.gif
11 ms
sdk.js
88 ms
buy-leads-new.php
651 ms
712355_1415616476.jpg
123 ms
logo.png
162 ms
close.jpg
66 ms
loading.gif
72 ms
banner1.jpg
286 ms
banner2.jpg
167 ms
banner3.jpg
171 ms
banner4.jpg
248 ms
banner5.jpg
261 ms
banner6.jpg
332 ms
banner7.jpg
275 ms
banner8.jpg
270 ms
banner9.jpg
334 ms
smelogo.png
313 ms
next.png
320 ms
prev.png
322 ms
tradealert.png
347 ms
f1.png
355 ms
t1.png
364 ms
google.png
365 ms
712733_1428319999.jpg
98 ms
712361_1415685130.jpg
94 ms
712357_1415619086.jpg
98 ms
712350_1415599360.jpg
109 ms
63310_1332564109.jpg
111 ms
712733_1428320215.jpg
121 ms
712351_1415611351.jpg
131 ms
712350_1415599498.jpg
149 ms
712355_1415616946.jpg
150 ms
712733_1428320174.jpg
165 ms
712354_1415615680.jpg
166 ms
712354_1415615635.jpg
177 ms
63310_1342002859.jpg
173 ms
712358_1415620152.jpg
190 ms
712351_1415611187.jpg
190 ms
712356_1415618157.jpg
222 ms
712356_1415617970.jpg
224 ms
712353_1415613678.jpg
218 ms
63309_1332562724.jpg
236 ms
63309_1332561789.jpg
231 ms
glyphicons-halflings-regular.woff
27 ms
118 ms
712355_1415616476.jpg
130 ms
xd_arbiter.php
42 ms
xd_arbiter.php
65 ms
712361_1415685130.jpg
88 ms
712357_1415619086.jpg
367 ms
712733_1428319999.jpg
174 ms
712350_1415599360.jpg
190 ms
63310_1332564109.jpg
151 ms
712733_1428320215.jpg
122 ms
712351_1415611351.jpg
149 ms
712350_1415599498.jpg
193 ms
712355_1415616946.jpg
284 ms
712733_1428320174.jpg
177 ms
712354_1415615680.jpg
165 ms
63310_1342002859.jpg
183 ms
712354_1415615635.jpg
199 ms
712358_1415620152.jpg
232 ms
712351_1415611187.jpg
258 ms
712353_1415613678.jpg
251 ms
712356_1415618157.jpg
213 ms
712356_1415617970.jpg
238 ms
63309_1332561789.jpg
266 ms
63309_1332562724.jpg
254 ms
template_homepage2.css
348 ms
template_homepage.js
1004 ms
ar.png
286 ms
icon_india.jpg
256 ms
arrows.png
67 ms
bullets.png
55 ms
like.php
65 ms
LVx-xkvaJ0b.png
37 ms
sourcekey.in SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sourcekey.in 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 Sourcekey.in main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
sourcekey.in
Open Graph description is not detected on the main page of Sourcekey. 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: