1.4 sec in total
180 ms
1.1 sec
100 ms
Click here to check amazing Royalecastle content. Otherwise, check out these important facts you probably never knew about royalecastle.com
Grandfathered domains Google Apps Free, Legacy Free Google Apps, Domain Sale with Google Apps free
Visit royalecastle.comWe analyzed Royalecastle.com page load time and found that the first response time was 180 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
royalecastle.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.4 s
66/100
25%
Value3.2 s
92/100
10%
Value260 ms
83/100
30%
Value0.099
90/100
15%
Value4.0 s
88/100
10%
180 ms
208 ms
166 ms
220 ms
128 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Royalecastle.com, 18% (4 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (373 ms) relates to the external source Embed.tawk.to.
Page size can be reduced by 619.5 kB (77%)
801.6 kB
182.0 kB
In fact, the total size of Royalecastle.com main page is 801.6 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. 25% of websites need less resources to load. Javascripts take 558.2 kB which makes up the majority of the site volume.
Potential reduce by 3.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 3.1 kB or 65% of the original size.
Potential reduce by 413.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 413.5 kB or 74% of the original size.
Potential reduce by 203.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. Royalecastle.com needs all CSS files to be minified and compressed as it can save up to 203.0 kB or 85% of the original size.
Number of requests can be reduced by 15 (88%)
17
2
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royalecastle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
dfs.php
180 ms
bootstrap.min.css
208 ms
font-awesome.min.css
166 ms
animate.min.css
220 ms
owl.carousel.css
128 ms
owl.transitions.css
128 ms
prettyPhoto.css
222 ms
main.css
190 ms
jquery.js
346 ms
bootstrap.min.js
315 ms
mousescroll.js
266 ms
smoothscroll.js
270 ms
jquery.isotope.min.js
272 ms
jquery.inview.min.js
291 ms
wow.min.js
317 ms
main.js
332 ms
css
27 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
6 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
6 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
9 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
8 ms
default
373 ms
royalecastle.com accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
royalecastle.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
Page has valid source maps
royalecastle.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalecastle.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Royalecastle.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.
royalecastle.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: