Tools & Wizards About Us
vansteenlandt.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vansteenlandt.net

Doopsuiker Vansteenlandt – Uw speciaalzaak voor doopsuiker

Page Load Speed

8.7 sec in total

First Response

2.2 sec

Resources Loaded

6.4 sec

Page Rendered

164 ms

vansteenlandt.net screenshot

About Website

Welcome to vansteenlandt.net homepage info - get ready to check Vansteenlandt best content right away, or after learning these important things about vansteenlandt.net

Visit vansteenlandt.net

Key Findings

We analyzed Vansteenlandt.net page load time and found that the first response time was 2.2 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

vansteenlandt.net performance score

0

Network Requests Diagram

2218 ms

wp-emoji-release.min.js

388 ms

btsearch-style.css

202 ms

fontello.css

198 ms

light_style.css

201 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 81% of them (43 requests) were addressed to the original Vansteenlandt.net, 9% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Vansteenlandt.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.4 kB (60%)

Content Size

650.3 kB

After Optimization

262.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vansteenlandt.net main page is 650.3 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. 25% of websites need less resources to load. Javascripts take 265.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 19.2 kB

  • Original 25.6 kB
  • After minification 25.0 kB
  • After compression 6.3 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 19.2 kB or 75% of the original size.

Image Optimization

-13%

Potential reduce by 18.3 kB

  • Original 139.9 kB
  • After minification 121.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. Obviously, Vansteenlandt needs image optimization as it can save up to 18.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 179.4 kB

  • Original 265.8 kB
  • After minification 256.3 kB
  • After compression 86.4 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 179.4 kB or 68% of the original size.

CSS Optimization

-78%

Potential reduce by 170.4 kB

  • Original 219.1 kB
  • After minification 196.9 kB
  • After compression 48.7 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. Vansteenlandt.net needs all CSS files to be minified and compressed as it can save up to 170.4 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (70%)

Requests Now

47

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vansteenlandt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

2218 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

388 ms

btsearch-style.css

btsearch-style.css

202 ms

fontello.css

fontello.css

198 ms

light_style.css

light_style.css

201 ms

responsiveimgslider.css

responsiveimgslider.css

295 ms

woocommerce-layout.css

woocommerce-layout.css

583 ms

woocommerce.css

woocommerce.css

687 ms

prettyPhoto.css

prettyPhoto.css

498 ms

jquery.selectBox.css

jquery.selectBox.css

401 ms

style.css

style.css

680 ms

font-awesome.min.css

font-awesome.min.css

782 ms

css

css

62 ms

genericons.css

genericons.css

792 ms

style.css

style.css

1076 ms

vansteenlandt.net

vansteenlandt.net

1448 ms

jquery.js

jquery.js

1362 ms

jquery-migrate.min.js

jquery-migrate.min.js

907 ms

auto-complete.js

auto-complete.js

1009 ms

collapse.js

collapse.js

1107 ms

jquery.slides.min.js

jquery.slides.min.js

1205 ms

css

css

16 ms

css

css

27 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1208 ms

woocommerce.min.js

woocommerce.min.js

1116 ms

jquery.cookie.min.js

jquery.cookie.min.js

1211 ms

cart-fragments.min.js

cart-fragments.min.js

1334 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

1510 ms

jquery.prettyPhoto.init.min.js

jquery.prettyPhoto.init.min.js

1408 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

1593 ms

jquery.yith-wcwl.js

jquery.yith-wcwl.js

1500 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

1509 ms

functions.js

functions.js

1602 ms

wp-embed.min.js

wp-embed.min.js

1610 ms

XXX33401-e1450198631419.jpg

XXX33401-e1450198631419.jpg

598 ms

slide111-e1450185687338.jpg

slide111-e1450185687338.jpg

681 ms

cropped-065e84_1eed399160624486888d5a855db258471.jpg

cropped-065e84_1eed399160624486888d5a855db258471.jpg

694 ms

342_1pg0031-300x300.jpg

342_1pg0031-300x300.jpg

675 ms

adaptive-image_1-280-160_480-422-240_960-620-350_fit-origin_22511-300x300.jpg

adaptive-image_1-280-160_480-422-240_960-620-350_fit-origin_22511-300x300.jpg

607 ms

Thavorn_Wedding_Phuket_Romantic_Beachside1-300x300.jpg

Thavorn_Wedding_Phuket_Romantic_Beachside1-300x300.jpg

685 ms

IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff

IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff

27 ms

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

67 ms

RFda8w1V0eDZheqfcyQ4EBa1RVmPjeKy21_GQJaLlJI.woff

RFda8w1V0eDZheqfcyQ4EBa1RVmPjeKy21_GQJaLlJI.woff

81 ms

ZvcMqxEwPfh2qDWBPxn6nhGYIVA-f1n-gQW6IKoy_-M.woff

ZvcMqxEwPfh2qDWBPxn6nhGYIVA-f1n-gQW6IKoy_-M.woff

82 ms

ZvcMqxEwPfh2qDWBPxn6njPY4jw7fdqC-GX3uhj9onc.woff

ZvcMqxEwPfh2qDWBPxn6njPY4jw7fdqC-GX3uhj9onc.woff

81 ms

analytics.js

analytics.js

10 ms

collect

collect

17 ms

1461 ms

arrow-left.png

arrow-left.png

455 ms

arrow-right.png

arrow-right.png

457 ms

btns-next-prev.png

btns-next-prev.png

624 ms

pagination.png

pagination.png

630 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

201 ms

SEO Factors

vansteenlandt.net SEO score

0

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vansteenlandt.net can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Vansteenlandt.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.

Social Sharing Optimization

vansteenlandt.net

Open Graph description is not detected on the main page of Vansteenlandt. 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: