2.9 sec in total
432 ms
1.9 sec
507 ms
Welcome to francepizza.fr homepage info - get ready to check Francepizza best content for France right away, or after learning these important things about francepizza.fr
Bienvenue chez Francepizza.fr, le portail de la pizza et de la restauration italienne et son magazine France Pizza dédié à l’actualité de la pizza.
Visit francepizza.frWe analyzed Francepizza.fr page load time and found that the first response time was 432 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
francepizza.fr performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value7.4 s
4/100
25%
Value6.4 s
40/100
10%
Value250 ms
84/100
30%
Value2.769
0/100
15%
Value9.9 s
27/100
10%
432 ms
280 ms
283 ms
284 ms
289 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 68% of them (65 requests) were addressed to the original Francepizza.fr, 26% (25 requests) were made to Pub.francepizza.fr and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (752 ms) belongs to the original domain Francepizza.fr.
Page size can be reduced by 131.6 kB (30%)
439.4 kB
307.8 kB
In fact, the total size of Francepizza.fr main page is 439.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. 30% of websites need less resources to load. Images take 293.4 kB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 9.8 kB, which is 19% 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 41.9 kB or 83% of the original size.
Potential reduce by 31.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. Obviously, Francepizza needs image optimization as it can save up to 31.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 19.6 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 19.6 kB or 41% of the original size.
Potential reduce by 39.0 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. Francepizza.fr needs all CSS files to be minified and compressed as it can save up to 39.0 kB or 82% of the original size.
Number of requests can be reduced by 23 (25%)
92
69
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Francepizza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
francepizza.fr
432 ms
structure.css
280 ms
redactionnel.css
283 ms
menu.css
284 ms
slide.css
289 ms
style.css
286 ms
jquery.superbox.css
287 ms
magnific-popup.css
371 ms
stylesMenu.css
372 ms
jquery.min.js
6 ms
slide.js
392 ms
jquery.superbox-min.js
392 ms
jquery.magnific-popup.min.js
469 ms
jquery.cookie.js
392 ms
bgHeader.jpg
186 ms
ga.js
82 ms
afr.php
383 ms
afr.php
366 ms
afr.php
356 ms
afr.php
352 ms
afr.php
360 ms
afr.php
372 ms
afr.php
520 ms
afr.php
517 ms
afr.php
514 ms
btnLogin.png
129 ms
logoPizzaFr.png
217 ms
cadreNewsletter.png
126 ms
titreNewsletter.png
124 ms
abonne.jpg
124 ms
cadreForum2.png
190 ms
titreForum.png
221 ms
flech_jaune.png
221 ms
btnFormNewsletter.png
215 ms
bgSousMenu.png
217 ms
home.gif
356 ms
mag_off.gif
356 ms
actu_off.gif
358 ms
forum_off.gif
358 ms
expert_off.gif
359 ms
guide_fournisseur_off.gif
360 ms
annonces_off.gif
479 ms
evenements_off.gif
478 ms
recettes_off.gif
493 ms
bg_submenu.gif
491 ms
bg_search.gif
512 ms
bt_search.gif
512 ms
imgDecouvrerMag2015.jpg
749 ms
titre_actuUne_475.gif
568 ms
news_1229.jpg
584 ms
filet_rond_gris.png
586 ms
titre_actuFrance_475.gif
605 ms
news_1228.jpg
615 ms
news_1227.jpg
657 ms
news_1226.jpg
675 ms
news_1225.jpg
677 ms
news_1224.jpg
697 ms
news_1223.jpg
707 ms
news_1222.jpg
752 ms
news_1221.jpg
737 ms
__utm.gif
25 ms
__utm.gif
17 ms
news_1220.jpg
719 ms
collect
71 ms
news_1219.jpg
688 ms
titre_cherchePizza_475.gif
702 ms
bt_form_home.jpg
726 ms
bottom_cherchePizza_475.gif
725 ms
titre_nouveaute_195.gif
686 ms
prod_628.jpg
665 ms
titre_concepts_195.gif
690 ms
concept_45.jpg
703 ms
titre_experts_195.gif
720 ms
dossier_53.jpg
720 ms
5b66dcb432f1a6ff3852fa0de6e207a6.png
392 ms
lg.php
174 ms
ac3c01decf5ca0aae8bedbd1ca1eecbb.jpg
448 ms
lg.php
285 ms
dcb402c8cd694b7f1b4fca6d75d9791d.gif
538 ms
lg.php
281 ms
6f1e6ee7aeacc3e918c8f7e1eb23f464.gif
575 ms
lg.php
383 ms
4ca5ee7f5e07c76f59a8a4e9701c3ed2.jpg
540 ms
lg.php
522 ms
titre_recettes_195.gif
610 ms
recette_282.jpg
634 ms
titre_formations_195.gif
641 ms
mni_formations.jpg
655 ms
bgFooter.png
686 ms
lg.php
501 ms
6e0345df71fbdda31d57f9fe960db814.gif
570 ms
lg.php
472 ms
lg.php
473 ms
3da89c96678b9a956910eb3b30655f51.jpg
466 ms
lg.php
485 ms
francepizza.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
francepizza.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
francepizza.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Francepizza.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 Francepizza.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.
francepizza.fr
Open Graph description is not detected on the main page of Francepizza. 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: