595 ms in total
56 ms
429 ms
110 ms
Click here to check amazing Build Princecraft content for Canada. Otherwise, check out these important facts you probably never knew about build.princecraft.com
Visit build.princecraft.comWe analyzed Build.princecraft.com page load time and found that the first response time was 56 ms and then it took 539 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
build.princecraft.com performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value8.1 s
2/100
25%
Value8.4 s
18/100
10%
Value890 ms
32/100
30%
Value0.248
50/100
15%
Value7.8 s
44/100
10%
56 ms
155 ms
48 ms
160 ms
75 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 50% of them (11 requests) were addressed to the original Build.princecraft.com, 14% (3 requests) were made to Princecraft.com and 14% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (160 ms) relates to the external source Princecraft.com.
Page size can be reduced by 52.6 kB (25%)
211.8 kB
159.3 kB
In fact, the total size of Build.princecraft.com main page is 211.8 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. Images take 116.3 kB which makes up the majority of the site volume.
Potential reduce by 17.0 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 17.0 kB or 76% of the original size.
Potential reduce by 3.6 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. Build Princecraft images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 44% of the original size.
Number of requests can be reduced by 5 (28%)
18
13
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Build Princecraft. 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 as a result speed up the page load time.
build.princecraft.com
56 ms
build.princecraft.com
155 ms
master
48 ms
hdr_logo.png
160 ms
logo_print.png
75 ms
jquery.min.js
32 ms
master
74 ms
homeJs
78 ms
conversion.js
14 ms
b_hi.jpg
125 ms
d_hi.jpg
125 ms
p_hi.jpg
125 ms
hdr_bg.jpg
94 ms
hdr_nav_sprite_2015.png
94 ms
sprite_breadcrumbs.png
55 ms
2431E5_0_0.woff
81 ms
fp.js
138 ms
69 ms
analytics.js
52 ms
collect
29 ms
collect
37 ms
40 ms
build.princecraft.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
<frame> or <iframe> elements do not have a title
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.
build.princecraft.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
General
Impact
Issue
Detected JavaScript libraries
build.princecraft.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Build.princecraft.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 Build.princecraft.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.
build.princecraft.com
Open Graph description is not detected on the main page of Build Princecraft. 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: