7.2 sec in total
835 ms
5.4 sec
899 ms
Visit gtml.in now to see the best up-to-date Gtml content for India and also check out these interesting facts you probably never knew about gtml.in
Visit gtml.inWe analyzed Gtml.in page load time and found that the first response time was 835 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
gtml.in performance score
835 ms
861 ms
36 ms
1443 ms
532 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 84% of them (53 requests) were addressed to the original Gtml.in, 3% (2 requests) were made to Counter6.statcounterfree.com and 3% (2 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Gtml.in.
Page size can be reduced by 393.0 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of Gtml.in main page is 1.7 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 81.6 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 22.9 kB, which is 25% 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 81.6 kB or 90% of the original size.
Potential reduce by 62.7 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. Gtml images are well optimized though.
Potential reduce by 143.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 143.9 kB or 74% of the original size.
Potential reduce by 104.8 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. Gtml.in needs all CSS files to be minified and compressed as it can save up to 104.8 kB or 86% of the original size.
Number of requests can be reduced by 26 (43%)
60
34
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gtml. 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 8 to 1 for CSS and as a result speed up the page load time.
gtml.in
835 ms
Home_Index.aspx
861 ms
atrk.js
36 ms
jquery-1.8.2.min.js
1443 ms
common.js
532 ms
jquery.easing.1.3.js
578 ms
ddsmoothmenu.js
846 ms
jquery.flexslider.js
1299 ms
jquery.elastislide.js
810 ms
jquery.accordion.js
797 ms
light_box.js
1126 ms
style.css
1359 ms
orange.css
1090 ms
skeleton.css
1389 ms
layout.css
1369 ms
ddsmoothmenu.css
1402 ms
elastislide.css
1610 ms
home_flexslider.css
1618 ms
light_box.css
1636 ms
atrk.gif
21 ms
test.png
154 ms
counter.js
376 ms
drop.png
364 ms
logo.png
317 ms
banner1.jpg
1328 ms
banner3.jpg
1877 ms
banner4.jpg
1588 ms
nav_arrow.png
315 ms
safed-musli.png
1108 ms
Shilajit.png
595 ms
tagara.png
628 ms
shallaki.png
1109 ms
garcinia.png
1109 ms
banawa.png
1111 ms
caralluma.png
1201 ms
Sarpgandha.png
1230 ms
karela.png
1356 ms
tulasi.png
1487 ms
punarnava.png
1510 ms
manjishtha.png
1588 ms
Arjuna.png
1624 ms
amalaki.png
1769 ms
shatavari.png
1793 ms
hadjod.png
1907 ms
giloy.png
1915 ms
ashwagandha.png
1929 ms
brahmi.png
2049 ms
aloevera.png
2126 ms
gas-out.png
2198 ms
TRIPHLA.png
2235 ms
Product_Default.png
2250 ms
facebook.png
2257 ms
twitter.png
2309 ms
dribbble.png
2403 ms
rss.png
2568 ms
counter.php
363 ms
pointeur.gif
273 ms
external.min.js
272 ms
banner_left_btn.png
2475 ms
banner_right_btn.png
2490 ms
widget_v2.132.js
11 ms
avatar_simple_visitor.png
139 ms
aL63HcygAAVYuCCsAAA==
2 ms
gtml.in SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gtml.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), while the claimed language is English. Our system also found out that Gtml.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.
gtml.in
Open Graph description is not detected on the main page of Gtml. 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: