7.1 sec in total
751 ms
6.1 sec
304 ms
Visit journal.lecho.be now to see the best up-to-date Journal L Echo content for Belgium and also check out these interesting facts you probably never knew about journal.lecho.be
Visit journal.lecho.beWe analyzed Journal.lecho.be page load time and found that the first response time was 751 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
journal.lecho.be performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value10.4 s
0/100
25%
Value7.1 s
31/100
10%
Value1,310 ms
18/100
30%
Value0.101
89/100
15%
Value11.3 s
19/100
10%
751 ms
58 ms
168 ms
172 ms
179 ms
Our browser made a total of 234 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Journal.lecho.be, 52% (122 requests) were made to Static.lecho.be and 36% (84 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Static.lecho.be.
Page size can be reduced by 2.5 MB (30%)
8.3 MB
5.8 MB
In fact, the total size of Journal.lecho.be main page is 8.3 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. 65% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 178.2 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 178.2 kB or 86% of the original size.
Potential reduce by 0 B
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. Journal L Echo images are well optimized though.
Potential reduce by 501.4 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 501.4 kB or 81% of the original size.
Potential reduce by 1.8 MB
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. Journal.lecho.be needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 88% of the original size.
Number of requests can be reduced by 150 (64%)
233
83
The browser has sent 233 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Journal L Echo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 118 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
journal.lecho.be
751 ms
dojo.xd.js
58 ms
fonts.css
168 ms
grid.css
172 ms
bump.css
179 ms
ipaper.css
173 ms
main.css
140 ms
datepicker.css
169 ms
scrollbar.css
172 ms
main.css
170 ms
decoratedBlocks.css
255 ms
imageSlider.css
204 ms
imageSliderFullscreen.css
223 ms
font-awesome.css
68 ms
css
107 ms
css
120 ms
echo-s2014.css
275 ms
tundra.css
78 ms
main_dojo.js
412 ms
main_dojo_ported.js
250 ms
dialog_dojo.js
252 ms
dst_dojo.js
366 ms
ZeroClipboard.js
366 ms
slider.js
366 ms
fr.js
366 ms
datepicker.js
1252 ms
bump.js
365 ms
mwTag.js
365 ms
MediafinUser.js
525 ms
Hyphenator.js
669 ms
fr.js
439 ms
scrollbar.js
531 ms
multipleItemsWidget.js
669 ms
fr.js
521 ms
tooltip.js
624 ms
ipaper.js
892 ms
ipaper.css
590 ms
dojoconfig.js
728 ms
dojo.js
58 ms
tag.js
357 ms
css
15 ms
NodeList-traverse.xd.js
7 ms
NodeList-manipulate.xd.js
6 ms
fx.xd.js
14 ms
Dialog.xd.js
7 ms
move.xd.js
6 ms
Source.xd.js
12 ms
string.xd.js
13 ms
window.xd.js
12 ms
Mover.xd.js
9 ms
Moveable.xd.js
8 ms
TimedMoveable.xd.js
9 ms
fx.xd.js
8 ms
_Widget.xd.js
13 ms
_Templated.xd.js
13 ms
_CssStateMixin.xd.js
14 ms
_FormMixin.xd.js
14 ms
_DialogMixin.xd.js
16 ms
DialogUnderlay.xd.js
14 ms
ContentPane.xd.js
14 ms
common.xd.js
14 ms
TooltipDialog.xd.js
14 ms
_base.xd.js
16 ms
Selector.xd.js
15 ms
Manager.xd.js
14 ms
common.xd.js
15 ms
autoscroll.xd.js
15 ms
Toggler.xd.js
15 ms
_WidgetBase.xd.js
8 ms
_base.xd.js
11 ms
parser.xd.js
12 ms
cache.xd.js
12 ms
_ContentPaneResizeMixin.xd.js
11 ms
html.xd.js
11 ms
loading.xd.js
11 ms
Container.xd.js
11 ms
Avatar.xd.js
11 ms
manager.xd.js
10 ms
Stateful.xd.js
11 ms
focus.xd.js
7 ms
place.xd.js
7 ms
popup.xd.js
9 ms
scroll.xd.js
10 ms
sniff.xd.js
10 ms
typematic.xd.js
8 ms
wai.xd.js
10 ms
window.xd.js
11 ms
stamp.xd.js
11 ms
_Contained.xd.js
10 ms
_LayoutWidget.xd.js
10 ms
AdapterRegistry.xd.js
8 ms
uacss.xd.js
4 ms
_Container.xd.js
4 ms
style.xd.js
37 ms
timing.xd.js
37 ms
Tooltip.xd.js
30 ms
BorderContainer.xd.js
31 ms
TabContainer.xd.js
32 ms
StackContainer.xd.js
29 ms
DragPane.xd.js
31 ms
CenteringPane.xd.js
125 ms
Button.xd.js
28 ms
cookie.xd.js
29 ms
hash.xd.js
31 ms
social-facebook.js
43 ms
social-mediaid.js
15 ms
mediafin-user.js
46 ms
mfcookie.js
37 ms
357 ms
body_gradient_fr.png
99 ms
_base.xd.js
24 ms
StackController.xd.js
24 ms
_FormWidget.xd.js
24 ms
_HasDropDown.xd.js
26 ms
regexp.xd.js
23 ms
_TabContainerBase.xd.js
23 ms
TabController.xd.js
24 ms
ScrollingTabController.xd.js
25 ms
debuglog.js
41 ms
cookie.js
15 ms
ToggleButton.xd.js
15 ms
Menu.xd.js
7 ms
MenuItem.xd.js
8 ms
base64.js
7 ms
regexp.js
9 ms
_KeyNavContainer.xd.js
9 ms
PopupMenuItem.xd.js
10 ms
CheckedMenuItem.xd.js
9 ms
MenuSeparator.xd.js
10 ms
analytics.js
6 ms
collect
5 ms
collect
67 ms
print.css
24 ms
view
231 ms
thumbnail.jpg
343 ms
thumbnail.jpg
559 ms
thumbnail.jpg
470 ms
thumbnail.jpg
267 ms
thumbnail.jpg
264 ms
thumbnail.jpg
326 ms
thumbnail.jpg
503 ms
thumbnail.jpg
504 ms
thumbnail.jpg
569 ms
thumbnail.jpg
583 ms
thumbnail.jpg
644 ms
thumbnail.jpg
705 ms
thumbnail.jpg
678 ms
thumbnail.jpg
959 ms
thumbnail.jpg
762 ms
thumbnail.jpg
788 ms
thumbnail.jpg
945 ms
thumbnail.jpg
876 ms
thumbnail.jpg
888 ms
thumbnail.jpg
1008 ms
thumbnail.jpg
1028 ms
thumbnail.jpg
1054 ms
thumbnail.jpg
1115 ms
thumbnail.jpg
1145 ms
thumbnail.jpg
1703 ms
thumbnail.jpg
1259 ms
thumbnail.jpg
1256 ms
thumbnail.jpg
1277 ms
thumbnail.jpg
1354 ms
thumbnail.jpg
1363 ms
thumbnail.jpg
1488 ms
thumbnail.jpg
1470 ms
logo_print.gif
1361 ms
view
174 ms
view
287 ms
view
475 ms
all.js
98 ms
ajax-loader.gif
91 ms
echologo_mini.png
1417 ms
seperator.png
1450 ms
PagePreviewPane.xd.js
1375 ms
xgemius.js
187 ms
ads-mediafin.adhese.com
210 ms
135 ms
xd_arbiter.php
40 ms
xd_arbiter.php
50 ms
DoublePagePane.xd.js
1174 ms
PageBrowserPane.xd.js
1225 ms
fpdata.js
90 ms
lsget.html
238 ms
PageBrowseButton.xd.js
1173 ms
back_krant_fr.jpg
1199 ms
button-single-prev.png
1070 ms
button-single-next.png
1201 ms
button-right2.png
1200 ms
button-left2.png
1151 ms
cal-grey.gif
1134 ms
button-icon-arrowdown.png
1121 ms
rexdot.js
92 ms
button-icon-arrowup.png
1063 ms
buttons-sprite.png
1030 ms
button-icon-pdf.png
1004 ms
button-icon-cross.png
961 ms
arrow_left.jpg
1461 ms
arrow_right.jpg
855 ms
blank.gif
151 ms
preview.jpg
243 ms
preview.jpg
246 ms
preview.jpg
250 ms
preview.jpg
280 ms
preview.jpg
227 ms
preview.jpg
473 ms
preview.jpg
449 ms
preview.jpg
490 ms
preview.jpg
520 ms
preview.jpg
514 ms
preview.jpg
670 ms
preview.jpg
711 ms
preview.jpg
731 ms
preview.jpg
715 ms
preview.jpg
719 ms
preview.jpg
1226 ms
preview.jpg
910 ms
preview.jpg
1053 ms
preview.jpg
1071 ms
preview.jpg
1072 ms
preview.jpg
1008 ms
preview.jpg
1149 ms
preview.jpg
1234 ms
preview.jpg
1274 ms
preview.jpg
1274 ms
preview.jpg
1311 ms
preview.jpg
1427 ms
preview.jpg
1912 ms
preview.jpg
1488 ms
preview.jpg
1534 ms
preview.jpg
1526 ms
preview.jpg
1589 ms
tooltip_connector_right.png
14 ms
xd_arbiter.php
8 ms
journal.lecho.be accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
journal.lecho.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
journal.lecho.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Journal.lecho.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Journal.lecho.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.
journal.lecho.be
Open Graph description is not detected on the main page of Journal L Echo. 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: