Tools & Wizards About Us
console.thundra.io screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

console.thundra.io

Debug & Troubleshoot your Cloud Applications - Thundra

Page Load Speed

2 sec in total

First Response

136 ms

Resources Loaded

1.7 sec

Page Rendered

191 ms

console.thundra.io screenshot

About Website

Visit console.thundra.io now to see the best up-to-date Console Thundra content for India and also check out these interesting facts you probably never knew about console.thundra.io

Debug and troubleshoot your apps with Thundra, a must-have developer tool for developing, testing, and maintaining high-performing cloud applications.

Visit console.thundra.io

Key Findings

We analyzed Console.thundra.io page load time and found that the first response time was 136 ms and then it took 1.9 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

console.thundra.io performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value19.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.5 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value3,920 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value27.9 s

0/100

10%

Network Requests Diagram

console.thundra.io

136 ms

apm.thundra.io

35 ms

css2

34 ms

css

48 ms

2.dd766d92.chunk.css

638 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Console.thundra.io, 20% (5 requests) were made to Apm.thundra.io and 12% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (913 ms) relates to the external source Apm.thundra.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.6 kB (1%)

Content Size

580.9 kB

After Optimization

575.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Console.thundra.io main page is 580.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. CSS take 527.9 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 5.4 kB

  • Original 9.7 kB
  • After minification 9.7 kB
  • After compression 4.2 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 5.4 kB or 56% of the original size.

JavaScript Optimization

-0%

Potential reduce by 142 B

  • Original 43.4 kB
  • After minification 43.4 kB
  • After compression 43.2 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

-0%

Potential reduce by 0 B

  • Original 527.9 kB
  • After minification 527.9 kB
  • After compression 527.9 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. Console.thundra.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (61%)

Requests Now

23

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

console.thundra.io

console.thundra.io

136 ms

apm.thundra.io

apm.thundra.io

35 ms

css2

css2

34 ms

css

css

48 ms

2.dd766d92.chunk.css

2.dd766d92.chunk.css

638 ms

main.91bcb645.chunk.css

main.91bcb645.chunk.css

578 ms

2.53114e9c.chunk.js

2.53114e9c.chunk.js

913 ms

main.488750dc.chunk.js

main.488750dc.chunk.js

732 ms

gtm.js

gtm.js

63 ms

optimize.js

optimize.js

74 ms

analytics.js

analytics.js

98 ms

uwt.js

uwt.js

90 ms

insight.min.js

insight.min.js

301 ms

conversion_async.js

conversion_async.js

85 ms

js

js

80 ms

collect

collect

174 ms

320 ms

adsct

adsct

233 ms

adsct

adsct

228 ms

collect

collect

79 ms

ga-audiences

ga-audiences

174 ms

css

css

75 ms

41 ms

26 ms

shim.latest.js

shim.latest.js

52 ms

Accessibility Review

console.thundra.io accessibility score

91

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

Best Practices

console.thundra.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

console.thundra.io SEO score

77

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

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

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

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 Console.thundra.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 Console.thundra.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

console.thundra.io

Open Graph description is not detected on the main page of Console Thundra. 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: