2.4 sec in total
269 ms
1.8 sec
325 ms
Click here to check amazing Jaffnahindu content for Sri Lanka. Otherwise, check out these important facts you probably never knew about jaffnahindu.org
Jaffna Hindu College Web Portal
Visit jaffnahindu.orgWe analyzed Jaffnahindu.org page load time and found that the first response time was 269 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
jaffnahindu.org performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
269 ms
354 ms
357 ms
354 ms
419 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 63% of them (71 requests) were addressed to the original Jaffnahindu.org, 13% (15 requests) were made to Scontent.xx.fbcdn.net and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (730 ms) belongs to the original domain Jaffnahindu.org.
Page size can be reduced by 538.0 kB (33%)
1.6 MB
1.1 MB
In fact, the total size of Jaffnahindu.org main page is 1.6 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 965.3 kB which makes up the majority of the site volume.
Potential reduce by 72.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. 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 72.2 kB or 84% of the original size.
Potential reduce by 48.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. Jaffnahindu images are well optimized though.
Potential reduce by 196.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 196.9 kB or 62% of the original size.
Potential reduce by 220.1 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. Jaffnahindu.org needs all CSS files to be minified and compressed as it can save up to 220.1 kB or 83% of the original size.
Number of requests can be reduced by 29 (27%)
109
80
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jaffnahindu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
jaffnahindu.org
269 ms
styles.css
354 ms
fade.js
357 ms
slider.css
354 ms
jquery-1.7.1.min.js
419 ms
slider.js
354 ms
all.js
29 ms
ga.js
30 ms
__utm.gif
97 ms
background.jpg
101 ms
page_shadow.png
98 ms
topbanner.jpg
101 ms
topbannerline.jpg
97 ms
topmenuline.gif
95 ms
Jaffna_Hindu_College_Principal_Iyampillai_Thayanandarajah.jpg
169 ms
loading.gif
164 ms
11.jpg
301 ms
10.jpg
375 ms
7.jpg
364 ms
8.jpg
427 ms
6.jpg
374 ms
5.jpg
376 ms
4.jpg
481 ms
3.jpg
482 ms
2.jpg
578 ms
9.jpg
643 ms
slider_arrows.png
511 ms
195.jpg
496 ms
1.png
499 ms
dot.gif
511 ms
194.jpg
551 ms
6.png
579 ms
193.jpg
646 ms
192.jpg
642 ms
2.png
645 ms
191.jpg
646 ms
9.png
650 ms
190.jpg
649 ms
4.png
649 ms
3.png
650 ms
172.jpg
688 ms
161.jpg
692 ms
arrow.png
715 ms
1.jpg
730 ms
83.jpg
671 ms
lLQA8L19X3Q
168 ms
180 ms
xd_arbiter.php
71 ms
xd_arbiter.php
126 ms
d7nQTGtdsqo
134 ms
80.jpg
630 ms
Jaffna.gif
663 ms
MjUk7robV08
120 ms
Colombo.gif
669 ms
USA.gif
693 ms
Canada.gif
693 ms
UK.gif
628 ms
Sydney.gif
634 ms
like_box.php
300 ms
www-embed-player-vflZsBgOl.css
58 ms
www-embed-player.js
84 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
48 ms
ad_status.js
43 ms
Melbourne.gif
463 ms
NewZealand.gif
457 ms
Switzerland.gif
485 ms
Norway.gif
485 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
107 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
107 ms
Germany.gif
491 ms
8.jpg
397 ms
7.jpg
409 ms
6.jpg
413 ms
jTuqQ-OPDr6.css
44 ms
n370yiaI2G6.css
51 ms
_rx8naC75Dy.js
70 ms
x5F9OMjKyLw.js
86 ms
ICDbTSzjQEg.js
85 ms
TTCre3391I0.js
84 ms
5.jpg
430 ms
4.jpg
426 ms
2.jpg
423 ms
1.jpg
433 ms
9.jpg
406 ms
12.jpg
386 ms
12670164_1065669720166389_5641577874385410863_n.jpg
75 ms
7.jpg
357 ms
17647_487523897980977_875999945_n.jpg
34 ms
12647363_125170844531665_2155435277987769938_n.jpg
38 ms
12745563_1509984425978192_794836749355373160_n.jpg
39 ms
1936392_560218297467511_1531067931576841945_n.jpg
40 ms
1927699_176695069352775_5827273518762641500_n.jpg
41 ms
10391841_150436145344164_754675212523439163_n.jpg
42 ms
12342493_596175277201796_5562429904306664202_n.jpg
43 ms
1622873_1421568361414539_184086436_n.jpg
47 ms
1935284_1676834869260929_7612516275741434570_n.jpg
45 ms
1915801_1513113005650839_8354169197717693911_n.jpg
44 ms
12743988_828360323953482_4159063270836762545_n.jpg
45 ms
10422467_522816624554824_3448182991178539384_n.jpg
46 ms
11905389_881836895205407_5734754615659397445_n.jpg
119 ms
12662432_813973112064612_1942654643071706737_n.jpg
50 ms
wL6VQj7Ab77.png
17 ms
s7jcwEQH7Sx.png
17 ms
11.jpg
350 ms
15.jpg
356 ms
13.jpg
365 ms
bottomline.gif
378 ms
twitter.png
383 ms
facebook.png
412 ms
youtube.png
439 ms
I6-MnjEovm5.js
8 ms
vlXaquuXMrr.js
10 ms
jaffnahindu.org 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
Document doesn't have a <title> element
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
jaffnahindu.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
jaffnahindu.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jaffnahindu.org 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Jaffnahindu.org 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.
jaffnahindu.org
Open Graph description is not detected on the main page of Jaffnahindu. 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: