Access towereye.be. TowerEye: Tijdelijke Netwerken en Camerabewaking

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

towereye.be

271 ms

towereye.be

335 ms

88 ms

en

149 ms

web.assets_common.min.css

170 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 51% of them (44 requests) were addressed to the original Towereye.be, 35% (30 requests) were made to Fonts.odoocdn.com and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (916 ms) belongs to the original domain Towereye.be.

Content Size

2.0 MB

After Optimization

1.6 MB

In fact, the total size of Towereye.be main page is 2.0 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 28.6 kB

Original 36.1 kB
After minification 30.6 kB
After compression 7.5 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 5.4 kB, which is 15% 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 28.6 kB or 79% of the original size.

Image Optimization

-18%

Potential reduce by 316.2 kB

Original 1.8 MB
After minification 1.5 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. Obviously, Tower Eye needs image optimization as it can save up to 316.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 1.4 kB

Original 11.2 kB
After minification 11.2 kB
After compression 9.8 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 1.4 kB or 13% of the original size.

CSS Optimization

-26%

Potential reduce by 36.9 kB

Original 139.8 kB
After minification 139.8 kB
After compression 102.9 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. Towereye.be needs all CSS files to be minified and compressed as it can save up to 36.9 kB or 26% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

NL
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Towereye.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Towereye.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

towereye.be

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

Report Summary

Performance

Accessibility

Best Practices

SEO

TowerEye: Tijdelijke Netwerken en Camerabewaking

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

towereye.be

towereye.be

en

web.assets_common.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

towereye.be

towereye.be

en

web.assets_common.min.css

web.assets_frontend.min.css

web.assets_common_minimal.min.js

web.assets_frontend_minimal.min.js

js

css

css

TowerEye

129.jpg

build-builder-construction-585418.jpg

politie.jpg

333.jpg

the-qontinent-banner.jpg

build-builder-construction-585418.jpg

werfbeveiliging-banner%20%282%29.png

18.svg

129.jpg

314_sm.png

315_sm.png

526_sm.png

523_sm.png

09.svg

260%20%283%29.png

flanders-stateoftheart-light.png

us.png

be.png

odoo_logo_tiny.png

fontawesome-webfont.woff

KFOmCnqEu92Fr1Mu4mxP.ttf

Roboto-Regular-webfont.woff

Roboto-Regular.ttf

Roboto-Medium-webfont.woff

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

Roboto-Light-webfont.woff

Roboto-Thin-webfont.woff

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

Roboto-Bold-webfont.woff

Roboto-Black-webfont.woff

NotoSansArabic-Reg.woff

NotoSansHebrew-Reg.woff

NotoSans-Reg.woff