2.9 sec in total
37 ms
2.3 sec
653 ms
Visit discuss.io now to see the best up-to-date Discuss content for United States and also check out these interesting facts you probably never knew about discuss.io
Built to scale qualitative research with game-changing generative AI-powered insights, Discuss.io is home to the world's most loved market research tools.
Visit discuss.ioWe analyzed Discuss.io page load time and found that the first response time was 37 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
discuss.io performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value20.8 s
0/100
25%
Value21.3 s
0/100
10%
Value1,450 ms
15/100
30%
Value0.038
100/100
15%
Value28.4 s
0/100
10%
37 ms
18 ms
85 ms
37 ms
155 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 9% of them (9 requests) were addressed to the original Discuss.io, 81% (83 requests) were made to D2ja9mn5i96qhd.cloudfront.net and 6% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source D2ja9mn5i96qhd.cloudfront.net.
Page size can be reduced by 2.1 MB (39%)
5.4 MB
3.3 MB
In fact, the total size of Discuss.io main page is 5.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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 89.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 89.5 kB or 83% of the original size.
Potential reduce by 285.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. Discuss images are well optimized though.
Potential reduce by 713.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 713.0 kB or 73% of the original size.
Potential reduce by 1.0 MB
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. Discuss.io needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 88% of the original size.
Number of requests can be reduced by 72 (75%)
96
24
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discuss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
discuss.io
37 ms
www.discuss.io
18 ms
www.discuss.io
85 ms
wp-emoji-release.min.js
37 ms
dashicons.min.css
155 ms
jquery-ui-dialog.min.css
133 ms
styles.css
151 ms
tp_twitter_plugin.css
273 ms
settings.css
159 ms
teamshowcase-style.css
197 ms
slick.css
271 ms
testimonials-style.css
279 ms
slick.css
260 ms
style.css
306 ms
plugins.css
331 ms
skin.php
41 ms
custom.css
323 ms
style.css
341 ms
prettyPhoto.css
436 ms
animate.css
332 ms
js_composer.min.css
386 ms
font-awesome.min.css
67 ms
jquery.js
438 ms
jquery-migrate.min.js
436 ms
jquery.themepunch.tools.min.js
436 ms
jquery.themepunch.revolution.min.js
434 ms
slick.min.js
574 ms
team-showcase-popup.js
529 ms
slick.min.js
483 ms
jquery.easing.1.3.js
493 ms
css
95 ms
css
105 ms
css
118 ms
css
124 ms
prettyPhoto.min.css
492 ms
owl.min.css
484 ms
animate.min.css
550 ms
core.min.js
536 ms
widget.min.js
1437 ms
mouse.min.js
554 ms
resizable.min.js
589 ms
draggable.min.js
536 ms
button.min.js
643 ms
position.min.js
643 ms
dialog.min.js
641 ms
wpdialog.min.js
586 ms
jquery.form.min.js
598 ms
scripts.js
578 ms
jquery.tools.min.js
572 ms
jquery.validate.min.js
609 ms
drop-downs.js
530 ms
waypoints.js
464 ms
jquery.plugins.lib.js
456 ms
jquery.mb.YTPlayer.js
490 ms
jquery.flexslider.js
478 ms
css
19 ms
css
20 ms
owl.carousel.min.js
463 ms
jquery.prettyPhoto.js
447 ms
jquery.isotope.min.js
479 ms
sscr.min.js
469 ms
comment-reply.min.js
935 ms
slider.js
385 ms
main.js
385 ms
wp-embed.min.js
398 ms
js_composer_front.min.js
500 ms
jquery.prettyPhoto.min.js
392 ms
owl.carousel.min.js
401 ms
imagesloaded.pkgd.min.js
456 ms
underscore.min.js
427 ms
waypoints.min.js
433 ms
vc_grid.min.js
478 ms
vc-accordion.min.js
486 ms
vc-tta-autoplay.min.js
458 ms
vc-tabs.min.js
442 ms
waypoints.sticky.min.js
468 ms
logoDiscuss200px.png
432 ms
Screen-Shot-2016-02-16-at-11.04.28.png
512 ms
peoplegrid.jpg
540 ms
fa-globe_256_0_ffffff_none.png
429 ms
sprinter-e1455756235690.jpg
476 ms
support-e1455756315505.jpg
561 ms
recruiting.png
615 ms
discussion-rtcRoom.png
580 ms
sigmalogo-200x200.png
554 ms
logo_unilever-200x200.png
569 ms
futureadvisor-200x200.png
682 ms
brooke_rothman-200x200.jpg
620 ms
fontawesome-webfont.woff
3 ms
lynx.png
813 ms
logo-esomar_cropped.png
782 ms
world-map.png
780 ms
bullet-footer.png
635 ms
back-to-top.png
646 ms
revolution.extension.video.min.js
109 ms
revolution.extension.slideanims.min.js
118 ms
revolution.extension.layeranimation.min.js
120 ms
revolution.extension.navigation.min.js
119 ms
38qrarxl
39 ms
intercom.ff24bba5.js
87 ms
gridtile.png
126 ms
revicons.woff
101 ms
discuss.io 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
discuss.io 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
discuss.io SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discuss.io 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 Discuss.io 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.
discuss.io
Open Graph data is detected on the main page of Discuss. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: