2.4 sec in total
509 ms
1.8 sec
138 ms
Click here to check amazing Candyboxwiki content for United States. Otherwise, check out these important facts you probably never knew about candyboxwiki.com
Visit candyboxwiki.comWe analyzed Candyboxwiki.com page load time and found that the first response time was 509 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
candyboxwiki.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value18.6 s
0/100
25%
Value12.3 s
3/100
10%
Value2,330 ms
5/100
30%
Value0.227
55/100
15%
Value18.6 s
3/100
10%
509 ms
201 ms
295 ms
478 ms
7 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 39% of them (9 requests) were addressed to the original Candyboxwiki.com, 17% (4 requests) were made to Pagead2.googlesyndication.com and 17% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (509 ms) belongs to the original domain Candyboxwiki.com.
Page size can be reduced by 15.4 kB (11%)
141.8 kB
126.4 kB
In fact, the total size of Candyboxwiki.com main page is 141.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. 30% of websites need less resources to load. Images take 105.7 kB which makes up the majority of the site volume.
Potential reduce by 13.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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.0 kB or 70% of the original size.
Potential reduce by 2.2 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. Candyboxwiki images are well optimized though.
Potential reduce by 172 B
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.
Number of requests can be reduced by 8 (36%)
22
14
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Candyboxwiki. 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 as a result speed up the page load time.
Main_Page
509 ms
load.php
201 ms
load.php
295 ms
load.php
478 ms
adsbygoogle.js
7 ms
load.php
315 ms
search-ltr.png
60 ms
wiki.png
90 ms
cc-by-nc-sa.png
59 ms
poweredby_mediawiki_88x31.png
130 ms
ca-pub-4058971526014700.js
34 ms
zrt_lookup.html
99 ms
show_ads_impl.js
53 ms
ga.js
15 ms
__utm.gif
54 ms
ads
213 ms
osd.js
6 ms
4384389112204548863
33 ms
abg.js
35 ms
m_js_controller.js
50 ms
googlelogo_color_112x36dp.png
24 ms
s
17 ms
x_button_blue2.png
18 ms
candyboxwiki.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
candyboxwiki.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
candyboxwiki.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Candyboxwiki.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 Candyboxwiki.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.
candyboxwiki.com
Open Graph description is not detected on the main page of Candyboxwiki. 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: