Tools & Wizards About Us

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

instana.com

IBM Instana Observability

Page Load Speed

743 ms in total

First Response

55 ms

Resources Loaded

616 ms

Page Rendered

72 ms

About Website

Visit instana.com now to see the best up-to-date Instana content for United States and also check out these interesting facts you probably never knew about instana.com

Harness the power of AI and automation to proactively solve issues across the application stack with IBM Instana Observability.

Visit instana.com

Key Findings

We analyzed Instana.com page load time and found that the first response time was 55 ms and then it took 688 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

instana.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.0 s

0/100

25%

SI (Speed Index)

Value18.8 s

0/100

10%

TBT (Total Blocking Time)

Value9,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value48.9 s

0/100

10%

Network Requests Diagram

instana.com

55 ms

instana

75 ms

ibm-common.js

56 ms

loader.js

217 ms

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

30 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Instana.com, 78% (46 requests) were made to 1.www.s81c.com and 19% (11 requests) were made to Ibm.com. The less responsive or slowest element that took the longest time to load (217 ms) relates to the external source Hybrid-cloud-widgets-production.s3.us.cloud-object-storage.appdomain.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (85%)

Content Size

3.4 MB

After Optimization

518.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Instana.com main page is 3.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. 75% 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. Javascripts take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 85.3 kB

  • Original 96.2 kB
  • After minification 83.2 kB
  • After compression 10.9 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 13.0 kB, which is 14% 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 85.3 kB or 89% of the original size.

JavaScript Optimization

-85%

Potential reduce by 2.8 MB

  • Original 3.3 MB
  • After minification 3.3 MB
  • After compression 500.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 2.8 MB or 85% of the original size.

CSS Optimization

-2%

Potential reduce by 172 B

  • Original 7.0 kB
  • After minification 7.0 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. Instana.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (96%)

Requests Now

48

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

instana.com accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

instana.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

Missing source maps for large first-party JavaScript

SEO Factors

instana.com SEO score

86

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

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