4.1 sec in total
1 sec
2.9 sec
209 ms
Click here to check amazing Thirst content. Otherwise, check out these important facts you probably never knew about thirst.co
Today we are extremely sad to announce that Thirst will be shutting down. We appreciate all the support and feedback we have received over the past months and years from our investors, advisors,...
Visit thirst.coWe analyzed Thirst.co page load time and found that the first response time was 1 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
thirst.co performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.4 s
39/100
25%
Value5.4 s
57/100
10%
Value170 ms
93/100
30%
Value0.012
100/100
15%
Value7.7 s
45/100
10%
1035 ms
532 ms
5 ms
47 ms
50 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thirst.co, 22% (17 requests) were made to Static.tumblr.com and 19% (15 requests) were made to A.disquscdn.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Thirst.co.
Page size can be reduced by 918.9 kB (64%)
1.4 MB
508.9 kB
In fact, the total size of Thirst.co main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.5 kB or 73% of the original size.
Potential reduce by 5.9 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. Thirst images are well optimized though.
Potential reduce by 849.0 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 849.0 kB or 67% of the original size.
Potential reduce by 37.6 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. Thirst.co needs all CSS files to be minified and compressed as it can save up to 37.6 kB or 81% of the original size.
Number of requests can be reduced by 49 (67%)
73
24
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thirst. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
thirst.co
1035 ms
thirst-is-shutting-down
532 ms
pre_tumblelog.js
5 ms
reset.css
47 ms
site.css
50 ms
jquery.fancybox-1.3.1.css
46 ms
tumblelog_post_message_queue.js
40 ms
stylesheet.css
40 ms
jquery-1.4.4.min.js
78 ms
plugins.js
75 ms
effector-1.2.6.min.js
71 ms
widgets.js
128 ms
plusone.js
111 ms
index.js
46 ms
avatar_f6e1d642ea8f_16.png
37 ms
embed.js
227 ms
avatar_6131f4ed1f3d_16.png
40 ms
search.png
8 ms
menu_icons.png
9 ms
tumblr_static_watercooler-header.png
189 ms
meta_icons.png
9 ms
share.png
35 ms
notes.png
38 ms
post_shadow.png
36 ms
icons_spr_black.png
36 ms
header_shadow.png
8 ms
topbar_bg.png
10 ms
photo_btns_med.png
11 ms
cb=gapi.loaded_0
96 ms
cb=gapi.loaded_1
125 ms
fastbutton
202 ms
ga.js
120 ms
impixu
252 ms
user_timeline.json
216 ms
get_num_replies.js
151 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
230 ms
impixu
173 ms
analytics.html
141 ms
login_check.html
37 ms
327 ms
loading.8023a7350e47171f7bb79707886cd7c5.css
82 ms
stat.gif
806 ms
__utm.gif
91 ms
postmessageRelay
121 ms
cb=gapi.loaded_0
37 ms
cb=gapi.loaded_1
29 ms
rapid-3.36.js
48 ms
rapidworker-1.2.js
52 ms
loader-bg.173909e4737a7481df14d5492b5eeb48.png
32 ms
ga.js
73 ms
analytics.js
72 ms
cs.js
139 ms
yql
319 ms
3193398744-postmessagerelay.js
118 ms
rpc:shindig_random.js
43 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
83 ms
__utm.gif
43 ms
cb=gapi.loaded_0
7 ms
grlryt2bdKIyfMSOhzd1eA.woff
37 ms
lounge.load.85ba7336856f5be9db0e468752c2dad5.js
14 ms
lounge.f668c82e65f78693a6a62a5c7d3e54b8.css
16 ms
config.js
9 ms
common.bundle.9054241a18d1ec2777a52f6dcc96dfb6.js
43 ms
lounge.bundle.b75817c8b9cd25c332ba61b6a5c58c0d.js
40 ms
jot
158 ms
loader.5cc23909da9c4a9874500d7a85c4125f.gif
40 ms
discovery.449c10a436c997c3eee5afd5021da3a2.css
17 ms
147 ms
sprite.06bad3144429d24544aa8b00ffd77160.png
70 ms
icons.dcb5405f8abc9a80e5628869f735eaf0.woff
66 ms
discovery.bundle.188b7afdc0cb75bb665bca3eb0ce9ba7.js
92 ms
noavatar92.4549c5353ccf103d32a8b81a856576ed.png
71 ms
noavatar92.png
72 ms
__utm.gif
33 ms
avatar92.jpg
21 ms
__utm.gif
18 ms
avatar92.jpg
14 ms
cedexis.radar.js
5 ms
thirst.co 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.
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
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
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.
thirst.co 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
thirst.co 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thirst.co 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 Thirst.co 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.
thirst.co
Open Graph data is detected on the main page of Thirst. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: