Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

thundra.io

Catchpoint Invests to Advance API, Cloud Functions, and Microservices Monitoring

Page Load Speed

1.6 sec in total

First Response

41 ms

Resources Loaded

1.4 sec

Page Rendered

165 ms

thundra.io screenshot

About Website

Welcome to thundra.io homepage info - get ready to check Thundra best content for India right away, or after learning these important things about thundra.io

Catchpoint® announced the acquisition of the assets of Thundra.io, a move that strengthens Catchpoint’s Application Experience Solution with advanced microservices and API monitoring capabilities.

Visit thundra.io

Key Findings

We analyzed Thundra.io page load time and found that the first response time was 41 ms and then it took 1.6 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.

Performance Metrics

thundra.io performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

thundra.io

41 ms

thundra.io

79 ms

catchpoint-invests-to-advance-api-cloud-functions-and-microservices-monitoring

37 ms

cp-2021.869d3490e.min.css

54 ms

webfont.js

53 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Thundra.io, 22% (19 requests) were made to Fonts.gstatic.com and 13% (11 requests) were made to Assets-global.website-files.com. The less responsive or slowest element that took the longest time to load (409 ms) relates to the external source Ws.zoominfo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.9 kB (21%)

Content Size

763.9 kB

After Optimization

602.0 kB

In fact, the total size of Thundra.io main page is 763.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. 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. Images take 334.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 96.7 kB

  • Original 137.8 kB
  • After minification 136.3 kB
  • After compression 41.1 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 96.7 kB or 70% of the original size.

Image Optimization

-17%

Potential reduce by 55.2 kB

  • Original 334.7 kB
  • After minification 279.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. Obviously, Thundra needs image optimization as it can save up to 55.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 10.0 kB

  • Original 238.3 kB
  • After minification 238.3 kB
  • After compression 228.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

-0%

Potential reduce by 0 B

  • Original 53.1 kB
  • After minification 53.1 kB
  • After compression 53.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. Thundra.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (81%)

Requests Now

63

After Optimization

12

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

Accessibility Review

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

thundra.io SEO score

79

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

robots.txt is not valid

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

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