4.7 sec in total
412 ms
3.9 sec
412 ms
Visit indius.fr now to see the best up-to-date Indius content and also check out these interesting facts you probably never knew about indius.fr
indius
Visit indius.frWe analyzed Indius.fr page load time and found that the first response time was 412 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
indius.fr performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value6.1 s
12/100
25%
Value5.6 s
53/100
10%
Value690 ms
43/100
30%
Value0.162
72/100
15%
Value10.5 s
24/100
10%
412 ms
687 ms
553 ms
121 ms
631 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Indius.fr, 62% (33 requests) were made to Static.lyad.fr and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Static.lyad.fr.
Page size can be reduced by 126.0 kB (18%)
691.6 kB
565.5 kB
In fact, the total size of Indius.fr main page is 691.6 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. 70% of websites need less resources to load. Images take 304.8 kB which makes up the majority of the site volume.
Potential reduce by 54.5 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 13.7 kB, which is 20% 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 54.5 kB or 80% of the original size.
Potential reduce by 664 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. Indius images are well optimized though.
Potential reduce by 61.0 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 61.0 kB or 23% of the original size.
Potential reduce by 9.9 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. Indius.fr needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 20% of the original size.
Number of requests can be reduced by 21 (49%)
43
22
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indius. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
indius.fr
412 ms
www.lyad.fr
687 ms
vitrine.min.css
553 ms
css
121 ms
frontend.min.css
631 ms
plugins.min.css
584 ms
frontend_header.js
608 ms
fr.min.js
600 ms
index.js
282 ms
frontend_footer.js
1197 ms
vitrine.min.js
597 ms
ga.js
270 ms
gpt.js
310 ms
logo-lyad.png
379 ms
logo-mobile.png
514 ms
icon-subscribe.png
512 ms
slide-arrow.png
513 ms
image_9.jpg
1439 ms
feat1.png
1387 ms
feat2.png
1387 ms
feat3.png
1387 ms
feat5.png
1386 ms
feat4.png
1387 ms
temoignage-bg.jpg
1436 ms
fonc1.png
1435 ms
fonc2.png
1436 ms
fonc3.png
1436 ms
netfaces.png
1437 ms
4-1_10.png
1629 ms
5-1_08.png
1627 ms
6-1_06.png
1627 ms
8-1_03.png
1627 ms
arrow.png
1626 ms
bg-men.png
1626 ms
menbubblel.png
1761 ms
menbubbler.png
1760 ms
bg-homme.jpg
1930 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
111 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
309 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
1109 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
1112 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
1112 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
1111 ms
fontawesome-webfont.woff
1559 ms
icomoon.woff
1560 ms
pubads_impl_2022092601.js
1123 ms
ppub_config
1318 ms
collect
1080 ms
client:plusone.js
1119 ms
sdk.js
1105 ms
sdk.js
33 ms
cb=gapi.loaded_0
107 ms
114 ms
indius.fr accessibility score
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
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
indius.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
Browser errors were logged to the console
indius.fr 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
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 Indius.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 Indius.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.
indius.fr
Open Graph description is not detected on the main page of Indius. 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: