6.6 sec in total
1.4 sec
5 sec
152 ms
Click here to check amazing 1 G M content for India. Otherwise, check out these important facts you probably never knew about 1g1m.in
Visit 1g1m.inWe analyzed 1g1m.in page load time and found that the first response time was 1.4 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
1g1m.in performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.6 s
61/100
25%
Value3.9 s
82/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value3.9 s
88/100
10%
1443 ms
261 ms
497 ms
748 ms
511 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 80% of them (45 requests) were addressed to the original 1g1m.in, 9% (5 requests) were made to Static.hupso.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain 1g1m.in.
Page size can be reduced by 417.0 kB (48%)
865.3 kB
448.3 kB
In fact, the total size of 1g1m.in main page is 865.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 396.6 kB which makes up the majority of the site volume.
Potential reduce by 25.5 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 25.5 kB or 81% of the original size.
Potential reduce by 13.3 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. 1 G M images are well optimized though.
Potential reduce by 279.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 279.4 kB or 70% of the original size.
Potential reduce by 98.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. 1g1m.in needs all CSS files to be minified and compressed as it can save up to 98.8 kB or 68% of the original size.
Number of requests can be reduced by 37 (70%)
53
16
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 G M. 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 from 12 to 1 for CSS and as a result speed up the page load time.
1g1m.in
1443 ms
style.css
261 ms
style.css
497 ms
dashicons.min.css
748 ms
twttrbootstrap.css
511 ms
jquery.fancybox-1.3.4.css
516 ms
font-awesome.css
12 ms
style.css
569 ms
css
45 ms
dynamic.php
666 ms
dynamic.php
887 ms
scrollGallery.css
802 ms
scrollGallery_noDesign.css
771 ms
jquery.js
1096 ms
jquery-migrate.min.js
921 ms
jquery.easing.min.js
998 ms
jquery.smoothscroll.js
1031 ms
html5shiv.js
1061 ms
modernizr.js
1134 ms
move.js
1178 ms
jquery.imagefit.js
1247 ms
jquery.scrollTo-1.4.3.1-min.js
1289 ms
jquery.serialScroll-1.2.2-min.js
1367 ms
jquery.mixitup.min.js
1382 ms
jquery.waitforimages.js
1384 ms
jquery.touchSwipe.min.js
1435 ms
jquery.masonry.js
1502 ms
jquery.fancybox-1.3.4.pack.js
1551 ms
jquery.mousewheel-3.0.4.pack.js
1627 ms
imgLiquid-min.js
1645 ms
js
56 ms
script.js
1635 ms
mootools-core-1.3.2-full-compat.js
1946 ms
scrollGallery.js
1754 ms
powertools-mobile-1.1.1.js
1811 ms
share_toolbar.js
220 ms
comment-reply.min.js
1885 ms
jquery-ui.min.js
34 ms
wp-embed.min.js
1882 ms
wp-emoji-release.min.js
1644 ms
share-medium.png
100 ms
gray.jpg
507 ms
Logo-Final-e1454068317520.png
266 ms
Home-Page-Pic-1.jpg
1537 ms
Nestle-Milk-Powder-249x187.png
764 ms
dhampure-sugar-249x187.jpg
253 ms
Dabur-Kewra-Water-249x187.jpg
253 ms
Aam-Papad-Meetha-249x187.jpg
503 ms
imageedit_1_7001681551.gif
505 ms
imageedit_1_8470649231.gif
529 ms
imageedit_1_3520454160.gif
753 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
21 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
21 ms
twitter.png
183 ms
facebook.png
189 ms
googleplus.png
193 ms
1g1m.in accessibility score
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
1g1m.in 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
Browser errors were logged to the console
1g1m.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1g1m.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 1g1m.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.
1g1m.in
Open Graph description is not detected on the main page of 1 G M. 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: