Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

tenable.io

Tenable Vulnerability Management | Tenable®

Page Load Speed

2.1 sec in total

First Response

10 ms

Resources Loaded

618 ms

Page Rendered

1.5 sec

tenable.io screenshot

About Website

Click here to check amazing Tenable content. Otherwise, check out these important facts you probably never knew about tenable.io

Upgrade your VM strategy with Tenable Vulnerability Management. Try it for free here to find out why Tenable is different from other tools in the market!

Visit tenable.io

Key Findings

We analyzed Tenable.io page load time and found that the first response time was 10 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

tenable.io performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value3,460 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.333

34/100

15%

TTI (Time to Interactive)

Value33.9 s

0/100

10%

Network Requests Diagram

tenable.io

10 ms

tenable.io

16 ms

tenable-io

76 ms

vulnerability-management

51 ms

css_6UZpxGormf10meHlAz1mqj0iFJ3hZh8udivyVgI2rNc.css

42 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tenable.io, 66% (40 requests) were made to Tenable.com and 10% (6 requests) were made to Play.vidyard.com. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Tenable.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 379.2 kB (15%)

Content Size

2.5 MB

After Optimization

2.1 MB

In fact, the total size of Tenable.io main page is 2.5 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 176.1 kB

  • Original 213.4 kB
  • After minification 191.9 kB
  • After compression 37.3 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 176.1 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 202.3 kB

  • Original 2.1 MB
  • After minification 1.9 MB

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. Tenable images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 207 B

  • Original 175.5 kB
  • After minification 175.5 kB
  • After compression 175.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-15%

Potential reduce by 541 B

  • Original 3.6 kB
  • After minification 3.6 kB
  • After compression 3.0 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. Tenable.io needs all CSS files to be minified and compressed as it can save up to 541 B or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

48

After Optimization

29

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

tenable.io accessibility score

75

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

tenable.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tenable.io SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tenable.io 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 Tenable.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.

Social Sharing Optimization

Open Graph data is detected on the main page of Tenable. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: