9.7 sec in total
542 ms
8.6 sec
541 ms
Welcome to tharu.com homepage info - get ready to check Tharu best content for Sri Lanka right away, or after learning these important things about tharu.com
Visit tharu.comWe analyzed Tharu.com page load time and found that the first response time was 542 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tharu.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value5.6 s
18/100
25%
Value7.5 s
26/100
10%
Value10 ms
100/100
30%
Value0.005
100/100
15%
Value5.6 s
69/100
10%
542 ms
4117 ms
227 ms
672 ms
452 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 44% of them (57 requests) were addressed to the original Tharu.com, 9% (12 requests) were made to Scontent.xx.fbcdn.net and 8% (10 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Tharu.com.
Page size can be reduced by 830.6 kB (30%)
2.8 MB
2.0 MB
In fact, the total size of Tharu.com main page is 2.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 56.4 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 7.6 kB, which is 11% 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 56.4 kB or 81% of the original size.
Potential reduce by 102.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. Tharu images are well optimized though.
Potential reduce by 369.2 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 369.2 kB or 69% of the original size.
Potential reduce by 302.9 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. Tharu.com needs all CSS files to be minified and compressed as it can save up to 302.9 kB or 83% of the original size.
Number of requests can be reduced by 50 (41%)
123
73
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tharu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tharu.com
542 ms
www.tharu.com
4117 ms
style-4aa8de52.css
227 ms
jquery.min.js
672 ms
jquery.yiiactiveform.js
452 ms
copyrights.js
478 ms
jquery.slider.min.js
499 ms
Loading.js
499 ms
jquery.carousel.min.js
506 ms
jquery.capslide.js
701 ms
buttons.js
6 ms
jquery-ui.min.js
1433 ms
ga.js
51 ms
body-bg.jpg
482 ms
star-bg.png
1245 ms
header-bg.png
2825 ms
search-box-bg.png
1747 ms
where-fans-txt2.png
294 ms
loading.gif
447 ms
b9cf23a0dae77797370e17e1997faa56.jpg
2015 ms
mainbk.png
703 ms
b-home-323.png
930 ms
icon312.png
975 ms
orange-sample-32.png
1151 ms
icon422.png
1204 ms
smile11.png
1373 ms
e417_1.jpg
1459 ms
e416_1.jpg
1495 ms
e415_1.jpg
1598 ms
e418_1.jpg
1687 ms
e406_1.jpg
1745 ms
e292_1.jpg
1821 ms
e384_1.jpg
1938 ms
default.jpg
1993 ms
e457_1.png
1994 ms
e393_1.jpg
2055 ms
e147_1.jpg
2169 ms
join-bg.png
2239 ms
login-bg.png
2491 ms
FacebookPOD.jpg
2227 ms
e303_1.jpg
2265 ms
e259_1.jpg
2407 ms
e363_1.jpg
2449 ms
e278_1.jpg
2490 ms
e298_1.jpg
2487 ms
e382_1.jpg
2648 ms
e350_1.jpg
2671 ms
e217_1.jpg
2686 ms
gVuRRksHzos
87 ms
all.js
29 ms
__utm.gif
35 ms
191 ms
xd_arbiter.php
18 ms
xd_arbiter.php
43 ms
www-embed-player-vflfNyN_r.css
40 ms
www-embed-player.js
61 ms
base.js
86 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
47 ms
ad_status.js
53 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
45 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
e251_1.jpg
2448 ms
e294_1.jpg
2610 ms
featured-bg.png
2410 ms
feature-prev.png
2196 ms
ping
52 ms
getAllAppDefault.esi
59 ms
feature-next.png
2126 ms
getSegment.php
13 ms
checkOAuth.esi
23 ms
like_box.php
263 ms
t.dhj
8 ms
t.dhj
23 ms
cm
61 ms
x35248
118 ms
s-3271.xgi
16 ms
footer-bg.jpg
2066 ms
hbpix
40 ms
28 ms
27 ms
loading.gif
2098 ms
pixel
17 ms
xrefid.xgi
6 ms
pixel
14 ms
2981
27 ms
hDvwL1_H7g-.css
181 ms
56WNbrUYLbL.css
224 ms
q68gy-v_YMF.js
306 ms
FJmpeSpHpjS.js
379 ms
0wM5s1Khldu.js
302 ms
1bNoFZUdlYZ.js
303 ms
ui-bg_inset-soft_30_f58400_1x100.png
1976 ms
arrows.png
1922 ms
slider-list-icon.png
1919 ms
ui-icons_cccccc_256x240.png
1871 ms
314381_279686092072895_1045821631_n.jpg
229 ms
12744695_1563825247273153_3423744657812993506_n.jpg
266 ms
12348126_1907290472829960_7134432599871467591_n.jpg
310 ms
10802025_725575854200455_3066626663349407727_n.jpg
346 ms
11149418_830906900280014_1594054766150185913_n.jpg
351 ms
944078_891001167684082_298148163064212567_n.jpg
349 ms
10168137_1085765954819995_6002065193899745574_n.jpg
350 ms
12814022_227088290974153_7835815915228088484_n.jpg
404 ms
487486_420298791384910_944679179_n.jpg
418 ms
12208443_842542395854310_3292743403268903385_n.jpg
404 ms
22480_108492385827698_4501712_n.jpg
404 ms
1499572_186992904844513_2062559597_n.jpg
451 ms
wL6VQj7Ab77.png
45 ms
s7jcwEQH7Sx.png
46 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
28 ms
buttons.ab966a004186897711de4a5ed256c924.css
31 ms
plusone.js
75 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
17 ms
st.1188278743c14064d5e8ae56c8ada29c.js
27 ms
facebook_32.png
24 ms
twitter_32.png
23 ms
email_32.png
23 ms
linkedin_32.png
23 ms
wordpress_32.png
24 ms
blogger_32.png
24 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
86 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
8 ms
fastbutton
61 ms
postmessageRelay
48 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
17 ms
3193398744-postmessagerelay.js
37 ms
rpc:shindig_random.js
34 ms
cb=gapi.loaded_0
3 ms
tharu.com 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
tharu.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tharu.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tharu.com 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 Tharu.com 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.
tharu.com
Open Graph description is not detected on the main page of Tharu. 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: