Tools & Wizards About Us
vt4.be screenshot

Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

vt4.be

Combell.com Parkpage

Page Load Speed

2.2 sec in total

First Response

352 ms

Resources Loaded

1.8 sec

Page Rendered

116 ms

vt4.be screenshot

About Website

Welcome to vt4.be homepage info - get ready to check Vt 4 best content right away, or after learning these important things about vt4.be

This domain name has been activated for a Combell.com customer

Visit vt4.be

Key Findings

We analyzed Vt4.be page load time and found that the first response time was 352 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

vt4.be performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

vt4.be

352 ms

391 ms

domain

114 ms

css.eaa9de68.css

192 ms

api.js

31 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Vt4.be, 61% (14 requests) were made to Combell.com and 9% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (550 ms) relates to the external source Combell.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.2 kB (2%)

Content Size

638.4 kB

After Optimization

623.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-47%

Potential reduce by 531 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 588 B

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 531 B or 47% of the original size.

Image Optimization

-12%

Potential reduce by 13.4 kB

  • Original 112.9 kB
  • After minification 99.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, Vt 4 needs image optimization as it can save up to 13.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 457.8 kB
  • After minification 457.8 kB
  • After compression 456.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 103 B

  • Original 66.5 kB
  • After minification 66.5 kB
  • After compression 66.4 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. Vt4.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (68%)

Requests Now

19

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vt4.be

vt4.be

352 ms

391 ms

domain

domain

114 ms

css.eaa9de68.css

css.eaa9de68.css

192 ms

api.js

api.js

31 ms

runtime.8d843e9d.js

runtime.8d843e9d.js

271 ms

9755.c964f554.js

9755.c964f554.js

398 ms

5169.df92f2c9.js

5169.df92f2c9.js

397 ms

5644.886765fe.js

5644.886765fe.js

550 ms

9154.ca1aa940.js

9154.ca1aa940.js

273 ms

6891.b1121508.js

6891.b1121508.js

285 ms

9257.ed79e835.js

9257.ed79e835.js

396 ms

9458.a64aaf55.js

9458.a64aaf55.js

461 ms

js.08e1827c.js

js.08e1827c.js

402 ms

recaptcha__de.js

recaptcha__de.js

22 ms

css2

css2

37 ms

gtm.js

gtm.js

91 ms

j.php

j.php

39 ms

jasperc.png

jasperc.png

213 ms

jasperc.png

jasperc.png

394 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

18 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

25 ms

iubenda_cs.js

iubenda_cs.js

42 ms

Accessibility Review

vt4.be accessibility score

45

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

vt4.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

vt4.be SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vt4.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Vt4.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

vt4.be

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