8.3 sec in total
1.3 sec
6.7 sec
283 ms
Click here to check amazing Videotheque CNRS content for France. Otherwise, check out these important facts you probably never knew about videotheque.cnrs.fr
CNRS Images est la plateforme d’images du CNRS : photos, videos, films et expositions sur l’actualité de la recherche, tous les domaines scientifiques et les sciences au 20e siècle.
Visit videotheque.cnrs.frWe analyzed Videotheque.cnrs.fr page load time and found that the first response time was 1.3 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
videotheque.cnrs.fr performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value11.9 s
0/100
25%
Value7.5 s
27/100
10%
Value250 ms
84/100
30%
Value0.01
100/100
15%
Value17.7 s
4/100
10%
1280 ms
245 ms
477 ms
229 ms
257 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 99% of them (115 requests) were addressed to the original Videotheque.cnrs.fr, 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Videotheque.cnrs.fr.
Page size can be reduced by 1.5 MB (45%)
3.4 MB
1.8 MB
In fact, the total size of Videotheque.cnrs.fr main page is 3.4 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 184.7 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 184.7 kB or 83% of the original size.
Potential reduce by 46.0 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. Videotheque CNRS images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 80% of the original size.
Potential reduce by 145.7 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. Videotheque.cnrs.fr needs all CSS files to be minified and compressed as it can save up to 145.7 kB or 85% of the original size.
Number of requests can be reduced by 35 (30%)
115
80
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Videotheque CNRS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
videotheque.cnrs.fr
1280 ms
jquery-ui-1.9.2.custom.css
245 ms
n_general.css
477 ms
empty.php
229 ms
detectEnv.js
257 ms
fonctionsJavascript.js
350 ms
rightPanel.js
463 ms
autocomplete-3-2.js
502 ms
prototype.js
896 ms
scriptaculous.js
508 ms
all.js
9 ms
jquery-1.9.1.min.js
834 ms
jquery-ui-1.9.2.custom.min.js
1182 ms
drag_and_drop.js
649 ms
lang_FR.js
668 ms
general.js
670 ms
cherche.js
907 ms
solr.js
833 ms
panier.js
840 ms
main.js
1151 ms
AC_QuickTime.js
990 ms
OW_player.js
1273 ms
OWH_player.js
1636 ms
OJW_player.js
1322 ms
jwplayer.js
1637 ms
n_style.css
922 ms
empty.php
495 ms
builder.js
159 ms
effects.js
349 ms
dragdrop.js
259 ms
controls.js
266 ms
slider.js
179 ms
sound.js
186 ms
logo-CNRS-web.png
682 ms
icn-play.png
683 ms
makeVignette.php
683 ms
makeVignette.php
686 ms
makeVignette.php
687 ms
makeVignette.php
683 ms
makeVignette.php
724 ms
makeVignette.php
713 ms
makeVignette.php
846 ms
makeVignette.php
757 ms
makeVignette.php
775 ms
makeVignette.php
759 ms
makeVignette.php
994 ms
makeVignette.php
954 ms
makeVignette.php
966 ms
makeVignette.php
966 ms
makeVignette.php
1077 ms
makeVignette.php
1147 ms
makeVignette.php
1245 ms
makeVignette.php
1175 ms
makeVignette.php
1261 ms
makeVignette.php
1296 ms
makeVignette.php
1372 ms
makeVignette.php
1447 ms
makeVignette.php
1385 ms
makeVignette.php
1550 ms
makeVignette.php
1551 ms
makeVignette.php
1506 ms
makeVignette.php
1672 ms
makeVignette.php
1688 ms
makeVignette.php
1726 ms
makeVignette.php
1735 ms
makeVignette.php
1841 ms
makeVignette.php
1767 ms
makeVignette.php
1883 ms
makeVignette.php
1898 ms
blank.php
1261 ms
empty.php
1303 ms
makeVignette.php
1312 ms
makeVignette.php
1465 ms
makeVignette.php
1522 ms
makeVignette.php
1416 ms
makeVignette.php
1443 ms
makeVignette.php
1537 ms
makeVignette.php
1547 ms
makeVignette.php
1679 ms
makeVignette.php
1655 ms
makeVignette.php
1596 ms
makeVignette.php
1536 ms
makeVignette.php
1500 ms
makeVignette.php
1636 ms
makeVignette.php
1738 ms
makeVignette.php
1642 ms
makeVignette.php
1590 ms
makeVignette.php
1504 ms
makeVignette.php
1447 ms
makeVignette.php
1635 ms
makeVignette.php
1781 ms
makeVignette.php
1624 ms
makeVignette.php
1628 ms
makeVignette.php
1500 ms
makeVignette.php
1445 ms
icn-nav-down.png
1519 ms
icn-search.png
1554 ms
ui-bg_flat_100_fcfdfd_40x100.png
1471 ms
icn-lang-down.png
1474 ms
shadow_alpha.png
1462 ms
icn-slide-arrow-w.png
1496 ms
slider-bulle-off.png
1492 ms
icn-slide-arrow-blue-darker.png
1424 ms
icn-social-rss.png
1419 ms
icn-social-dailymotion.png
1422 ms
icn-social-twitter.png
1411 ms
icn-social-facebook.png
1427 ms
icn-anchor-top.png
1438 ms
modalBG.png
1322 ms
slider-bulle-on.png
1319 ms
croix.png
1338 ms
ui-icons_FFF_256x240.png
1311 ms
icn-popup-identifiant.png
1308 ms
icn-popup-password.png
1292 ms
icn-popup-panier-add-success.png
1188 ms
demo_small.css
90 ms
videotheque.cnrs.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-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
videotheque.cnrs.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
General
Impact
Issue
Detected JavaScript libraries
videotheque.cnrs.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Videotheque.cnrs.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Videotheque.cnrs.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.
videotheque.cnrs.fr
Open Graph description is not detected on the main page of Videotheque CNRS. 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: