Tools & Wizards About Us
visplanner.be screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

visplanner.be

Visserslatijn, de hengelsportsite voor Nederland en België.

Page Load Speed

5.3 sec in total

First Response

399 ms

Resources Loaded

4.3 sec

Page Rendered

506 ms

visplanner.be screenshot

About Website

Visit visplanner.be now to see the best up-to-date Visplanner content and also check out these interesting facts you probably never knew about visplanner.be

Visserslatijn Nederland de hengelsportsite voor Nederland en België. Met hengelsportnieuws, tips, het Nationaal HengelSportForum en veel informatie.

Visit visplanner.be

Key Findings

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

Performance Metrics

visplanner.be performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

visplanner.be

399 ms

www.visserslatijn.nl

1243 ms

style.css

257 ms

mobile.css

171 ms

formidablepro.css

261 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Visplanner.be, 54% (66 requests) were made to Visserslatijn.nl and 10% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Visserslatijn.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.8 kB (16%)

Content Size

3.9 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Visplanner.be main page is 3.9 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. 70% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 68.3 kB

  • Original 86.5 kB
  • After minification 82.7 kB
  • After compression 18.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 68.3 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 147.2 kB

  • Original 3.3 MB
  • After minification 3.1 MB

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. Visplanner images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 277.7 kB

  • Original 420.1 kB
  • After minification 378.4 kB
  • After compression 142.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 277.7 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 124.6 kB

  • Original 147.6 kB
  • After minification 132.4 kB
  • After compression 23.0 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. Visplanner.be needs all CSS files to be minified and compressed as it can save up to 124.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (51%)

Requests Now

117

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

visplanner.be

visplanner.be

399 ms

www.visserslatijn.nl

www.visserslatijn.nl

1243 ms

style.css

style.css

257 ms

mobile.css

mobile.css

171 ms

formidablepro.css

formidablepro.css

261 ms

diggdigg-style.css

diggdigg-style.css

174 ms

meteor-slides.css

meteor-slides.css

172 ms

twitter-feed.css

twitter-feed.css

249 ms

wp-cat-list-theme.css

wp-cat-list-theme.css

254 ms

jquery.js

jquery.js

548 ms

jquery-migrate.min.js

jquery-migrate.min.js

263 ms

jquery.form.min.js

jquery.form.min.js

331 ms

slide.js

slide.js

337 ms

jquery.adrotate.clicktracker.js

jquery.adrotate.clicktracker.js

337 ms

ai.js

ai.js

423 ms

jquery.cycle.all.js

jquery.cycle.all.js

434 ms

jquery.metadata.v2.js

jquery.metadata.v2.js

414 ms

jquery.touchwipe.1.1.1.js

jquery.touchwipe.1.1.1.js

418 ms

slideshow.js

slideshow.js

420 ms

cufon-yui.js

cufon-yui.js

426 ms

SerpentineDBol_400-SerpentineDBol_italic_400.font.js

SerpentineDBol_400-SerpentineDBol_italic_400.font.js

603 ms

tw-sack.min.js

tw-sack.min.js

432 ms

highslide.min.css

highslide.min.css

435 ms

style.css

style.css

446 ms

vbulletin_lt.css

vbulletin_lt.css

526 ms

vbulletin_lt.js.php

vbulletin_lt.js.php

980 ms

all.js

all.js

11 ms

misc.php

misc.php

468 ms

highslide.min.js

highslide.min.js

546 ms

smoothscroll.js

smoothscroll.js

469 ms

comment-reply.min.js

comment-reply.min.js

508 ms

cookieControl-6.2.min.js

cookieControl-6.2.min.js

558 ms

css

css

32 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

419 ms

1c230a20e0d195f2a3df887dad49972a

1c230a20e0d195f2a3df887dad49972a

77 ms

5d8bd6fc4cd1799315d43807b8232677

5d8bd6fc4cd1799315d43807b8232677

78 ms

378f54ecc974535a21c417bdd7ab006a

378f54ecc974535a21c417bdd7ab006a

112 ms

110 ms

tab_b.png

tab_b.png

118 ms

tab_l.png

tab_l.png

130 ms

tab_m.png

tab_m.png

113 ms

bt_open.png

bt_open.png

114 ms

bt_close.png

bt_close.png

129 ms

tab_r.png

tab_r.png

129 ms

logo.gif

logo.gif

510 ms

VLheader15.png

VLheader15.png

1085 ms

VLheader14.png

VLheader14.png

1060 ms

VLheader13.png

VLheader13.png

1136 ms

VLheader12.png

VLheader12.png

1158 ms

VLheader11.png

VLheader11.png

911 ms

VLheader1.png

VLheader1.png

1261 ms

VLheader9.png

VLheader9.png

1266 ms

VLheader3.png

VLheader3.png

1397 ms

VLheader7.png

VLheader7.png

1430 ms

VLheader6.png

VLheader6.png

1388 ms

nofishing-300x225.png

nofishing-300x225.png

1326 ms

ajax-loader.gif

ajax-loader.gif

1341 ms

snoek_ow.jpg

snoek_ow.jpg

1351 ms

ad150aa006.gif

ad150aa006.gif

1427 ms

dot.png

dot.png

1430 ms

rss.gif

rss.gif

1487 ms

wpspin_light.gif

wpspin_light.gif

1487 ms

check.png

check.png

1488 ms

logo_atworx.png

logo_atworx.png

1534 ms

logo_eligere.png

logo_eligere.png

1534 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

55 ms

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

55 ms

429 ms

bg_home_fotos.png

bg_home_fotos.png

1413 ms

date.png

date.png

1424 ms

xd_arbiter.php

xd_arbiter.php

75 ms

xd_arbiter.php

xd_arbiter.php

355 ms

OneDayCitySmall

OneDayCitySmall

494 ms

bg_footer.png

bg_footer.png

1346 ms

close.png

close.png

1351 ms

30ccd650c8f067c7038bb1b60f040a7d905b74.gif

30ccd650c8f067c7038bb1b60f040a7d905b74.gif

194 ms

973b8b52b66b11a48efdc39d40f29c9f721fef.jpg

973b8b52b66b11a48efdc39d40f29c9f721fef.jpg

187 ms

2f911434c6db594702382d439a06bc5dbe4056.jpg

2f911434c6db594702382d439a06bc5dbe4056.jpg

186 ms

likebox.php

likebox.php

114 ms

like.php

like.php

132 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

62 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

66 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

78 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

103 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

63 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

72 ms

externalWidgetsNew.css

externalWidgetsNew.css

186 ms

jquery.min.js

jquery.min.js

27 ms

ExternalWidgetsTracking.js

ExternalWidgetsTracking.js

225 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

176 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

167 ms

392575_206357726122104_517560964_n.jpg

392575_206357726122104_517560964_n.jpg

118 ms

12299304_1500625123571901_5272335146273969533_n.jpg

12299304_1500625123571901_5272335146273969533_n.jpg

178 ms

10469708_1634696110138549_3763988915917413435_n.jpg

10469708_1634696110138549_3763988915917413435_n.jpg

67 ms

12814135_502067629993752_1155486737150413232_n.jpg

12814135_502067629993752_1155486737150413232_n.jpg

68 ms

12799393_10154120542142223_6105328109864643283_n.jpg

12799393_10154120542142223_6105328109864643283_n.jpg

68 ms

19436_109141232433600_5784795_n.jpg

19436_109141232433600_5784795_n.jpg

116 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

62 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

63 ms

ga.js

ga.js

20 ms

weather-icons-large-remake.png

weather-icons-large-remake.png

259 ms

__utm.gif

__utm.gif

24 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

6 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

14 ms

plusone.js

plusone.js

63 ms

widgets.js

widgets.js

110 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

68 ms

fastbutton

fastbutton

125 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

145 ms

postmessageRelay

postmessageRelay

90 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

36 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

49 ms

print.css

print.css

105 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

29 ms

rpc:shindig_random.js

rpc:shindig_random.js

41 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.nl.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.nl.html

44 ms

rounded-white.png

rounded-white.png

88 ms

zoomout.cur

zoomout.cur

87 ms

loader.white.gif

loader.white.gif

86 ms

Accessibility Review

visplanner.be accessibility score

47

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

visplanner.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

visplanner.be SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Visplanner.be 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 Visplanner.be 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

visplanner.be

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