2.2 sec in total
76 ms
1.4 sec
794 ms
Click here to check amazing Castle Inn content for United States. Otherwise, check out these important facts you probably never knew about castleinn.com
At our Anaheim hotel, you get the full castle experience while staying across the street from the happiest place on earth.
Visit castleinn.comWe analyzed Castleinn.com page load time and found that the first response time was 76 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 40% of websites can load faster.
castleinn.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value9.0 s
1/100
25%
Value6.3 s
42/100
10%
Value3,330 ms
2/100
30%
Value0.345
32/100
15%
Value12.7 s
13/100
10%
76 ms
68 ms
118 ms
28 ms
74 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 69% of them (27 requests) were addressed to the original Castleinn.com, 8% (3 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (397 ms) belongs to the original domain Castleinn.com.
Page size can be reduced by 174.2 kB (8%)
2.1 MB
1.9 MB
In fact, the total size of Castleinn.com main page is 2.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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 78.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 78.8 kB or 81% of the original size.
Potential reduce by 92.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. Castle Inn images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 119 B
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. Castleinn.com has all CSS files already compressed.
Number of requests can be reduced by 9 (28%)
32
23
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Castle Inn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
castleinn.com
76 ms
www.castleinn.com
68 ms
www.castleinn.com
118 ms
combined-home.css
28 ms
combined-home.js
74 ms
js
109 ms
font-awesome.min.css
50 ms
css
57 ms
combined.css
155 ms
combined.js
153 ms
visitorapi.js
250 ms
appmeasurement.js
250 ms
gen_204
203 ms
logo_even-smaller.png
104 ms
bg-parchment.png
243 ms
gnh-logo-1.png
131 ms
aaa-logo.png
102 ms
3297378_ImageLargeWidth.jpg
239 ms
bg-stone-wall.jpg
130 ms
bg-cta-shell.jpg
130 ms
poolside_CTA.jpg
240 ms
cta-icon-trumpet.png
166 ms
cta-03.jpg
167 ms
cta-icon-helmet.png
165 ms
ext_1cta.jpg
239 ms
cta-icon-knight-horse.png
169 ms
cta-01.jpg
237 ms
bg-map-legend.png
262 ms
bg-cta-foot.jpg
241 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
124 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mQ.ttf
16 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
16 ms
fontawesome-webfont.woff
49 ms
print.css
397 ms
3297390_ImageLargeWidth.jpg
191 ms
rd
24 ms
dest5.html
103 ms
id
110 ms
ibs:dpid=411&dpuuid=YzysGwAAAMUh1QNP
42 ms
castleinn.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
castleinn.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
castleinn.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Castleinn.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 Castleinn.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.
castleinn.com
Open Graph data is detected on the main page of Castle Inn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: