7.4 sec in total
671 ms
5.4 sec
1.3 sec
Visit nae.fr now to see the best up-to-date NAE content for France and also check out these interesting facts you probably never knew about nae.fr
Visit nae.frWe analyzed Nae.fr page load time and found that the first response time was 671 ms and then it took 6.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.
nae.fr performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value13.7 s
0/100
25%
Value8.6 s
17/100
10%
Value230 ms
86/100
30%
Value0.171
70/100
15%
Value11.0 s
21/100
10%
671 ms
87 ms
118 ms
276 ms
312 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 59% of them (58 requests) were addressed to the original Nae.fr, 14% (14 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nae.fr.
Page size can be reduced by 262.5 kB (18%)
1.4 MB
1.2 MB
In fact, the total size of Nae.fr main page is 1.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 77.9 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 77.9 kB or 76% of the original size.
Potential reduce by 12.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. NAE images are well optimized though.
Potential reduce by 7.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 7.4 kB or 28% of the original size.
Potential reduce by 164.3 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. Nae.fr needs all CSS files to be minified and compressed as it can save up to 164.3 kB or 60% of the original size.
Number of requests can be reduced by 47 (57%)
82
35
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.nae.fr
671 ms
fbsdk-en_US.js
87 ms
wp-emoji-release.min.js
118 ms
jquery-1.12.4-wp.js
276 ms
jquery-migrate.min-1.4.1.js
312 ms
tracking-analytics-events-408af75f37da3226b770ca447e95416c.js
314 ms
front.min-1.2.48.js
311 ms
st_insights.js
115 ms
recaptcha-53664d7d14349055295a37dc91c8022a.js
344 ms
scripts-a53aa4bcc6efd46851c399946db2f0f4.js
486 ms
ssba-e5d118a7f4fa4616abe29047acb7f774.js
487 ms
blankshield.min-4116.js
487 ms
block-tabnapping.min-4116.js
486 ms
api.js
58 ms
custom.min-4.0.9.js
577 ms
common-398d4eeaee00dfb16d4f94f058c7d47f.js
487 ms
functions-978d27ac0b9f82e0949a67f087bfdaaf.js
487 ms
wp-embed.min.js
478 ms
mediaelement-and-player.min-4.2.13-9993131.js
695 ms
mediaelement-migrate.min.js
480 ms
wp-mediaelement.min.js
560 ms
vendor.6f1879b7-d6563e5e654b4a2f81e5db5ea27c125e.js
694 ms
public.f80edd11-b6fc718f8fcaa18440e2ee14ffb6c4d1.js
544 ms
lazyload.min.js
647 ms
sdk.js
30 ms
ga-b66b3b5d54e154c81a50880cdcd7e5f8.js
362 ms
logo-header-normandie.jpg
336 ms
logo.png
618 ms
Moteur-LEAP-Safran.jpg
646 ms
AT432-YMARE-photo-daniel-trehet-286.jpg
646 ms
NAE-slide2_1920.jpg
646 ms
St%C3%A9_Vallet_REA_Benoit_Decout.jpg
639 ms
membres.jpg
609 ms
recrutement.jpg
899 ms
picto-business-grey-1.png
896 ms
picto-emploi-grey-1.png
899 ms
picto-RTI-grey.png
900 ms
picto-communication-grey-1.png
898 ms
Loupe-e1538984008400.png
898 ms
leopard-trophees-economie-normande-2020-1080x675.png
1019 ms
t%C3%A9l%C3%A9chargement.png
925 ms
La-DGA-%C3%A9value-de-nouvelles-capacit%C3%A9s-de-renseignement.png
1017 ms
Bandeau_Financeurs_2017.jpg
904 ms
Logo-ability-browser-non-alpha-300x53.png
904 ms
validationEngine.jquery-150679348e1baf03161d6c783f7fa425.css
793 ms
common-skeleton.min-4.10.2.css
809 ms
tooltip.min-4.10.2.css
808 ms
style.min.css
802 ms
styles-72b032be7c9e1d7b0a7a36a9e7714ea8.css
1015 ms
front.min.css
1009 ms
font-awesome.min.css
225 ms
style-cc75838a613e5961c0abaa81dde02df4.css
1009 ms
css
182 ms
dashicons.min.css
1009 ms
style-14fe492248daab7b858b53fd92ca2d2c.css
1126 ms
et-core-unified-2-15767504406112.min.css
1022 ms
portal.html
482 ms
recaptcha__en.js
495 ms
modules.ttf
1378 ms
collect
372 ms
hqdefault.jpg
660 ms
youtube.png
624 ms
hqdefault.jpg
624 ms
hqdefault.jpg
625 ms
mediaelementplayer-legacy.min-4.2.13-9993131.css
581 ms
wp-mediaelement.min.css
591 ms
public.75b7aa11-d20602920e601ad821e91adcafee01bb.css
593 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
949 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
1300 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
1317 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
1316 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
1314 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
1316 ms
dFa5ZfeM_74wlPZtksIFYoEf6HOpXnpwfa0.ttf
1316 ms
dFa5ZfeM_74wlPZtksIFYuUe6HOpXnpwfa0.ttf
1314 ms
dFa5ZfeM_74wlPZtksIFYskZ6HOpXnpwfa0.ttf
1318 ms
dFa6ZfeM_74wlPZtksIFajo6-F6LVlA.ttf
1306 ms
dFa5ZfeM_74wlPZtksIFYpEY6HOpXnpwfa0.ttf
1306 ms
anchor
513 ms
wa.css
730 ms
277411069
1071 ms
BG-filiere-excellence.jpg
550 ms
styles__ltr.css
192 ms
dUg2RX0dt0dTTlbc5xuaFyZXJEpJwtNdyW4dnj8sSFk.js
326 ms
webworker.js
674 ms
logo_48.png
320 ms
pview
478 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
391 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
391 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
391 ms
710178093.jpg
415 ms
player.js
412 ms
player.css
347 ms
vuid.min.js
341 ms
recaptcha__en.js
65 ms
sc
229 ms
reload
85 ms
defaults-blue_60x60.png
98 ms
710178093.jpg
52 ms
nae.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
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.
nae.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
nae.fr SEO score
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 Nae.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 Nae.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.
nae.fr
Open Graph description is not detected on the main page of NAE. 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: