Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

tumbleweed.com

Secure File Transfer with SecureTransport | Axway

Page Load Speed

3.3 sec in total

First Response

426 ms

Resources Loaded

2.7 sec

Page Rendered

234 ms

tumbleweed.com screenshot

About Website

Welcome to tumbleweed.com homepage info - get ready to check Tumbleweed best content right away, or after learning these important things about tumbleweed.com

Axway's Secure Transport provides a secure file transfer option delivering scalability, reliability, and functionality while reducing costs and complexity.

Visit tumbleweed.com

Key Findings

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

Performance Metrics

tumbleweed.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

tumbleweed-products

426 ms

css_liv4p2IKIpTPOt54k7tFSyvHNMBW_VqR_-6NkRWTWE4.css

86 ms

inf5rvw.js

243 ms

js_0gj6QcpfRH2jzTbCQqf7kEkm4MXY0UA_sRhwPc8jC1o.js

109 ms

js_Pp6R7qANL_kpz3ldCYs8JY0nutQSO6P5RxEltLLJduY.js

103 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tumbleweed.com, 19% (10 requests) were made to D.adroll.com and 15% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Api.axway.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 490.8 kB (64%)

Content Size

764.0 kB

After Optimization

273.2 kB

In fact, the total size of Tumbleweed.com main page is 764.0 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. 40% of websites need less resources to load. Javascripts take 379.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 39.7 kB

  • Original 51.6 kB
  • After minification 49.7 kB
  • After compression 11.8 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 39.7 kB or 77% of the original size.

Image Optimization

-32%

Potential reduce by 34.1 kB

  • Original 106.9 kB
  • After minification 72.9 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, Tumbleweed needs image optimization as it can save up to 34.1 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 241.2 kB

  • Original 379.5 kB
  • After minification 253.9 kB
  • After compression 138.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 241.2 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 175.8 kB

  • Original 226.0 kB
  • After minification 222.5 kB
  • After compression 50.2 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. Tumbleweed.com needs all CSS files to be minified and compressed as it can save up to 175.8 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (76%)

Requests Now

37

After Optimization

9

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

Accessibility Review

tumbleweed.com accessibility score

93

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

Best Practices

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

Page has valid source maps

SEO Factors

tumbleweed.com SEO score

85

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

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 Tumbleweed.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 Tumbleweed.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 description is not detected on the main page of Tumbleweed. 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: