3.3 sec in total
280 ms
2.8 sec
249 ms
Visit pfg.fr now to see the best up-to-date PFG content for France and also check out these interesting facts you probably never knew about pfg.fr
PFG vous accompagne avant, pendant et après les obsèques : démarches administratives, organisation de la cérémonie, crémation ou inhumation, enterrement civil ou religieux.
Visit pfg.frWe analyzed Pfg.fr page load time and found that the first response time was 280 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pfg.fr performance score
name
value
score
weighting
Value3.4 s
39/100
10%
Value5.1 s
24/100
25%
Value6.7 s
36/100
10%
Value700 ms
43/100
30%
Value0.01
100/100
15%
Value10.6 s
23/100
10%
280 ms
1122 ms
373 ms
196 ms
498 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 90% of them (63 requests) were addressed to the original Pfg.fr, 3% (2 requests) were made to Stats.g.doubleclick.net and 3% (2 requests) were made to Storelocator.ogf.fr. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pfg.fr.
Page size can be reduced by 664.4 kB (49%)
1.4 MB
688.0 kB
In fact, the total size of Pfg.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. 50% of websites need less resources to load. Javascripts take 567.7 kB which makes up the majority of the site volume.
Potential reduce by 101.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 101.9 kB or 81% of the original size.
Potential reduce by 46.5 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. PFG images are well optimized though.
Potential reduce by 432.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 432.3 kB or 76% of the original size.
Potential reduce by 83.6 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. Pfg.fr needs all CSS files to be minified and compressed as it can save up to 83.6 kB or 85% of the original size.
Number of requests can be reduced by 21 (32%)
66
45
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PFG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
pfg.fr
280 ms
www.pfg.fr
1122 ms
base.css
373 ms
jquery.superbox.css
196 ms
jquery-1.5.2.min.js
498 ms
jquery.superbox.js
297 ms
jquery.carouFredSel-5.0.7.js
397 ms
jquery.validate.js
482 ms
base.js
360 ms
storelocator.js
399 ms
storelocator_pfg.js
470 ms
tc_PFG_3.js
463 ms
WebResource.axd
347 ms
blank.js
348 ms
tc_PFG_1.js
295 ms
init.js
189 ms
ScriptResource.axd
106 ms
ScriptResource.axd
103 ms
bg_trame.png
139 ms
picto_loupe.png
143 ms
logo_pfg.png
142 ms
prevoyance-obseques.jpg
140 ms
solution-testament-obseques.jpg
138 ms
demarches-urgence-pfg.jpg
141 ms
obseques-pas.jpg
189 ms
apres-obseques.jpg
190 ms
essentiels2016-pfg.jpg
211 ms
produits-pfg.jpg
207 ms
services-pfg.jpg
207 ms
avis_deces_web.jpg
219 ms
Conseils_redaction_avis_deces.jpg
294 ms
commander-fleurs-deuil.jpg
285 ms
organisation-obseques.jpg
303 ms
testament-obseques.jpg
306 ms
monuments-fleurs.jpg
308 ms
accompagnement-pfg.jpg
415 ms
accompagnement-conseiller-pfg.jpg
468 ms
essentiel-pfg.jpg
477 ms
prevoir-obseques.jpg
404 ms
organiser-obseques.jpg
402 ms
services-produits-pfg.png
498 ms
nouvelle-collection-monuments.jpg
503 ms
Offre-du-moment-Essentiels.jpg
505 ms
Monuments.jpg
516 ms
guide-etapes-deuil.jpg
560 ms
valeur-engagement-pfg.jpg
568 ms
fondation-pfg.jpg
595 ms
PFG-FILM2_TV.jpg
699 ms
206420_10_0.woff
739 ms
dc.js
37 ms
PageLocalisation.aspx
612 ms
bg_nav.png
604 ms
pictos.png
613 ms
bg_ss_nav.png
645 ms
border_deco.png
683 ms
__utm.gif
57 ms
privacy_5.js
59 ms
AgencesAleatoires
339 ms
206420_D_0.woff
713 ms
bg_map_france.png
628 ms
degrade_01.png
660 ms
filet_bottom.png
668 ms
filets_deco.png
699 ms
picto_caddi.png
716 ms
privacyHit.php
202 ms
filets_separate_02.png
667 ms
new_bg_contact.png
703 ms
pictos_transverse.png
701 ms
privacyHit.php
216 ms
150 ms
pfg.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
pfg.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
pfg.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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pfg.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 Pfg.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.
pfg.fr
Open Graph description is not detected on the main page of PFG. 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: