Tools & Wizards About Us
watsonanalytics.com screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

watsonanalytics.com

Pricing - IBM Cognos Analytics

Page Load Speed

3 sec in total

First Response

187 ms

Resources Loaded

2.6 sec

Page Rendered

186 ms

watsonanalytics.com screenshot

About Website

Welcome to watsonanalytics.com homepage info - get ready to check Watson Analytics best content for United States right away, or after learning these important things about watsonanalytics.com

Have questions about the different editions of IBM Cognos Analytics and their pricing? This easy-to-understand table breaks it all down.

Visit watsonanalytics.com

Key Findings

We analyzed Watsonanalytics.com page load time and found that the first response time was 187 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

watsonanalytics.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value6,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.515

15/100

15%

TTI (Time to Interactive)

Value31.9 s

0/100

10%

Network Requests Diagram

watsonanalytics.com

187 ms

pricing

1839 ms

ibm-common.js

143 ms

loader.js

227 ms

clientlib-idlStylesCarbon.lc-4bcd71d5119ddf067401538b806d7bbb-lc.min.css

41 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Watsonanalytics.com, 67% (37 requests) were made to 1.www.s81c.com and 20% (11 requests) were made to Ibm.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Ibm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 855.7 kB (65%)

Content Size

1.3 MB

After Optimization

452.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watsonanalytics.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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 81.2 kB

  • Original 90.2 kB
  • After minification 54.9 kB
  • After compression 9.0 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 35.2 kB, which is 39% 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 81.2 kB or 90% of the original size.

Image Optimization

-14%

Potential reduce by 15.7 kB

  • Original 114.0 kB
  • After minification 98.3 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. Obviously, Watson Analytics needs image optimization as it can save up to 15.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 757.2 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 338.7 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 757.2 kB or 69% of the original size.

CSS Optimization

-19%

Potential reduce by 1.6 kB

  • Original 8.4 kB
  • After minification 8.3 kB
  • After compression 6.8 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. Watsonanalytics.com needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (93%)

Requests Now

45

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watson Analytics. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

watsonanalytics.com

watsonanalytics.com

187 ms

pricing

pricing

1839 ms

ibm-common.js

ibm-common.js

143 ms

loader.js

loader.js

227 ms

clientlib-idlStylesCarbon.lc-4bcd71d5119ddf067401538b806d7bbb-lc.min.css

clientlib-idlStylesCarbon.lc-4bcd71d5119ddf067401538b806d7bbb-lc.min.css

41 ms

clientlib-idlStyles.lc-3f39c0cbd1ee640b47190aa213db9354-lc.min.css

clientlib-idlStyles.lc-3f39c0cbd1ee640b47190aa213db9354-lc.min.css

48 ms

plex.css

plex.css

145 ms

sans.css

sans.css

150 ms

masthead.min.js

masthead.min.js

147 ms

react.production.min.js

react.production.min.js

43 ms

react-dom.production.min.js

react-dom.production.min.js

56 ms

react-intl.min.js

react-intl.min.js

68 ms

main.a1b709bb.css

main.a1b709bb.css

343 ms

main.a3006a29.js

main.a3006a29.js

357 ms

clientlib-idlBundle.lc-fb47b8b531f83fcf850e1bf1b108d5b5-lc.min.js

clientlib-idlBundle.lc-fb47b8b531f83fcf850e1bf1b108d5b5-lc.min.js

40 ms

clientlib-target-antiflicker.lc-36a1efb28e947b5873f4a28c2cf9d5eb-lc.min.js

clientlib-target-antiflicker.lc-36a1efb28e947b5873f4a28c2cf9d5eb-lc.min.js

55 ms

clientlib-idlStyles.lc-cbcf977b1ac48999963b65f2ef61ae61-lc.min.js

clientlib-idlStyles.lc-cbcf977b1ac48999963b65f2ef61ae61-lc.min.js

39 ms

cm-app.min.js

cm-app.min.js

45 ms

tag.min.js

tag.min.js

143 ms

code-snippet.min.js

code-snippet.min.js

145 ms

content-block-card-static.min.js

content-block-card-static.min.js

145 ms

footer.min.js

footer.min.js

146 ms

leadspace.min.js

leadspace.min.js

146 ms

card-group.min.js

card-group.min.js

146 ms

text-cta.js

text-cta.js

147 ms

content-block.min.js

content-block.min.js

147 ms

link-list.min.js

link-list.min.js

149 ms

link-list-item-cta.js

link-list-item-cta.js

148 ms

table-of-contents.min.js

table-of-contents.min.js

148 ms

button-group.min.js

button-group.min.js

149 ms

content-item.min.js

content-item.min.js

148 ms

tag-group.min.js

tag-group.min.js

149 ms

content-section.min.js

content-section.min.js

150 ms

button-cta.js

button-cta.js

151 ms

content-group-heading.js

content-group-heading.js

153 ms

pricing-table.min.js

pricing-table.min.js

153 ms

lightbox-video-player.min.js

lightbox-video-player.min.js

154 ms

cta-block.min.js

cta-block.min.js

151 ms

video-cta-container.min.js

video-cta-container.min.js

153 ms

background-media.min.js

background-media.min.js

155 ms

paragraph.min.js

paragraph.min.js

156 ms

breadcrumb.min.js

breadcrumb.min.js

158 ms

star-rating.min.js

star-rating.min.js

168 ms

XV8HZRU

XV8HZRU

51 ms

sec-4-5.css

sec-4-5.css

40 ms

sec-cpt-4-5.js

sec-cpt-4-5.js

41 ms

leadspace

leadspace

273 ms

IBMPlexSans-Text.woff

IBMPlexSans-Text.woff

14 ms

IBMPlexSans-Regular.woff

IBMPlexSans-Regular.woff

15 ms

IBMPlexSans-Medium.woff

IBMPlexSans-Medium.woff

14 ms

IBMPlexSans-Light.woff

IBMPlexSans-Light.woff

15 ms

IBMPlexSans-ExtraLight.woff

IBMPlexSans-ExtraLight.woff

81 ms

IBMPlexSans-Thin.woff

IBMPlexSans-Thin.woff

81 ms

IBMPlexSans-SemiBold.woff

IBMPlexSans-SemiBold.woff

15 ms

IBMPlexSans-Bold.woff

IBMPlexSans-Bold.woff

15 ms

Accessibility Review

watsonanalytics.com accessibility score

76

Accessibility Issues

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

[role]s do not have all required [aria-*] attributes

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

watsonanalytics.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

watsonanalytics.com SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

watsonanalytics.com

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