3.9 sec in total
380 ms
3.3 sec
158 ms
Visit legi.inpg.fr now to see the best up-to-date LEGI Inpg content for France and also check out these interesting facts you probably never knew about legi.inpg.fr
Visit legi.inpg.frWe analyzed Legi.inpg.fr page load time and found that the first response time was 380 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
legi.inpg.fr performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value8.9 s
1/100
25%
Value8.5 s
17/100
10%
Value110 ms
98/100
30%
Value0.001
100/100
15%
Value6.7 s
56/100
10%
380 ms
878 ms
417 ms
189 ms
374 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Legi.inpg.fr, 98% (45 requests) were made to Legi.grenoble-inp.fr. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Legi.grenoble-inp.fr.
Page size can be reduced by 475.2 kB (71%)
671.2 kB
196.0 kB
In fact, the total size of Legi.inpg.fr main page is 671.2 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. 20% of websites need less resources to load. Javascripts take 453.6 kB which makes up the majority of the site volume.
Potential reduce by 17.4 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 3.0 kB, which is 13% 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 17.4 kB or 76% of the original size.
Potential reduce by 3.1 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. LEGI Inpg images are well optimized though.
Potential reduce by 370.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 370.7 kB or 82% of the original size.
Potential reduce by 84.1 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. Legi.inpg.fr needs all CSS files to be minified and compressed as it can save up to 84.1 kB or 83% of the original size.
Number of requests can be reduced by 26 (68%)
38
12
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEGI Inpg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
legi.inpg.fr
380 ms
878 ms
417 ms
reset.css
189 ms
structure.css
374 ms
spip.css
185 ms
charte.css
368 ms
institut-ingenierie.css
280 ms
global.css
270 ms
local.css
275 ms
colorbox.css
278 ms
barre_outils.css
361 ms
spip.php
394 ms
mll_styles.css
374 ms
mediaelementplayer.css
553 ms
mejs-skins.css
452 ms
jquery.js
1081 ms
jquery.form.js
639 ms
jquery.autosave.js
459 ms
jquery.placeholder-label.js
482 ms
ajaxCallback.js
634 ms
jquery.cookie.js
552 ms
jquery.colorbox.js
755 ms
spip.mediabox.js
641 ms
jquery.markitup_pour_spip.js
823 ms
jquery.previsu_spip.js
727 ms
spip.php
786 ms
spip.php
779 ms
refbase.css
819 ms
mediaelement-and-player.min.js
1118 ms
spip.php
547 ms
spip.php
157 ms
siteon0.jpg
94 ms
baniere.jpg
368 ms
logo-cnrs.png
97 ms
logo-uga-bbc79.png
96 ms
logo-inpg-2f34d.gif
95 ms
logo-cuga-8194f.jpg
186 ms
logo-fed3g-ad09b.png
185 ms
logo-osug-e2086.png
187 ms
ok.gif
186 ms
overlay.png
187 ms
OpenSans-Bold-webfont.woff
458 ms
nimbuscondGNU.ttf
550 ms
OpenSans-Semibold-webfont.woff
279 ms
print.css
94 ms
legi.inpg.fr accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
legi.inpg.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
legi.inpg.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legi.inpg.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 Legi.inpg.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.
legi.inpg.fr
Open Graph description is not detected on the main page of LEGI Inpg. 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: