735 ms in total
29 ms
618 ms
88 ms
Welcome to indiecastle.net homepage info - get ready to check Indie Castle best content for United States right away, or after learning these important things about indiecastle.net
Visit indiecastle.netWe analyzed Indiecastle.net page load time and found that the first response time was 29 ms and then it took 706 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
indiecastle.net performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value6.5 s
9/100
25%
Value9.8 s
10/100
10%
Value1,050 ms
25/100
30%
Value0
100/100
15%
Value18.4 s
3/100
10%
29 ms
86 ms
39 ms
44 ms
59 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Indiecastle.net, 13% (5 requests) were made to Frog.wix.com and 5% (2 requests) were made to Indiecastleradio.wix.com. The less responsive or slowest element that took the longest time to load (294 ms) relates to the external source Static.parastorage.com.
Page size can be reduced by 2.1 MB (77%)
2.8 MB
636.4 kB
In fact, the total size of Indiecastle.net main page is 2.8 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. 75% 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. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 14.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 14.8 kB or 73% of the original size.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 5.8 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. Indiecastle.net needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.
Number of requests can be reduced by 27 (73%)
37
10
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indie Castle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
indiecastleradio
29 ms
bt
86 ms
require.min.js
39 ms
main-r.min.js
44 ms
viewer.css
59 ms
dynamicmodel
12 ms
7ed2e3_d8c3d15cba501af624f44f4d3ec4fe63_77.json.z
52 ms
7ed2e3_a2ddafa3756483d0e19e0560bab8a637_78.json.z
64 ms
ugc-viewer
62 ms
ugc-viewer
75 ms
bt
74 ms
skins.min.js
166 ms
components.min.js
109 ms
utils.min.js
155 ms
core.min.js
158 ms
react-with-addons.min.js
105 ms
lodash.min.js
35 ms
TweenMax.min.js
62 ms
layout.min.js
83 ms
tpa.min.js
294 ms
fonts.min.js
101 ms
animations.min.js
147 ms
swfobject.min.js
146 ms
mousetrap.min.js
147 ms
tweenEngine.min.js
146 ms
DrawSVGPlugin.min.js
150 ms
react-dom.min.js
149 ms
ScrollToPlugin.min.js
146 ms
widgets.min.js
147 ms
experiment.js
147 ms
render.min.js
286 ms
wixappsCore.min.js
285 ms
wixappsClassics.min.js
286 ms
wixappsBuilder.min.js
148 ms
zepto.min.js
147 ms
color.min.js
283 ms
react-dom-server.min.js
16 ms
bt
68 ms
indiecastle.net 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
Image elements do not have [alt] attributes
Links do not have a discernible name
indiecastle.net 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
indiecastle.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indiecastle.net 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 Indiecastle.net 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.
indiecastle.net
Open Graph description is not detected on the main page of Indie Castle. 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: