Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

indicator.be

Larcier-Intersentia ~ Webshop ~ Livres, formations, revues et solutions digitales

Page Load Speed

1.2 sec in total

First Response

275 ms

Resources Loaded

860 ms

Page Rendered

106 ms

indicator.be screenshot

About Website

Click here to check amazing Indicator content for Belgium. Otherwise, check out these important facts you probably never knew about indicator.be

Larcier-Intersentia propose des solutions techniques et documentaires adaptées aux besoins des professionnels de la fiscalité, du droit et de la conformité.

Visit indicator.be

Key Findings

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

Performance Metrics

indicator.be performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value1,460 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

www.indicator.be

275 ms

bg_page_beige2.gif

90 ms

FR-NLkarton.png

316 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Indicator.be and no external sources were called. The less responsive or slowest element that took the longest time to load (316 ms) belongs to the original domain Indicator.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.7 kB (13%)

Content Size

61.2 kB

After Optimization

53.5 kB

In fact, the total size of Indicator.be main page is 61.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 60.2 kB which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 414 B

  • Original 921 B
  • After minification 862 B
  • After compression 507 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 414 B or 45% of the original size.

Image Optimization

-12%

Potential reduce by 7.3 kB

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

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indicator. According to our analytics all requests are already optimized.

Accessibility Review

indicator.be accessibility score

65

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.

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

ARIA IDs are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

indicator.be best practices score

58

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

Missing source maps for large first-party JavaScript

SEO Factors

indicator.be SEO score

83

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

High

robots.txt is not valid

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

    FR

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indicator.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Indicator.be main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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