Analyze

candyblog.de: Candyblog | Entdecke die kuriose Welt der Süßigkeiten

Page load speed analysis

  • 47/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    1.3 sec

  • Resources loaded

    5.5 sec

  • Page rendered

    1.6 sec

  • Total page load time

    8.4 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

We 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.

Page optimization

  • HTML 89.8 kB
    Images 1.6 MB
    Javascripts 922.4 kB
    CSS 482.1 kB

    In fact, the total size of Candyblog.de main page is 3.1 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. 85% 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.

    • Original 89.8 kB
    • After minification 86.3 kB
    • After compression 15.7 kB

    HTML optimization

    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.

    • Original 1.6 MB
    • After optimization 1.5 MB

    Image optimization

    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.

    • Original 922.4 kB
    • After minification 844.8 kB
    • After compression 269.3 kB

    JavaScript optimization

    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 653.1 kB or 71% of the original size.

    • Original 482.1 kB
    • After minification 456.9 kB
    • After compression 72.2 kB

    CSS optimization

    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.

Network requests diagram

  • www.candyblog.de
  • style.css
  • subscriptions.css
  • responsive-slider.css
  • styles.css
  • widgets.css
  • app.css
  • css
  • jquery.js
  • jquery-migrate.min.js
  • jquery.fitvids.js
  • jquery.placeholder.min.js
  • custom.js
  • www.candyblog.de
  • widgets.js
  • responsive-slider.js
  • jquery.form.min.js
  • scripts.js
  • devicepx-jetpack.js
  • gprofiles.js
  • wpgroho.js
  • lib.core.js
  • lib.view.js
  • client.js
  • client.js
  • tag.item.js
  • tag.ui.js
  • handler.image.js
  • e-201611.js
  • e-201611.js
  • wp-emoji-release.min.js
  • all.js
  • Candyblog_Logo.png
  • menuicon.png
  • header2.jpg
  • religious_sweets.jpg
  • simple-smile.png
  • post-border.png
  • Doritos.jpg
  • russia.jpg
  • maoam.jpg
  • Knetmasse.jpg
  • Japan_Kit_Kat.png
  • portugal.jpg
  • mikronesien.jpg
  • search.png
  • sugafari1.jpg
  • top.png
  • plusone.js
  • like.php
  • like.php
  • like.php
  • like.php
  • like.php
  • like.php
  • like.php
  • like.php
  • like.php
  • like.php
  • likebox.php
  • cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
  • DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
  • k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
  • EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
  • g.gif
  • hovercard.css
  • services.css
  • style.css
  • css
  • style.css
  • button.0308b81ff1714e446f674b5b9793f2cd.js
  • xd_arbiter.php
  • xd_arbiter.php
  • SAHk8nPAa-8
  • 81688267
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • fastbutton
  • TY3MhkXpWJ-.js
  • LVx-xkvaJ0b.png
  • www-embed-player-vflfNyN_r.css
  • www-embed-player.js
  • base.js
  • player.js
  • player.css
  • ga.js
  • vuid.min.js
  • rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
  • tweet_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
  • postmessageRelay
  • kyEKgjk51ZE.css
  • xgj7bXhJNEH.css
  • 1kPfZUdGrka.js
  • Yuj_Y8xNH2C.js
  • Mpe38fuBVZ2.js
  • n8qIhCw3vMx.js
  • cb=gapi.loaded_0
  • cb=gapi.loaded_1
  • W5F8_SL0XFawnjxHGsZjJA.ttf
  • __utm.gif
  • proxy.html
  • 457977248.jpg
  • 6434647_60x60.jpg
  • 417096_348910228486458_1409269170_n.jpg
  • 374286_305477066163108_1077537328_n.jpg
  • 10945731_790249951010900_4480537873162752300_n.jpg
  • 11012521_1683378758559282_7063804871724885926_n.jpg
  • 10998861_967971013233221_1647518510753613796_n.jpg
  • 1924037_960013224053749_6851500961073241571_n.jpg
  • 10366209_432741416894024_1389869819869964982_n.jpg
  • wL6VQj7Ab77.png
  • s7jcwEQH7Sx.png
  • 3193398744-postmessagerelay.js
  • rpc:shindig_random.js
  • Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
  • ad_status.js
  • zN7GBFwfMP4uA6AR0HCoLQ.ttf
  • RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
  • cb=gapi.loaded_0
  • jot.html
  • VXcANLwwL5J.js
  • AmlxWlqMvlv.js
  • pinit.js
  • ping

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.

Additional info on candyblog.de

Requests

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.

46

Javascripts

31

Images

18

CSS

30

AJAX

125

All

Possible request optimization

1

Javascripts

20

Images

1

CSS

30

AJAX

73

Optimized

52

All

Normal result

IP address

Candyblog.de uses IP address which is currently shared with 3 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

candyblog.de

forever-aloe-hamburg.de

realness.de

rohde-christian.de

178.16.59.239

DNS records

Type Host Target/ip TTL Other
A

candyblog.de

178.16.59.239 3600
NS

candyblog.de

geons1.rturbo.de 3600
NS

candyblog.de

geons3.rturbo.de 3600
NS

candyblog.de

geons2.rturbo.de 3600
SOA

candyblog.de

3600 Mname: geons1.rturbo.de
Rname: hostmaster.candyblog.de
Serial: 956697984
Refresh: 7200
Retry: 1800
Expire: 604800
Minimum-ttl: 86400

Language and encoding

Good result

Language

DE de language flag

Detected

DE de language flag

Claimed

Encoding

UTF-8

Claimed

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.

HTTPS certificate

SSL Certificate

Candyblog.de has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Candyblog.de is located in Germany, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Poor result

Social Sharing Optimization

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:

candyblog.de

Share this report in social media

Analyze another website

Analyze