Tools & Wizards About Us
visionline.be screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

visionline.be

Startpagina | VisionLine

Page Load Speed

2.9 sec in total

First Response

353 ms

Resources Loaded

2.1 sec

Page Rendered

417 ms

visionline.be screenshot

About Website

Welcome to visionline.be homepage info - get ready to check Vision Line best content right away, or after learning these important things about visionline.be

Webdesign, grafische vormgeving en fotografie. Al meer dan 10 jaar!

Visit visionline.be

Key Findings

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

Performance Metrics

visionline.be performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

visionline.be

353 ms

www.visionline.be

647 ms

142 ms

style.css

161 ms

jquery-ui-1.8.18.custom.css

249 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 57% of them (20 requests) were addressed to the original Visionline.be, 6% (2 requests) were made to Maxcdn.bootstrapcdn.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (656 ms) belongs to the original domain Visionline.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.5 kB (32%)

Content Size

582.1 kB

After Optimization

393.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Visionline.be main page is 582.1 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. 45% of websites need less resources to load. Images take 327.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 14.9 kB

  • Original 21.6 kB
  • After minification 21.0 kB
  • After compression 6.6 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 14.9 kB or 69% of the original size.

Image Optimization

-5%

Potential reduce by 15.0 kB

  • Original 327.9 kB
  • After minification 312.9 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. Vision Line images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 56.0 kB

  • Original 107.1 kB
  • After minification 106.4 kB
  • After compression 51.1 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 56.0 kB or 52% of the original size.

CSS Optimization

-82%

Potential reduce by 102.5 kB

  • Original 125.6 kB
  • After minification 114.7 kB
  • After compression 23.1 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. Visionline.be needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (40%)

Requests Now

30

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

visionline.be

visionline.be

353 ms

www.visionline.be

www.visionline.be

647 ms

142 ms

style.css

style.css

161 ms

jquery-ui-1.8.18.custom.css

jquery-ui-1.8.18.custom.css

249 ms

font-awesome.min.css

font-awesome.min.css

12 ms

css

css

26 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

14 ms

jquery-ui.min.js

jquery-ui.min.js

12 ms

script.js

script.js

330 ms

shCore.js

shCore.js

241 ms

shAutoloader.js

shAutoloader.js

166 ms

shCoreDefault.css

shCoreDefault.css

166 ms

logo2x.png

logo2x.png

234 ms

workstation.jpg

workstation.jpg

656 ms

empty.gif

empty.gif

327 ms

css

css

15 ms

share.js

share.js

375 ms

ribbon.png

ribbon.png

99 ms

nobile-webfont.woff

nobile-webfont.woff

173 ms

anMUvcNT0H1YN4FII8wpr8emR1SRkPORqDWOmtmtNc0.ttf

anMUvcNT0H1YN4FII8wpr8emR1SRkPORqDWOmtmtNc0.ttf

42 ms

nobile_bold-webfont.woff

nobile_bold-webfont.woff

165 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

328 ms

all.js

all.js

31 ms

analytics.js

analytics.js

28 ms

thumb_UF_Y3WqN.png

thumb_UF_Y3WqN.png

478 ms

social.jpg

social.jpg

245 ms

support.jpg

support.jpg

236 ms

infographic.gif

infographic.gif

261 ms

collect

collect

35 ms

131 ms

xd_arbiter.php

xd_arbiter.php

17 ms

xd_arbiter.php

xd_arbiter.php

35 ms

ping

ping

59 ms

Accessibility Review

visionline.be accessibility score

78

Accessibility Issues

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

High

Links do not have a discernible name

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

visionline.be best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

visionline.be SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

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

visionline.be

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