Tools & Wizards About Us
metasafe.be screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

metasafe.be

Veiligheidsstudie, inbraakpreventie, inbraakbeveiliging, woning beveiligen, alarm woning, inbraak, inbraak woning METASAFE antwerpen vlaams brabant, b...

Page Load Speed

7.4 sec in total

First Response

3.1 sec

Resources Loaded

4.2 sec

Page Rendered

61 ms

metasafe.be screenshot

About Website

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

Contacteer METASAFE voor inbraakpreventie en inbraakbeveiliging in Vlaanderen!

Visit metasafe.be

Key Findings

We analyzed Metasafe.be page load time and found that the first response time was 3.1 sec and then it took 4.3 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

metasafe.be performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

www.metasafe.be

3104 ms

originTrials.41d7301a.bundle.min.js

29 ms

minified.js

37 ms

focus-within-polyfill.js

35 ms

polyfill.min.js

31 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Metasafe.be, 45% (23 requests) were made to Static.wixstatic.com and 25% (13 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Metasafe.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 293.2 kB (42%)

Content Size

702.2 kB

After Optimization

409.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Metasafe.be main page is 702.2 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. 50% of websites need less resources to load. HTML takes 374.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 286.5 kB

  • Original 374.6 kB
  • After minification 373.1 kB
  • After compression 88.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. 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 286.5 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 3.9 kB

  • Original 99.9 kB
  • After minification 96.0 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. METASAFE images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 227.7 kB
  • After minification 227.7 kB
  • After compression 224.9 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.

Requests Breakdown

Number of requests can be reduced by 11 (31%)

Requests Now

35

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.metasafe.be

www.metasafe.be

3104 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

29 ms

minified.js

minified.js

37 ms

focus-within-polyfill.js

focus-within-polyfill.js

35 ms

polyfill.min.js

polyfill.min.js

31 ms

thunderbolt-commons.2113c4aa.bundle.min.js

thunderbolt-commons.2113c4aa.bundle.min.js

122 ms

main.6c492079.bundle.min.js

main.6c492079.bundle.min.js

121 ms

lodash.min.js

lodash.min.js

122 ms

react.production.min.js

react.production.min.js

122 ms

react-dom.production.min.js

react-dom.production.min.js

125 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

123 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

137 ms

bea144_a64c5549442a401f94a18b8919159e66~mv2.png

bea144_a64c5549442a401f94a18b8919159e66~mv2.png

196 ms

bundle.min.js

bundle.min.js

58 ms

bea144_3b025f4f16934d56831548b43564a09b~mv2.jpg

bea144_3b025f4f16934d56831548b43564a09b~mv2.jpg

235 ms

Logo.png

Logo.png

299 ms

bea144_d7ac447250594a958d838e73c7882daf~mv2.jpg

bea144_d7ac447250594a958d838e73c7882daf~mv2.jpg

215 ms

logo.jpg

logo.jpg

185 ms

10.jpg

10.jpg

167 ms

ContentLogo.png

ContentLogo.png

287 ms

7.jpg

7.jpg

305 ms

8.jpg

8.jpg

319 ms

9.jpg

9.jpg

369 ms

het.png

het.png

410 ms

maximg_dl_1.jpg

maximg_dl_1.jpg

437 ms

bea144_de457bb00e7f477bb55e89ebbdad592f~mv2.jpg

bea144_de457bb00e7f477bb55e89ebbdad592f~mv2.jpg

474 ms

bea144_ea935e6ea98642a5a78a58c1c486e4ff~mv2.jpg

bea144_ea935e6ea98642a5a78a58c1c486e4ff~mv2.jpg

562 ms

bea144_e8cd7a93765142d3ae2a69f683f08c97~mv2.jpg

bea144_e8cd7a93765142d3ae2a69f683f08c97~mv2.jpg

491 ms

bea144_2a35437ff00544ad961211b6019994f8~mv2.jpg

bea144_2a35437ff00544ad961211b6019994f8~mv2.jpg

539 ms

bea144_83a65a29eefb4faba7645f59eef796e1~mv2.jpg

bea144_83a65a29eefb4faba7645f59eef796e1~mv2.jpg

591 ms

bea144_1010ac4d16a34b03951458a6dd210111~mv2.jpg

bea144_1010ac4d16a34b03951458a6dd210111~mv2.jpg

640 ms

bea144_0a1d552cb1ea4dcab52e91eb13afeecf~mv2.jpg

bea144_0a1d552cb1ea4dcab52e91eb13afeecf~mv2.jpg

643 ms

106 ms

108 ms

107 ms

105 ms

105 ms

100 ms

138 ms

150 ms

147 ms

149 ms

144 ms

file.woff

file.woff

337 ms

file.woff

file.woff

348 ms

file.woff

file.woff

349 ms

file.woff

file.woff

370 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

19 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

metasafe.be accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

metasafe.be best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

metasafe.be SEO score

98

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

High

Tap targets are not sized appropriately

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

metasafe.be

Open Graph data is detected on the main page of METASAFE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: