Tools & Wizards About Us
tumbleweedroyalty.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

tumbleweedroyalty.com

Tumbleweed Royalty | Mineral Royalty Acquisition West Texas

Page Load Speed

2.4 sec in total

First Response

184 ms

Resources Loaded

1.5 sec

Page Rendered

669 ms

tumbleweedroyalty.com screenshot

About Website

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

We focus on mineral, royalty and overriding royalty acquisitions in the Permian Basin in West Texas. In its short existence, Tumbleweed has purchased over $250MM of minerals and royalties in the Permi...

Visit tumbleweedroyalty.com

Key Findings

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

Performance Metrics

tumbleweedroyalty.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

76/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

tumbleweedroyalty.com

184 ms

www.tumbleweedroyalty.com

187 ms

icon

37 ms

styles.v-1.0.min.css

75 ms

main.v-1.1031202418139.js

209 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 76% of them (22 requests) were addressed to the original Tumbleweedroyalty.com, 14% (4 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tumbleweedroyalty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.4 kB (2%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tumbleweedroyalty.com main page is 1.1 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.5 kB

  • Original 11.9 kB
  • After minification 10.9 kB
  • After compression 3.4 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 8.5 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 250 B

  • Original 1.1 MB
  • After minification 1.1 MB

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. Tumbleweed Royalty images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 11.3 kB

  • Original 47.3 kB
  • After minification 47.3 kB
  • After compression 36.0 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 11.3 kB or 24% of the original size.

CSS Optimization

-27%

Potential reduce by 3.3 kB

  • Original 12.3 kB
  • After minification 12.3 kB
  • After compression 9.0 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. Tumbleweedroyalty.com needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (17%)

Requests Now

24

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tumbleweedroyalty.com

tumbleweedroyalty.com

184 ms

www.tumbleweedroyalty.com

www.tumbleweedroyalty.com

187 ms

icon

icon

37 ms

styles.v-1.0.min.css

styles.v-1.0.min.css

75 ms

main.v-1.1031202418139.js

main.v-1.1031202418139.js

209 ms

tumbleweed.v1.svg

tumbleweed.v1.svg

152 ms

tumbleweed-circle.v1.svg

tumbleweed-circle.v1.svg

165 ms

tumbleweed.v1.jpg

tumbleweed.v1.jpg

485 ms

tumbleweed.v2.jpg

tumbleweed.v2.jpg

589 ms

map-rev.v1.jpg

map-rev.v1.jpg

143 ms

Grant-Wright.v2.jpg

Grant-Wright.v2.jpg

219 ms

blake-carpenter.v2.jpg

blake-carpenter.v2.jpg

222 ms

ben-faith.v2.jpg

ben-faith.v2.jpg

255 ms

Mason-Kruse.v2.jpg

Mason-Kruse.v2.jpg

280 ms

slant.v1.jpg

slant.v1.jpg

284 ms

analytics.js

analytics.js

18 ms

bg-xwide.v2.jpg

bg-xwide.v2.jpg

1064 ms

btn-arrow-right.v1.png

btn-arrow-right.v1.png

437 ms

bg.v1.jpg

bg.v1.jpg

888 ms

BellGothicStd-Bold.woff

BellGothicStd-Bold.woff

494 ms

collect

collect

16 ms

constantine-webfont.woff

constantine-webfont.woff

470 ms

BellGothicStd-Black.woff

BellGothicStd-Black.woff

536 ms

font

font

28 ms

js

js

77 ms

promise.min.js

promise.min.js

740 ms

fetch.min.js

fetch.min.js

556 ms

collect

collect

3 ms

collect

collect

4 ms

Accessibility Review

tumbleweedroyalty.com accessibility score

94

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

High

Page has valid source maps

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tumbleweedroyalty.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tumbleweedroyalty.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

tumbleweedroyalty.com

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