Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

baloise.be

Baloise - Wij verzekeren wat jou inspireert

Page Load Speed

4.7 sec in total

First Response

231 ms

Resources Loaded

3.9 sec

Page Rendered

520 ms

baloise.be screenshot

About Website

Welcome to baloise.be homepage info - get ready to check Baloise best content for Belgium right away, or after learning these important things about baloise.be

Op zoek naar particuliere verzekeringen of verzekeringen voor je bedrijf? Ontdek het ruime aanbod van verzekeringsproducten bij Baloise.

Visit baloise.be

Key Findings

We analyzed Baloise.be page load time and found that the first response time was 231 ms and then it took 4.4 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

baloise.be performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

baloise.be

231 ms

particulieren.html

381 ms

styles.css

98 ms

lzl3vbu.js

216 ms

__basic-behaviour.js

286 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 62% of them (32 requests) were addressed to the original Baloise.be, 8% (4 requests) were made to Etracker.de and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (783 ms) belongs to the original domain Baloise.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.3 kB (67%)

Content Size

305.5 kB

After Optimization

101.2 kB

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

HTML Optimization

-89%

Potential reduce by 111.9 kB

  • Original 125.8 kB
  • After minification 117.2 kB
  • After compression 13.9 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 111.9 kB or 89% of the original size.

JavaScript Optimization

-51%

Potential reduce by 92.4 kB

  • Original 179.7 kB
  • After minification 179.6 kB
  • After compression 87.3 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 92.4 kB or 51% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (49%)

Requests Now

45

After Optimization

23

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

Accessibility Review

baloise.be accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

Missing source maps for large first-party JavaScript

SEO Factors

baloise.be SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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