3.8 sec in total
161 ms
3.4 sec
278 ms
Visit royalcapital.com now to see the best up-to-date Royal Capital content and also check out these interesting facts you probably never knew about royalcapital.com
Rick DuPuis, CFP®, President, Royal Capital Management LLC. Seeking to outperform the benchmark, and do it with less volatility. In the end you have my promise, next to you, no one will work harder or...
Visit royalcapital.comWe analyzed Royalcapital.com page load time and found that the first response time was 161 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
royalcapital.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value14.4 s
0/100
25%
Value5.5 s
54/100
10%
Value140 ms
95/100
30%
Value0.209
60/100
15%
Value9.9 s
27/100
10%
161 ms
196 ms
2134 ms
220 ms
476 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Royalcapital.com, 87% (40 requests) were made to Royalcapitalmanagement.com and 7% (3 requests) were made to Advicenter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Royalcapitalmanagement.com.
Page size can be reduced by 183.8 kB (62%)
296.0 kB
112.2 kB
In fact, the total size of Royalcapital.com main page is 296.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. 20% of websites need less resources to load. Javascripts take 187.8 kB which makes up the majority of the site volume.
Potential reduce by 24.9 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 24.9 kB or 57% of the original size.
Potential reduce by 8.1 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, Royal Capital needs image optimization as it can save up to 8.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.8 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 139.8 kB or 74% of the original size.
Potential reduce by 11.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. Royalcapital.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 77% of the original size.
Number of requests can be reduced by 32 (80%)
40
8
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royal Capital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
royalcapital.com
161 ms
www.royalcapitalmanagement.com
196 ms
royalcapitalmanagement.aspx
2134 ms
MyFormsValidate.js
220 ms
jquery-1.2.6.min.js
476 ms
suckerfish.js
150 ms
featuredcontentglider.js
225 ms
jquery_cookie_js.js
232 ms
jquery.lightbox.js
298 ms
jquery.dimensions.js
292 ms
jquery.validate.js
447 ms
cmxforms.js
309 ms
chili-1.7.pack.js
325 ms
jquery.easing.js
364 ms
jquery.accordion.js
372 ms
jquery.simplemodal-1.2.3.js
459 ms
feedreader.js
394 ms
thickbox.js
508 ms
AC_RunActiveContent.js
443 ms
misc.asp
966 ms
suckerfish.css
154 ms
thickbox.css
458 ms
featuredcontentglider.css
152 ms
jquery.lightbox.css
224 ms
T22right.css
463 ms
T22top.css
472 ms
T22left.css
572 ms
T22blank.css
545 ms
style.css
528 ms
flowplayer-3.1.4.min.js
396 ms
T22buttonhome.gif
413 ms
T22buttoncontactus.gif
467 ms
T22buttonplanning.gif
478 ms
T22buttonarticles.gif
486 ms
T22labelaboutus.gif
502 ms
T22labelotherresources.gif
511 ms
triad1011.jpg
542 ms
inverted%20logo%20border-250.jpg
569 ms
meter.asp
16 ms
T22bottom.css
533 ms
emblem-readonly.png
549 ms
meter.asp
14 ms
T22backgroundtopframe.JPG
173 ms
T22backgroundleftframe.JPG
143 ms
T22backgroundbottomframe.JPG
75 ms
loadingAnimation.gif
74 ms
royalcapital.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
royalcapital.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
royalcapital.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalcapital.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 Royalcapital.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
royalcapital.com
Open Graph description is not detected on the main page of Royal Capital. 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: