4.2 sec in total
317 ms
1.6 sec
2.3 sec
Click here to check amazing Community Disqus content for United States. Otherwise, check out these important facts you probably never knew about community.disqus.com
The official blog for Disqus news, tips, and updates.
Visit community.disqus.comWe analyzed Community.disqus.com page load time and found that the first response time was 317 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
community.disqus.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value7.9 s
3/100
25%
Value21.0 s
0/100
10%
Value1,510 ms
14/100
30%
Value0.069
96/100
15%
Value54.8 s
0/100
10%
317 ms
15 ms
45 ms
20 ms
36 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Community.disqus.com, 20% (24 requests) were made to O.twimg.com and 19% (23 requests) were made to Media.disquscdn.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source Media.disquscdn.com.
Page size can be reduced by 1.0 MB (16%)
6.2 MB
5.2 MB
In fact, the total size of Community.disqus.com main page is 6.2 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. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 75.6 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 14.1 kB, which is 13% 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 75.6 kB or 71% of the original size.
Potential reduce by 537.5 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. Community Disqus images are well optimized though.
Potential reduce by 354.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 354.4 kB or 63% of the original size.
Potential reduce by 35.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. Community.disqus.com needs all CSS files to be minified and compressed as it can save up to 35.9 kB or 83% of the original size.
Number of requests can be reduced by 41 (36%)
114
73
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Disqus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
community.disqus.com
317 ms
pre_tumblelog.js
15 ms
base.css
45 ms
tiptip.css
20 ms
jquery.min.js
36 ms
tiptip.js
174 ms
blog-2015-01-19.css
49 ms
tumblelog_post_message_queue.js
10 ms
stylesheet.css
9 ms
widgets.js
96 ms
index.js
16 ms
reset.css
23 ms
type.css
40 ms
facebox.css
41 ms
ga.js
200 ms
mixpanel-2.1.min.js
201 ms
prum.min.js
197 ms
widgets.js
198 ms
disqus-logo.png
195 ms
avatar_62b2062ae750_64.png
194 ms
avatar_08cc693c05a8_64.png
190 ms
count.js
295 ms
impixu
292 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
265 ms
tweet.2c548e167cf5bdb0bd941e41896f257d.js
302 ms
avatar_4127ed3d1d49_64.png
146 ms
kandric.png
871 ms
votes-kandric.png
148 ms
gmail-filters.png
247 ms
gmail-unread-labels.png
365 ms
microphone.jpg
318 ms
completed-disqus-profile.jpg
279 ms
empty-crowd.jpg
297 ms
featured-comment.jpg
282 ms
wrap-up.jpg
297 ms
bi-ignition2014.jpg
347 ms
add-comments.jpg
348 ms
JustPlainSomething.png
390 ms
snortblat-comment.png
362 ms
votes-just-plain-something.png
362 ms
nikki-styling-you.jpg
404 ms
La-Donna-Pietra.png
448 ms
votes-la-donna-pietra.png
406 ms
blogher2014.jpg
405 ms
icon-follow-twitter.png
178 ms
icon-follow-facebook.png
180 ms
icon-follow-rss.png
182 ms
impixu
146 ms
analytics.html
178 ms
proximanova-bold.woff
139 ms
proximanova-light.woff
139 ms
proximanova-reg.woff
139 ms
login_check.html
70 ms
__utm.gif
103 ms
87 ms
85 ms
avatar_bb0e89dd32a2_40.png
85 ms
iframe_logo.png
39 ms
count-data.js
106 ms
rapid-3.36.js
56 ms
rapidworker-1.2.js
59 ms
ga.js
71 ms
analytics.js
42 ms
cs.js
70 ms
yql
355 ms
syndication
128 ms
521087117120663554
235 ms
tweets.json
161 ms
syndication
125 ms
__utm.gif
35 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
54 ms
Mwh6z8iI_normal.jpeg
181 ms
lOhQFavT_normal.jpeg
201 ms
ePZeXEdV_normal.jpeg
204 ms
proxy.jpg
62 ms
1f355.png
61 ms
1f37a.png
77 ms
proxy.jpg
80 ms
proxy.jpg
76 ms
proxy.jpg
54 ms
proxy.jpg
58 ms
proxy.jpg
76 ms
proxy.jpg
68 ms
proxy.jpg
69 ms
proxy.jpg
78 ms
proxy.jpg
83 ms
proxy.jpg
132 ms
proxy.jpg
85 ms
proxy.jpg
82 ms
proxy.jpg
126 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
38 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
aXbiZ_IZ_normal.jpeg
129 ms
XBRdWMOS_normal.jpeg
148 ms
79urftAa_normal.jpg
153 ms
0GMmfXrC_normal.png
156 ms
-IYMX1pm_normal.png
161 ms
7PyjF8oy_normal.png
160 ms
af69f7089ebfabe3bb33129bf9d4d325_normal.png
159 ms
CcFbp_wW8AEyCWV.jpg:small
199 ms
CcAo15MXEAAlvV3.jpg:small
204 ms
Ca4ult9UMAAhYkk.jpg:small
236 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
41 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
50 ms
jot.html
44 ms
proxy.jpg
4 ms
proxy.jpg
15 ms
proxy.jpg
5 ms
proxy.jpg
6 ms
proxy.jpg
3 ms
proxy.jpg
5 ms
proxy.jpg
3 ms
proxy.jpg
4 ms
jot.html
32 ms
proxy.jpg
5 ms
cedexis.radar.js
10 ms
proxy.jpg
9 ms
community.disqus.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
community.disqus.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
Missing source maps for large first-party JavaScript
community.disqus.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.disqus.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 Community.disqus.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.
community.disqus.com
Open Graph data is detected on the main page of Community Disqus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: