3.2 sec in total
42 ms
2.5 sec
647 ms
Visit 100year.in now to see the best up-to-date 100 Year content for India and also check out these interesting facts you probably never knew about 100year.in
Vridhgram : first hindi blog of the aged
Visit 100year.inWe analyzed 100year.in page load time and found that the first response time was 42 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
100year.in performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value14.3 s
0/100
25%
Value3.9 s
82/100
10%
Value240 ms
85/100
30%
Value0
100/100
15%
Value10.4 s
24/100
10%
42 ms
123 ms
38 ms
77 ms
132 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 100year.in, 6% (6 requests) were made to Tpc.googlesyndication.com and 5% (5 requests) were made to Blogger.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Indiblogger.in.
Page size can be reduced by 465.9 kB (56%)
837.7 kB
371.8 kB
In fact, the total size of 100year.in main page is 837.7 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. 65% of websites need less resources to load. Javascripts take 469.0 kB which makes up the majority of the site volume.
Potential reduce by 95.1 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 95.1 kB or 78% of the original size.
Potential reduce by 84.0 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. Obviously, 100 Year needs image optimization as it can save up to 84.0 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 286.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 286.9 kB or 61% of the original size.
Potential reduce by 6 B
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. 100year.in has all CSS files already compressed.
Number of requests can be reduced by 57 (62%)
92
35
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 100 Year. 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 as a result speed up the page load time.
100year.in
42 ms
www.100year.in
123 ms
webfont.js
38 ms
3375562265-css_bundle_v2.css
77 ms
authorization.css
132 ms
show_ads.js
7 ms
widget.js
59 ms
stblogger2.js
33 ms
indirank.php
1323 ms
counter_xhtml.js
35 ms
3731899860-widgets.js
108 ms
plusone.js
103 ms
css
42 ms
bird-2toned-blue-fade.png
203 ms
logo%2Bvridhgram%2B2.png
205 ms
icon18_wrench_allbkg.png
204 ms
ca-pub-6011417599978543.js
333 ms
zrt_lookup.html
581 ms
show_ads_impl.js
230 ms
get_custom_js
316 ms
pixel.png
177 ms
jquery-1.4.2.min.js
176 ms
taza%2Bpost.png
681 ms
budhapa1.png
657 ms
hamarivaniicon.GIF
654 ms
arrow_dropdown.gif
659 ms
icon_feed12.png
653 ms
subscribe-netvibes.png
657 ms
subscribe-yahoo.png
668 ms
Harminder%2BSingh%2Bblogadda%2Bbadge%2Bwin%2B15.png
362 ms
vridhgram.png
651 ms
kaki.png
663 ms
PeTTkHQKj5rUPVxkIGAoaw.ttf
233 ms
buttons.js
150 ms
ads
713 ms
osd.js
256 ms
ads
628 ms
show_widget
203 ms
tc.js
345 ms
vglnk.js
360 ms
ads
611 ms
102081253.jpg
150 ms
355393671.jpg
148 ms
42654566.jpg
150 ms
123027391.jpg
19 ms
104975499.jpg
21 ms
p
44 ms
pixel.gif
29 ms
pixel.gif
33 ms
v2
43 ms
dpx
7 ms
xrefid.xgi
6 ms
ca.png
184 ms
52154.gif
6 ms
m_js_controller.js
57 ms
abg.js
81 ms
googlelogo_color_112x36dp.png
129 ms
9056170878245390650
126 ms
imgad
77 ms
nessie_icon_tiamat_white.png
77 ms
s
66 ms
x_button_blue2.png
9 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
23 ms
s_top.png
19 ms
indirank_blue.png
501 ms
s_bottom.png
17 ms
t.php
69 ms
cb=gapi.loaded_0
23 ms
analytics.js
75 ms
ping
242 ms
sdk.js
90 ms
85 ms
getAllAppDefault.esi
155 ms
mapuid
102 ms
cb=gapi.loaded_1
62 ms
collect
40 ms
demconf.jpg
54 ms
209 ms
201 ms
xd_arbiter.php
187 ms
xd_arbiter.php
278 ms
getSegment.php
143 ms
checkOAuth.esi
126 ms
batch
78 ms
t.dhj
6 ms
t.dhj
17 ms
s-3271.xgi
32 ms
cm
60 ms
47154.gif
24 ms
hbpix
186 ms
7 ms
15 ms
px
13 ms
pixel
19 ms
2981
21 ms
pixel.gif
82 ms
100year.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
100year.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
100year.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
HI
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 100year.in can be misinterpreted by Google and other search engines. Our service has detected that Hindi 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 100year.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.
100year.in
Open Graph description is not detected on the main page of 100 Year. 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: