Tools & Wizards About Us
lenartz.be screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

lenartz.be

Chauffagiste à Verviers, Spa, Aubel, Herve, Welkenraedt - LENARTZ

Page Load Speed

23.2 sec in total

First Response

645 ms

Resources Loaded

22 sec

Page Rendered

557 ms

lenartz.be screenshot

About Website

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

Chauffagiste à Aubel, près de Verviers, Spa, Herve et Welkenraedt | LENARTZ, chaudière gaz, chaudière mazout et pompe à chaleur à Aubel, Verviers, Herve, Spa.

Visit lenartz.be

Key Findings

We analyzed Lenartz.be page load time and found that the first response time was 645 ms and then it took 22.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

lenartz.be performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.94

3/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

lenartz.be

645 ms

www.lenartz.be

826 ms

style.css

130 ms

plusone.js

311 ms

styles.css

268 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 44% of them (17 requests) were addressed to the original Lenartz.be, 21% (8 requests) were made to Apis.google.com and 8% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source R19008.ovh.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.3 kB (43%)

Content Size

291.3 kB

After Optimization

165.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lenartz.be main page is 291.3 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 151.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 18.0 kB

  • Original 24.8 kB
  • After minification 23.7 kB
  • After compression 6.8 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 18.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 561 B

  • Original 89.5 kB
  • After minification 88.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. LENARTZ images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 86.0 kB

  • Original 151.6 kB
  • After minification 150.2 kB
  • After compression 65.6 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 86.0 kB or 57% of the original size.

CSS Optimization

-82%

Potential reduce by 20.7 kB

  • Original 25.4 kB
  • After minification 17.0 kB
  • After compression 4.6 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. Lenartz.be needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (43%)

Requests Now

35

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lenartz.be

lenartz.be

645 ms

www.lenartz.be

www.lenartz.be

826 ms

style.css

style.css

130 ms

plusone.js

plusone.js

311 ms

styles.css

styles.css

268 ms

comment-reply.min.js

comment-reply.min.js

275 ms

jquery.js

jquery.js

410 ms

jquery-migrate.min.js

jquery-migrate.min.js

278 ms

all.js

all.js

266 ms

jquery.form.min.js

jquery.form.min.js

636 ms

scripts.js

scripts.js

930 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

320 ms

ga.js

ga.js

206 ms

puce.png

puce.png

20106 ms

lenartz-photovoltaique.jpg

lenartz-photovoltaique.jpg

573 ms

achat-panneau-solaire.jpg

achat-panneau-solaire.jpg

570 ms

maison-capteurs-photovoltaique.jpg

maison-capteurs-photovoltaique.jpg

202 ms

chauffage.jpg

chauffage.jpg

199 ms

images_003.jpg

images_003.jpg

200 ms

images_005.jpg

images_005.jpg

569 ms

sdb3_000.jpg

sdb3_000.jpg

577 ms

devis-panneaux-photovoltaiques.jpg

devis-panneaux-photovoltaiques.jpg

574 ms

436 ms

__utm.gif

__utm.gif

177 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

138 ms

fastbutton

fastbutton

318 ms

xd_arbiter.php

xd_arbiter.php

162 ms

xd_arbiter.php

xd_arbiter.php

384 ms

postmessageRelay

postmessageRelay

325 ms

xd_arbiter.php

xd_arbiter.php

151 ms

like.php

like.php

447 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

162 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

129 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

400 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

366 ms

rpc:shindig_random.js

rpc:shindig_random.js

73 ms

9WGlSBHSxG2.js

9WGlSBHSxG2.js

274 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

256 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

31 ms

Accessibility Review

lenartz.be accessibility score

80

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

SEO Factors

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

lenartz.be

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