8.4 sec in total
1.3 sec
5.5 sec
1.6 sec
Welcome to candyblog.de homepage info - get ready to check Candyblog best content right away, or after learning these important things about candyblog.de
Visit candyblog.deWe analyzed Candyblog.de page load time and found that the first response time was 1.3 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
candyblog.de performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value16.4 s
0/100
25%
Value14.0 s
1/100
10%
Value2,150 ms
6/100
30%
Value0.09
92/100
15%
Value25.4 s
0/100
10%
1316 ms
481 ms
216 ms
216 ms
215 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 32% of them (43 requests) were addressed to the original Candyblog.de, 13% (18 requests) were made to Apis.google.com and 10% (13 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Candyblog.de.
Page size can be reduced by 1.1 MB (38%)
3.0 MB
1.9 MB
In fact, the total size of Candyblog.de main page is 3.0 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 74.2 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 74.2 kB or 83% of the original size.
Potential reduce by 56.1 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. Candyblog images are well optimized though.
Potential reduce by 604.2 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 604.2 kB or 69% of the original size.
Potential reduce by 409.9 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. Candyblog.de needs all CSS files to be minified and compressed as it can save up to 409.9 kB or 85% of the original size.
Number of requests can be reduced by 73 (58%)
125
52
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Candyblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.candyblog.de
1316 ms
style.css
481 ms
subscriptions.css
216 ms
responsive-slider.css
216 ms
styles.css
215 ms
widgets.css
507 ms
app.css
280 ms
css
26 ms
jquery.js
512 ms
jquery-migrate.min.js
314 ms
jquery.fitvids.js
308 ms
jquery.placeholder.min.js
366 ms
custom.js
401 ms
www.candyblog.de
943 ms
widgets.js
83 ms
responsive-slider.js
380 ms
jquery.form.min.js
419 ms
scripts.js
477 ms
devicepx-jetpack.js
9 ms
gprofiles.js
60 ms
wpgroho.js
482 ms
lib.core.js
488 ms
lib.view.js
714 ms
client.js
514 ms
client.js
572 ms
tag.item.js
576 ms
tag.ui.js
584 ms
handler.image.js
611 ms
e-201611.js
4 ms
e-201611.js
34 ms
wp-emoji-release.min.js
264 ms
all.js
132 ms
Candyblog_Logo.png
254 ms
menuicon.png
253 ms
header2.jpg
331 ms
religious_sweets.jpg
784 ms
simple-smile.png
252 ms
post-border.png
251 ms
Doritos.jpg
1760 ms
russia.jpg
1006 ms
maoam.jpg
550 ms
Knetmasse.jpg
716 ms
Japan_Kit_Kat.png
2360 ms
portugal.jpg
1002 ms
mikronesien.jpg
925 ms
search.png
1076 ms
sugafari1.jpg
1166 ms
top.png
1165 ms
plusone.js
301 ms
like.php
394 ms
like.php
461 ms
like.php
455 ms
like.php
452 ms
like.php
450 ms
like.php
440 ms
like.php
448 ms
like.php
613 ms
like.php
611 ms
like.php
607 ms
likebox.php
673 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
219 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
264 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
266 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
265 ms
g.gif
216 ms
hovercard.css
128 ms
services.css
152 ms
style.css
851 ms
css
120 ms
style.css
1122 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
336 ms
253 ms
xd_arbiter.php
140 ms
xd_arbiter.php
222 ms
SAHk8nPAa-8
195 ms
81688267
178 ms
cb=gapi.loaded_0
148 ms
cb=gapi.loaded_1
256 ms
fastbutton
274 ms
fastbutton
267 ms
fastbutton
322 ms
fastbutton
319 ms
fastbutton
317 ms
fastbutton
323 ms
fastbutton
542 ms
fastbutton
531 ms
fastbutton
613 ms
fastbutton
608 ms
TY3MhkXpWJ-.js
883 ms
LVx-xkvaJ0b.png
935 ms
www-embed-player-vflfNyN_r.css
298 ms
www-embed-player.js
668 ms
base.js
1083 ms
player.js
670 ms
player.css
552 ms
ga.js
542 ms
vuid.min.js
578 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
235 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
276 ms
postmessageRelay
803 ms
kyEKgjk51ZE.css
640 ms
xgj7bXhJNEH.css
656 ms
1kPfZUdGrka.js
691 ms
Yuj_Y8xNH2C.js
720 ms
Mpe38fuBVZ2.js
717 ms
n8qIhCw3vMx.js
752 ms
cb=gapi.loaded_0
432 ms
cb=gapi.loaded_1
434 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
731 ms
__utm.gif
262 ms
proxy.html
232 ms
457977248.jpg
540 ms
6434647_60x60.jpg
442 ms
417096_348910228486458_1409269170_n.jpg
290 ms
374286_305477066163108_1077537328_n.jpg
341 ms
10945731_790249951010900_4480537873162752300_n.jpg
372 ms
11012521_1683378758559282_7063804871724885926_n.jpg
370 ms
10998861_967971013233221_1647518510753613796_n.jpg
408 ms
1924037_960013224053749_6851500961073241571_n.jpg
373 ms
10366209_432741416894024_1389869819869964982_n.jpg
403 ms
wL6VQj7Ab77.png
218 ms
s7jcwEQH7Sx.png
216 ms
3193398744-postmessagerelay.js
264 ms
rpc:shindig_random.js
228 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
86 ms
ad_status.js
86 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
51 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
60 ms
cb=gapi.loaded_0
13 ms
jot.html
64 ms
VXcANLwwL5J.js
3 ms
AmlxWlqMvlv.js
6 ms
pinit.js
37 ms
ping
39 ms
candyblog.de 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
candyblog.de 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
Browser errors were logged to the console
candyblog.de SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Candyblog.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Candyblog.de 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.
candyblog.de
Open Graph description is not detected on the main page of Candyblog. 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: