5.8 sec in total
1.6 sec
3.8 sec
521 ms
Welcome to charlemagne.fr homepage info - get ready to check Charlemagne best content right away, or after learning these important things about charlemagne.fr
Boutique propulsée par PrestaShop
Visit charlemagne.frWe analyzed Charlemagne.fr page load time and found that the first response time was 1.6 sec 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.
charlemagne.fr performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.7 s
16/100
25%
Value4.4 s
74/100
10%
Value120 ms
97/100
30%
Value0.21
59/100
15%
Value5.0 s
77/100
10%
1554 ms
154 ms
169 ms
172 ms
170 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 38% of them (21 requests) were addressed to the original Charlemagne.fr, 22% (12 requests) were made to Static.xx.fbcdn.net and 15% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Charlemagne.fr.
Page size can be reduced by 274.4 kB (45%)
607.4 kB
332.9 kB
In fact, the total size of Charlemagne.fr main page is 607.4 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. 45% of websites need less resources to load. Images take 241.1 kB which makes up the majority of the site volume.
Potential reduce by 33.0 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 33.0 kB or 75% of the original size.
Potential reduce by 13.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. Charlemagne images are well optimized though.
Potential reduce by 143.3 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 143.3 kB or 69% of the original size.
Potential reduce by 84.4 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. Charlemagne.fr needs all CSS files to be minified and compressed as it can save up to 84.4 kB or 73% of the original size.
Number of requests can be reduced by 24 (49%)
49
25
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Charlemagne. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
charlemagne.fr
1554 ms
wp-emoji-release.min.js
154 ms
slideshow.css
169 ms
styles.css
172 ms
front.css
170 ms
css
66 ms
genericons.css
342 ms
style.css
324 ms
jquery.js
458 ms
jquery-migrate.min.js
253 ms
front.js
252 ms
itro-scripts.js
337 ms
all.js
270 ms
slideshow.js
359 ms
jquery.form.min.js
351 ms
scripts.js
361 ms
functions.js
367 ms
wp-embed.min.js
486 ms
cropped-banniere-en-tete.jpg
379 ms
Affiche-lIle-O-fromage-201x300.jpg
367 ms
Saint-valentin-Ros%C3%A9-brut-300x134.jpg
377 ms
Affiche-web-300x212.jpg
367 ms
boutique-2.jpg
500 ms
like.php
312 ms
like.php
320 ms
like.php
342 ms
1bHRUMxmJHoup12DnI9XmQ.woff
310 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
321 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
322 ms
7DI7Kjvwfuz8m3ExKe6m-Q.woff
321 ms
VqvVqv1mv0Gr1Gr9Frul7xuyp+V8XvqnTyb1UoNRm4Af+FsAGNAEuwCFBYsQEBjlmxRgYrWCGwEFlLsBRSWCGwgFkdsAYrXFhZsBQrAAAAAVLP0T8AAA==
2 ms
257 ms
xd_arbiter.php
391 ms
xd_arbiter.php
595 ms
TY3MhkXpWJ-.js
538 ms
LVx-xkvaJ0b.png
422 ms
like_box.php
105 ms
ebiMDO3r-8l.css
281 ms
jGc-59L_9lo.css
285 ms
1kPfZUdGrka.js
356 ms
Yuj_Y8xNH2C.js
420 ms
Mpe38fuBVZ2.js
349 ms
n8qIhCw3vMx.js
351 ms
1536492_648034818592104_2004804219_n.jpg
427 ms
1623192_672384356157150_1717622728_n.jpg
554 ms
11960162_10207564332733525_5025393069857485138_n.jpg
679 ms
556458_4227854691580_281602060_n.jpg
635 ms
11222532_10208330193118183_1566665876491786716_n.jpg
673 ms
12239675_535007833333532_716830124532942796_n.jpg
670 ms
12742762_1264286393587139_563225030526886348_n.jpg
629 ms
10450149_348392112024675_4372442039287281644_n.jpg
684 ms
wL6VQj7Ab77.png
72 ms
s7jcwEQH7Sx.png
71 ms
VXcANLwwL5J.js
69 ms
AmlxWlqMvlv.js
134 ms
charlemagne.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
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.
charlemagne.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
charlemagne.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Charlemagne.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 Charlemagne.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.
charlemagne.fr
Open Graph data is detected on the main page of Charlemagne. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: