4.7 sec in total
388 ms
3.8 sec
417 ms
Click here to check amazing Francoishollande content. Otherwise, check out these important facts you probably never knew about francoishollande.fr
François Hollande. 842,238 likes · 34,158 talking about this. Page officielle de François Hollande, président de la République Française. www.elysee.fr
Visit francoishollande.frWe analyzed Francoishollande.fr page load time and found that the first response time was 388 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 65% of websites can load faster.
francoishollande.fr performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value5.3 s
21/100
25%
Value5.0 s
63/100
10%
Value200 ms
90/100
30%
Value0.002
100/100
15%
Value3.7 s
90/100
10%
388 ms
518 ms
298 ms
365 ms
434 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Francoishollande.fr, 68% (62 requests) were made to Static.xx.fbcdn.net and 27% (25 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 242.2 kB (46%)
526.9 kB
284.7 kB
In fact, the total size of Francoishollande.fr main page is 526.9 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. HTML takes 296.5 kB which makes up the majority of the site volume.
Potential reduce by 237.8 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 237.8 kB or 80% of the original size.
Potential reduce by 4.4 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. Francoishollande images are well optimized though.
Number of requests can be reduced by 52 (58%)
89
37
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Francoishollande. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
francoishollande.fr
388 ms
francoishollande.fr
518 ms
rw3hvHw9YfL.css
298 ms
r6Aw0SZFbhw.css
365 ms
McLpmVM3wCm.css
434 ms
N5iHAgzP3Um.css
639 ms
slX8bpbTGPC.css
497 ms
J5OscvYCeDY.css
562 ms
sFTVm4Wm5AN.css
511 ms
aotr4BvRhka.css
499 ms
X97l7PURgJ9.css
559 ms
CBDLOEbg5FF.css
612 ms
v_An6I20hBD.css
610 ms
YZbfjhkE0sX.css
654 ms
hhn-1r1gAPt.css
659 ms
OFG6f5m6ZIM.css
654 ms
sWfWs0fJqat.css
686 ms
FAHeNGXgPup.js
713 ms
event
271 ms
1526306_10152182492652502_321723486_n.jpg
581 ms
1528711_10152182496267502_718510904_n.jpg
615 ms
12688194_10153972833972502_5191068985428563155_n.jpg
1364 ms
12631373_10153963835757502_1386988054492761458_n.jpg
1540 ms
10301415_10153422846157502_8435923802525869152_n.jpg
1544 ms
11046737_10153212855087502_4544051589231458799_n.jpg
1543 ms
10534599_10152657561952502_2311414738441097771_n.jpg
1540 ms
1798873_10152268142877502_1108967796_n.jpg
1545 ms
1560604_10152245424217502_945510028_n.jpg
1542 ms
1528711_10152182496267502_718510904_n.jpg
1543 ms
1526306_10152182492652502_321723486_n.jpg
1545 ms
12104299_10153750532107502_1702349462_n.jpg
1545 ms
410617_10150475767546766_10150475766226766_58076_847_b.jpg
1546 ms
245558_10150274834761766_10150274833171766_52572_1357_b.jpg
1547 ms
11265301_10153636914515350_1461166557206616239_n.png
1546 ms
1528711_10152182496267502_718510904_n.jpg
1581 ms
ZVyMWStefv_.png
226 ms
K00K-UgnsKu.png
225 ms
wL6VQj7Ab77.png
222 ms
ZrLxvLoiUzX.png
225 ms
GsNJNwuI-UM.gif
220 ms
HEyyDkPknAC.png
154 ms
geAvKyblz0A.png
159 ms
l5aPruN9xMM.png
157 ms
YGgz9e4B0yW.png
158 ms
ZYpT1aFajd7.png
157 ms
spacer.gif
109 ms
UHNY_g5mVbr.js
72 ms
FJmpeSpHpjS.js
224 ms
hbybLXHu6w1.js
84 ms
Oagsvfb4VWi.js
135 ms
1bNoFZUdlYZ.js
73 ms
_UYztdBNTjs.js
80 ms
1FCa-btixu2.js
201 ms
7BE0CZr3HTs.js
142 ms
IjqSyiwKeaX.js
143 ms
RTHSWgdzleR.js
144 ms
OZFAYTv-ZUg.js
210 ms
m-2AbGY1fWh.js
409 ms
VfAud2trIQQ.js
329 ms
kvx5eeRG4FE.js
407 ms
Nn19HjwCsOL.js
325 ms
pQrUxxo5oQp.js
326 ms
H3EKDTObx05.js
325 ms
J0ZuTxeV0vD.js
355 ms
bh5z0Gfv2P_.js
357 ms
njEKf1WUXml.js
357 ms
1QuX41zDRrx.js
393 ms
yMCR4PoU6B-.js
396 ms
7uWMMev-gdj.js
708 ms
yBzWdmXwoNV.js
707 ms
yXuA_dMgOm6.js
709 ms
c05laeT1OPx.js
1141 ms
-sVccfRXDIY.js
1133 ms
UiJCRDQUmbL.js
1131 ms
F1Xohf2RB95.png
514 ms
12814469_10206163146294733_9214546927666810405_n.jpg
282 ms
12512355_1722282341321192_2889812049181619552_n.jpg
285 ms
12079290_892321410843864_3677912399195814113_n.jpg
283 ms
10945009_720593804724672_596851883278638696_n.jpg
282 ms
10334427_1347449121947924_8462998430521032918_n.jpg
284 ms
1931364_10207035661963598_1505512889899979194_n.jpg
340 ms
12140560_10206589345464917_6386829480366844163_n.jpg
339 ms
12540683_10153856754701182_5486198799851819397_n.jpg
338 ms
1930800_1662976860620558_3228701691394748194_n.jpg
341 ms
pimRBh7B6ER.png
235 ms
I6-MnjEovm5.js
70 ms
Dppan5o6UJu.js
70 ms
8v2_hdH4Nfm.js
78 ms
-Tr757ZEtMP.js
271 ms
A0qdgknEnD5.js
73 ms
-PAXP-deijE.gif
71 ms
francoishollande.fr accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
francoishollande.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
francoishollande.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Francoishollande.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Francoishollande.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.
francoishollande.fr
Open Graph description is not detected on the main page of Francoishollande. 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: