Tools & Wizards About Us
greetz.be screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

greetz.be

Greetz: kaarten, bloemen, ballonnen & andere verrassingen bezorgen

Page Load Speed

4.4 sec in total

First Response

315 ms

Resources Loaded

3.7 sec

Page Rendered

413 ms

greetz.be screenshot

About Website

Click here to check amazing Greetz content for Belgium. Otherwise, check out these important facts you probably never knew about greetz.be

Met Greetz zeg je het op jouw manier. Welke verrassing je ook kiest, je maakt het altijd uniek & persoonlijk. Voor 22:00 uur besteld, de volgende dag bezorgd. Bekijk ons uitgebreide assortiment verras...

Visit greetz.be

Key Findings

We analyzed Greetz.be page load time and found that the first response time was 315 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

greetz.be performance score

0

Network Requests Diagram

greetz.be

315 ms

home

592 ms

lib.min.js

777 ms

style.min.css

620 ms

style.min.css

527 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 26% of them (21 requests) were addressed to the original Greetz.be, 44% (36 requests) were made to Assets.greetz.nl and 6% (5 requests) were made to Static.greetz.be. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Nl.sitestat.com.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

665.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greetz.be main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 792.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 52.2 kB

  • Original 63.3 kB
  • After minification 55.5 kB
  • After compression 11.1 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 7.8 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 52.2 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 4.0 kB

  • Original 414.7 kB
  • After minification 410.7 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. Greetz images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 581.0 kB

  • Original 792.6 kB
  • After minification 737.7 kB
  • After compression 211.6 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 581.0 kB or 73% of the original size.

CSS Optimization

-91%

Potential reduce by 341.6 kB

  • Original 373.9 kB
  • After minification 373.7 kB
  • After compression 32.2 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. Greetz.be needs all CSS files to be minified and compressed as it can save up to 341.6 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (41%)

Requests Now

70

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greetz.be

greetz.be

315 ms

home

home

592 ms

lib.min.js

lib.min.js

777 ms

style.min.css

style.min.css

620 ms

style.min.css

style.min.css

527 ms

greetz.util.js

greetz.util.js

85 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

253 ms

jquery-migrate-1.1.1.min.js

jquery-migrate-1.1.1.min.js

256 ms

async-tracking.js

async-tracking.js

340 ms

validate-tracking.js

validate-tracking.js

365 ms

merged-hippo-1458082800000_86.css

merged-hippo-1458082800000_86.css

563 ms

merged-1458082800000_86.js

merged-1458082800000_86.js

457 ms

merged-wicketlibs-1458082800000_86.js

merged-wicketlibs-1458082800000_86.js

468 ms

conversion.js

conversion.js

29 ms

content.min.js

content.min.js

519 ms

js_visitor_settings.php

js_visitor_settings.php

28 ms

greetz%3Afourc

greetz%3Afourc

314 ms

thuiswinkel-rank.svg

thuiswinkel-rank.svg

254 ms

greetz%3Afourc

greetz%3Afourc

489 ms

greetz%3Afourc

greetz%3Afourc

381 ms

greetz%3Afourc

greetz%3Afourc

380 ms

greetz%3Afourc

greetz%3Afourc

433 ms

greetz%3Afourc

greetz%3Afourc

392 ms

greetz%3Afourc

greetz%3Afourc

483 ms

greetz%3Afourc

greetz%3Afourc

565 ms

greetz%3Afourc

greetz%3Afourc

579 ms

greetz%3Asixc

greetz%3Asixc

565 ms

greetz%3Asixc

greetz%3Asixc

642 ms

v.gif

v.gif

21 ms

thuiswinkel-award.svg

thuiswinkel-award.svg

238 ms

footer-appstore.svg

footer-appstore.svg

249 ms

footer-android.svg

footer-android.svg

245 ms

footer-social01.svg

footer-social01.svg

340 ms

footer-social02.svg

footer-social02.svg

331 ms

footer-social03.svg

footer-social03.svg

334 ms

footer-social04.svg

footer-social04.svg

332 ms

footer-social05.svg

footer-social05.svg

436 ms

footer-social06.svg

footer-social06.svg

432 ms

footer-social07.svg

footer-social07.svg

436 ms

footer-thuiswinkel.png

footer-thuiswinkel.png

434 ms

footer-payments.png

footer-payments.png

433 ms

gtm.js

gtm.js

249 ms

border-gray.png

border-gray.png

244 ms

icon-basket_small.png

icon-basket_small.png

357 ms

search-bg.png

search-bg.png

414 ms

logo_new.png

logo_new.png

416 ms

IntroBook.woff

IntroBook.woff

505 ms

icons-common_desktop.woff

icons-common_desktop.woff

504 ms

icons-common.woff

icons-common.woff

505 ms

263 ms

menu-bg.jpg

menu-bg.jpg

489 ms

flyout-bg.png

flyout-bg.png

488 ms

menuitem_greetzblue.png

menuitem_greetzblue.png

486 ms

flyout_greetzblue.png

flyout_greetzblue.png

566 ms

line_forwardslash.png

line_forwardslash.png

566 ms

text-line.svg

text-line.svg

562 ms

border-gray.png

border-gray.png

573 ms

review-score.svg

review-score.svg

574 ms

review_score_stars.png

review_score_stars.png

574 ms

review-logo-new.svg

review-logo-new.svg

648 ms

footer.png

footer.png

1183 ms

footer-top.png

footer-top.png

828 ms

greetz%3Atwelvec

greetz%3Atwelvec

682 ms

dc.js

dc.js

135 ms

arrows.png

arrows.png

494 ms

IntroBold.woff

IntroBold.woff

499 ms

Lunchbox.woff

Lunchbox.woff

588 ms

LunchboxLight.woff

LunchboxLight.woff

569 ms

conversion_async.js

conversion_async.js

53 ms

hotjar-123604.js

hotjar-123604.js

195 ms

s

s

1318 ms

fbevents.js

fbevents.js

238 ms

103 ms

46 ms

68 ms

__utm.gif

__utm.gif

23 ms

26 ms

19 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

21 ms

96 ms

visit-data

visit-data

208 ms

s

s

267 ms

SEO Factors

greetz.be SEO score

0

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greetz.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Greetz.be main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

greetz.be

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