2.7 sec in total
23 ms
2.1 sec
527 ms
Welcome to capleroyalty.com homepage info - get ready to check Caple Royalty best content right away, or after learning these important things about capleroyalty.com
Caple Royalty Services offers advice and negotiation services for Oil and Gas Royalty Owners, ensuring that you receive True Market Prices.
Visit capleroyalty.comWe analyzed Capleroyalty.com page load time and found that the first response time was 23 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
capleroyalty.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value6.9 s
6/100
25%
Value6.5 s
38/100
10%
Value1,160 ms
21/100
30%
Value0.209
59/100
15%
Value10.3 s
25/100
10%
23 ms
316 ms
28 ms
33 ms
309 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 57% of them (60 requests) were addressed to the original Capleroyalty.com, 30% (32 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (776 ms) belongs to the original domain Capleroyalty.com.
Page size can be reduced by 80.7 kB (11%)
728.8 kB
648.0 kB
In fact, the total size of Capleroyalty.com main page is 728.8 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. Only a small number of websites need less resources to load. Javascripts take 335.9 kB which makes up the majority of the site volume.
Potential reduce by 71.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 71.2 kB or 81% of the original size.
Potential reduce by 187 B
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. Caple Royalty images are well optimized though.
Potential reduce by 5.5 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.
Potential reduce by 3.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. Capleroyalty.com has all CSS files already compressed.
Number of requests can be reduced by 54 (77%)
70
16
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caple 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 36 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
capleroyalty.com
23 ms
capleroyalty.com
316 ms
style.min.css
28 ms
style.css
33 ms
mediaelementplayer-legacy.min.css
309 ms
wp-mediaelement.min.css
322 ms
style.css
37 ms
font-awesome.min.css
37 ms
style.min.css
40 ms
style.css
42 ms
dripicons.css
50 ms
kiko-all.css
51 ms
font-awesome-5.min.css
56 ms
stylesheet.min.css
83 ms
print.css
65 ms
style_dynamic.css
65 ms
responsive.min.css
70 ms
style_dynamic_responsive.css
80 ms
js_composer.min.css
138 ms
css
78 ms
core-dashboard.min.css
134 ms
script.js
155 ms
jquery.min.js
154 ms
jquery-migrate.min.js
154 ms
jquery.js
157 ms
js
156 ms
js
165 ms
doubletaptogo.js
154 ms
modernizr.min.js
469 ms
jquery.appear.js
155 ms
hoverIntent.min.js
156 ms
jquery.prettyPhoto.js
156 ms
mediaelement-and-player.min.js
157 ms
mediaelement-migrate.min.js
158 ms
wp-mediaelement.min.js
158 ms
jquery.waitforimages.js
159 ms
jquery.form.min.js
159 ms
waypoints.min.js
160 ms
jquery.easing.1.3.js
160 ms
jquery.mousewheel.min.js
160 ms
jquery.isotope.min.js
588 ms
skrollr.js
566 ms
default_dynamic.js
140 ms
default.min.js
142 ms
comment-reply.min.js
152 ms
js_composer_front.min.js
556 ms
jquery.flexslider-min.js
274 ms
jquery.touchSwipe.min.js
409 ms
jquery.fitvids.js
407 ms
qode-like.min.js
410 ms
gtm.js
246 ms
fbevents.js
246 ms
eiRGkzYSr2E
396 ms
caple-logo-small.png.webp
212 ms
slide3.jpg.webp
605 ms
slide2.jpg.webp
606 ms
slide4.jpg.webp
607 ms
slide1.jpg.webp
608 ms
slide3-mobile.jpg.webp
212 ms
slide2-mobile.jpg.webp
302 ms
slide4-mobile-1.jpg.webp
605 ms
slide1-mobile.jpg.webp
303 ms
informative-articles.jpg.webp
304 ms
listen.jpg.webp
305 ms
white-caple-icon.png
352 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
367 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf
365 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
370 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
370 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
368 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
369 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
443 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
442 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
445 ms
KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf
444 ms
KFOkCnqEu92Fr1Mu51xIIzc.ttf
445 ms
KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf
445 ms
KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf
446 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
445 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
483 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
483 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
447 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
448 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
483 ms
fontawesome-webfont.woff
776 ms
u-4l0qyriQwlOrhSvowK_l5-eR7lXff4jvk.ttf
483 ms
u-4m0qyriQwlOrhSvowK_l5-eRZOf-c.ttf
486 ms
u-4l0qyriQwlOrhSvowK_l5-eR71Wvf4jvk.ttf
486 ms
u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf
486 ms
u-440qyriQwlOrhSvowK_l5-fCZJ.ttf
485 ms
u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf
543 ms
u-4n0qyriQwlOrhSvowK_l52_wFZWMf_.ttf
543 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf
547 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJQ.ttf
545 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDrMfJQ.ttf
545 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJQ.ttf
545 ms
www-player.css
225 ms
www-embed-player.js
301 ms
base.js
405 ms
ad_status.js
250 ms
GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js
234 ms
embed.js
76 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
113 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
116 ms
id
100 ms
capleroyalty.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
capleroyalty.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
capleroyalty.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capleroyalty.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 Capleroyalty.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.
capleroyalty.com
Open Graph data is detected on the main page of Caple Royalty. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: