5.1 sec in total
437 ms
1.9 sec
2.8 sec
Visit castleville.com now to see the best up-to-date Castleville content and also check out these interesting facts you probably never knew about castleville.com
Looking for Multiplayer Games? Check out our selection of games & play! Including: √ Words with Friends √ FarmVille 3 √ Draw Something & more!"
Visit castleville.comWe analyzed Castleville.com page load time and found that the first response time was 437 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
castleville.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value16.6 s
0/100
25%
Value17.4 s
0/100
10%
Value14,200 ms
0/100
30%
Value0.352
31/100
15%
Value21.4 s
1/100
10%
437 ms
65 ms
103 ms
103 ms
111 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Castleville.com, 14% (17 requests) were made to S3.amazonaws.com and 11% (13 requests) were made to Castlevillelegend.files.wordpress.com. The less responsive or slowest element that took the longest time to load (776 ms) relates to the external source S3.amazonaws.com.
Page size can be reduced by 962.1 kB (18%)
5.5 MB
4.5 MB
In fact, the total size of Castleville.com main page is 5.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 128.5 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 128.5 kB or 85% of the original size.
Potential reduce by 252.5 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. Castleville images are well optimized though.
Potential reduce by 568.4 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 568.4 kB or 73% of the original size.
Potential reduce by 12.6 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. Castleville.com needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 62% of the original size.
Number of requests can be reduced by 57 (55%)
104
47
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Castleville. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
blog.castlevillelegends.com
437 ms
webfont.js
65 ms
103 ms
103 ms
111 ms
style.css
108 ms
s2.wp.com
107 ms
gprofiles.js
124 ms
wpgroho.js
104 ms
102 ms
119 ms
tiled-gallery.css
101 ms
121 ms
widgets.js
102 ms
119 ms
w.js
87 ms
lvl5oxz.js
320 ms
merriweather.css
19 ms
background.png
219 ms
NavBanner.png
395 ms
img1447805730008-cvltower1.jpg
393 ms
sdk.js
288 ms
master.html
173 ms
cropped-bannerart1.png
164 ms
dragons-den-1.jpg
437 ms
dragons-den-2.jpg
438 ms
dragons-den-3.jpg
438 ms
dragons-den-4.jpg
444 ms
promoart-friendsconnect.png
442 ms
1-11.jpg
451 ms
2-2.jpg
451 ms
3-3.jpg
473 ms
4-4.jpg
472 ms
side_extended_bg.png
399 ms
side_bg.png
474 ms
img1447806312168-cvltower2.jpg
241 ms
img1447806520364-cvltower4.jpg
239 ms
img1447806687081-cvltower3.jpg
362 ms
img1447806845739-cvltower5.jpg
361 ms
img1446643553074-Untitled.jpg
361 ms
img1446643628295-Untitled.jpg
391 ms
img1446643723965-Untitled.jpg
433 ms
img1446643762536-Untitled.jpg
436 ms
img1443011098846-be1.jpg
474 ms
img1443011123708-be2.jpg
470 ms
img1443011144313-be3.jpg
448 ms
img1443011174695-be4.jpg
776 ms
img1444172124073-FoF01.png
513 ms
img1444172233743-FoF02.png
646 ms
img1444172332130-FoF03.png
509 ms
img1444172411747-FoF04.png
519 ms
Genericons.svg
230 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
61 ms
Noticons.svg
159 ms
BaABdRAi2AAAA
60 ms
merriweather-bold-webfont.ttf
157 ms
merriweather-regular-webfont.ttf
355 ms
merriweather-light-webfont.ttf
353 ms
hovercard.css
140 ms
services.css
216 ms
count.json
362 ms
g.gif
198 ms
graph.facebook.com
202 ms
count.json
359 ms
graph.facebook.com
356 ms
count.json
355 ms
graph.facebook.com
428 ms
count.json
357 ms
graph.facebook.com
428 ms
count.json
349 ms
graph.facebook.com
426 ms
count.json
349 ms
graph.facebook.com
428 ms
count.json
424 ms
graph.facebook.com
425 ms
count.json
425 ms
graph.facebook.com
467 ms
count.json
420 ms
graph.facebook.com
471 ms
background.png
460 ms
jquery.js
176 ms
g.gif
174 ms
g.gif
176 ms
g.gif
181 ms
g.gif
181 ms
g.gif
300 ms
g.gif
300 ms
g.gif
302 ms
g.gif
300 ms
g.gif
337 ms
g.gif
336 ms
g.gif
339 ms
g.gif
339 ms
g.gif
339 ms
g.gif
339 ms
g.gif
372 ms
g.gif
372 ms
g.gif
375 ms
f
480 ms
g.gif
342 ms
g.gif
342 ms
g.gif
343 ms
cropped-bannerart1.png
355 ms
postmessage.js
52 ms
jed.js
85 ms
underscore.min.js
84 ms
285 ms
xd_arbiter.php
91 ms
xd_arbiter.php
123 ms
global-print.css
76 ms
jquery.wpcom-proxy-request.js
8 ms
25 ms
70 ms
likes-rest.js
31 ms
UCLW_U5MbhRmrQ3LPQ948eBMNJrr8AyIs2JE6XSdavwff55UMUMdeMI6MK6f5Mt.eot
33 ms
l0P2paY9cTcOXKZRB39jn3eGTfiU8HtyHhNiFjolJJtff5AUMUMdeMI6MK6f5gI.eot
84 ms
gELugsV2QWlIqrhlJ4WhmUF-kcP73jr_Mktsr7shgaCff5HUMUMdeMI6MK6f5Mb.eot
119 ms
_MwHPl85n2orR4pI24jzDwx48_Mnd5V3T7EJBozuj2Cff5PUMUMdeMI6MK6f5MS.eot
155 ms
batch
133 ms
castleville.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.
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
Form elements do not have associated labels
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.
castleville.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
castleville.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 Castleville.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 Castleville.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.
castleville.com
Open Graph data is detected on the main page of Castleville. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: