3.9 sec in total
247 ms
3 sec
639 ms
Click here to check amazing Eco121 content for France. Otherwise, check out these important facts you probably never knew about eco121.fr
Eco121, le mensuel des décideurs des Hauts-de-France. Eco121 est un média qui se concentre sur l’actualité économique de la région Hauts-de-France.
Visit eco121.frWe analyzed Eco121.fr page load time and found that the first response time was 247 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
eco121.fr performance score
name
value
score
weighting
Value5.3 s
8/100
10%
Value10.3 s
0/100
25%
Value9.2 s
13/100
10%
Value640 ms
46/100
30%
Value0.547
13/100
15%
Value17.4 s
4/100
10%
247 ms
245 ms
718 ms
40 ms
56 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 15% of them (12 requests) were addressed to the original Eco121.fr, 28% (22 requests) were made to Media.eco121.fr and 23% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Media.eco121.fr.
Page size can be reduced by 584.7 kB (48%)
1.2 MB
623.2 kB
In fact, the total size of Eco121.fr main page is 1.2 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. Javascripts take 489.6 kB which makes up the majority of the site volume.
Potential reduce by 76.6 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 17.3 kB, which is 19% 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 76.6 kB or 85% of the original size.
Potential reduce by 123.8 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, Eco121 needs image optimization as it can save up to 123.8 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 192.7 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 192.7 kB or 39% of the original size.
Potential reduce by 191.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. Eco121.fr needs all CSS files to be minified and compressed as it can save up to 191.6 kB or 85% of the original size.
Number of requests can be reduced by 31 (76%)
41
10
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eco121. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
eco121.fr
247 ms
www.eco121.fr
245 ms
www.eco121.fr
718 ms
font-awesome.min.css
40 ms
css
56 ms
css
73 ms
d648a2f.css
332 ms
5e52012.css
316 ms
214ef46.css
337 ms
5f6a4a5.css
260 ms
fafeff9.css
338 ms
6132695.css
346 ms
js
87 ms
in.js
43 ms
subscribe-validate.js
113 ms
widgets.js
114 ms
jquery.min.js
44 ms
b5cb922.js
795 ms
banniere-newsletter%20728x90-usb.jpg
895 ms
loader_sblue.gif
112 ms
logo.png
128 ms
footer_logo.png
128 ms
4a11e2878764d0b39b83ec286a6e5a5f
955 ms
59130faa9ae09f3b1034a2fc1f3694eb
660 ms
da3de5398318dab8781146c7fad16507
733 ms
ba9268eedee856534ac11d5e2e66b266
912 ms
90ec9b2dbbddac2b490c0f746b9271bf
1115 ms
5cd071207aa08e470cde32ec336506cf
869 ms
f10c90f0f8fa3d9dc2349997a11d87f7
1270 ms
64a8511f8b2e1f7becfe32bf6e2b40d9
1022 ms
83cf7eb8562b73558fcca2dc50ff5f67
1010 ms
665702fc85eb0407d190407e7150edba
1282 ms
12f33e6613bd20cc01cb015f3233256a
1055 ms
1ad15619ec788d006ea3baa6e098f66c
1129 ms
8339ecfc337629283dc6e6e082dbe8ab
1137 ms
6ee798d924d7d837e8b7128f9c8460c8
1162 ms
d5bc6c1b73d5acf05788f8b41e35ed8f
1227 ms
856f96465826ae3db58a0b5b00b400dc
1245 ms
277e28e6f3ed07cd1f78892a3cf60fb8
1354 ms
e0435649cb983371cf54fadf97adfe48
1273 ms
02dd56a3e8f649fdd90d0df4e3e113e4
1314 ms
81952f3e33a85fbde5f8c42ef6e2bd2b
1347 ms
7001879e197a7f753d88555fd1a339a7
1367 ms
sdk.js
125 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
65 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
100 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
122 ms
kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf
129 ms
kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf
123 ms
fontawesome-webfont.woff
14 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
128 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
144 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
144 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
143 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
144 ms
sdk.js
11 ms
87 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
102 ms
settings
95 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
21 ms
eco121
60 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
22 ms
runtime-b1c52fd0a13ead5fcf6b.js
45 ms
modules-96ebc7ac3ad66d681a3d.js
86 ms
main-babd9234dc048fb47339.js
72 ms
_app-a9c9f1a99e4414675fb1.js
84 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
114 ms
_buildManifest.js
122 ms
_ssgManifest.js
123 ms
8526.0c32a8f0cfc5749221a3.js
23 ms
3438.6b749a04474f8fb0cbba.js
21 ms
8283.f3e5048cca7cef5eed7f.js
22 ms
3077.44bfeb00af01bc4020f6.js
46 ms
1362.42d432e02f7980bca032.js
40 ms
4956.c4e51ef593974b9db0bb.js
81 ms
5893.d500bd2a89ded806aa73.js
20 ms
eco121.fr accessibility score
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
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements 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
Form elements do not have associated labels
Links do not have a discernible name
eco121.fr 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
eco121.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
FR
![]()
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eco121.fr 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 Eco121.fr 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.
eco121.fr
Open Graph description is not detected on the main page of Eco121. 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: