2 sec in total
296 ms
1.3 sec
334 ms
Welcome to discussions.tenable.com homepage info - get ready to check Discussions Tenable best content for United States right away, or after learning these important things about discussions.tenable.com
Visit discussions.tenable.comWe analyzed Discussions.tenable.com page load time and found that the first response time was 296 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
discussions.tenable.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value8.2 s
2/100
25%
Value5.2 s
59/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value6.2 s
62/100
10%
296 ms
237 ms
304 ms
173 ms
182 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 85% of them (23 requests) were addressed to the original Discussions.tenable.com, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (385 ms) belongs to the original domain Discussions.tenable.com.
Page size can be reduced by 744.2 kB (58%)
1.3 MB
541.7 kB
In fact, the total size of Discussions.tenable.com main page is 1.3 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. 25% of websites need less resources to load. CSS take 408.9 kB which makes up the majority of the site volume.
Potential reduce by 159.8 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 159.8 kB or 76% of the original size.
Potential reduce by 29.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. Discussions Tenable images are well optimized though.
Potential reduce by 220.8 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 220.8 kB or 67% of the original size.
Potential reduce by 334.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. Discussions.tenable.com needs all CSS files to be minified and compressed as it can save up to 334.1 kB or 82% of the original size.
Number of requests can be reduced by 8 (32%)
25
17
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discussions Tenable. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
welcome
296 ms
99403fd0804a69abf1164039b9ead7d0.js
237 ms
jive.css
304 ms
jive-icons.css
173 ms
jive-widgets.css
182 ms
1411659090786.css
177 ms
search.css
147 ms
08b4f895137503b337618b42f4d1a160.js
278 ms
0e6b4451bcff7dfb464a74018a7698ff.js
195 ms
3cefffa1ea889e96c186e156d7c787ae.js
385 ms
headerLogo-1407337904045-logo-200.png
104 ms
22.png
110 ms
22.png
108 ms
22.png
111 ms
22.png
109 ms
jive-avatar-disabled.png
115 ms
22.png
179 ms
22.png
180 ms
22.png
183 ms
powered_by_Jive.png
156 ms
j-ui-sprite.png
202 ms
jive-icon-sprites-sml.png
228 ms
jive-icon-sprites-med.png
285 ms
analytics.js
51 ms
collect
10 ms
collect
54 ms
ga-audiences
43 ms
discussions.tenable.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
discussions.tenable.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
discussions.tenable.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discussions.tenable.com 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), while the claimed language is English. Our system also found out that Discussions.tenable.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.
discussions.tenable.com
Open Graph description is not detected on the main page of Discussions Tenable. 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: