4.4 sec in total
336 ms
3.8 sec
207 ms
Click here to check amazing Paris Notaires content. Otherwise, check out these important facts you probably never knew about paris.notaires.fr
Chambre de Paris
Visit paris.notaires.frWe analyzed Paris.notaires.fr page load time and found that the first response time was 336 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
paris.notaires.fr performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value7.8 s
3/100
25%
Value7.3 s
29/100
10%
Value90 ms
99/100
30%
Value0.288
42/100
15%
Value8.0 s
43/100
10%
336 ms
421 ms
81 ms
1117 ms
85 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 91% of them (108 requests) were addressed to the original Paris.notaires.fr, 8% (10 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Paris.notaires.fr.
Page size can be reduced by 172.5 kB (23%)
745.4 kB
572.9 kB
In fact, the total size of Paris.notaires.fr main page is 745.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. 60% of websites need less resources to load. Images take 271.0 kB which makes up the majority of the site volume.
Potential reduce by 89.7 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 89.7 kB or 80% of the original size.
Potential reduce by 27.2 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. Paris Notaires images are well optimized though.
Potential reduce by 39.9 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 39.9 kB or 18% of the original size.
Potential reduce by 15.7 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. Paris.notaires.fr needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 11% of the original size.
Number of requests can be reduced by 90 (87%)
103
13
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Paris Notaires. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
paris.notaires.fr
336 ms
paris.notaires.fr
421 ms
fr
81 ms
fr
1117 ms
eu_cookie_compliance.script.js
85 ms
align.module.css
163 ms
fieldgroup.module.css
235 ms
container-inline.module.css
237 ms
clearfix.module.css
235 ms
details.module.css
243 ms
hidden.module.css
243 ms
item-list.module.css
243 ms
js.module.css
312 ms
nowrap.module.css
313 ms
position-container.module.css
314 ms
progress.module.css
323 ms
reset-appearance.module.css
323 ms
resize.module.css
324 ms
sticky-header.module.css
389 ms
system-status-counter.css
388 ms
system-status-report-counters.css
389 ms
system-status-report-general-info.css
402 ms
tablesort.module.css
402 ms
tree-child.module.css
402 ms
views.module.css
466 ms
views_slideshow_cycle.css
465 ms
eu_cookie_compliance.bare.css
467 ms
efd.css
481 ms
ds-2col-fluid.css
482 ms
paragraphs.unpublished.css
799 ms
youtube.responsive.css
543 ms
controls_text.css
543 ms
style.css
697 ms
smartselect.css
563 ms
bootstrap-datetimepicker.min.css
564 ms
style.css
774 ms
Logo_mini_NDGP.png
719 ms
logo.svg
743 ms
jquery.min.js
720 ms
nodelist.foreach.js
790 ms
element.matches.js
722 ms
object.assign.js
718 ms
css.escape.js
646 ms
es6-promise.auto.min.js
646 ms
underscore-min.js
648 ms
once.min.js
644 ms
jquery.once.min.js
644 ms
fr_rbkxLUnv1eKVcIBMvJtNdVx3tDf5DWp0pUzlaSHUlCs.js
652 ms
drupalSettingsLoader.js
609 ms
drupal.js
626 ms
drupal.init.js
627 ms
index.umd.min.js
618 ms
jquery.number.js
633 ms
progress.js
651 ms
progress.js
604 ms
jquery.once.bc.js
625 ms
loadjs.min.js
623 ms
responsive_image.ajax.js
614 ms
ajax.js
630 ms
ajax.js
653 ms
affix.js
614 ms
alert.js
623 ms
button.js
624 ms
carousel.js
611 ms
collapse.js
629 ms
dropdown.js
592 ms
modal.js
610 ms
tooltip.js
601 ms
popover.js
603 ms
css
41 ms
scrollspy.js
449 ms
tab.js
470 ms
transition.js
490 ms
jquery.sticky.js
488 ms
script.js
449 ms
jquery.smartselect.js
453 ms
notaires-smartselect.js
433 ms
moment.min.js
788 ms
fr.js
420 ms
bootstrap-datetimepicker.min.js
439 ms
drupal.bootstrap.js
442 ms
attributes.js
442 ms
theme.js
442 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
24 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
24 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf
35 ms
js.cookie.min.js
493 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexYMUdjFnmg.ttf
76 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexYMUdjFnmg.ttf
184 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexYMUdjFnmg.ttf
51 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexYMUdjFnmg.ttf
68 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexYMUdjFnmg.ttf
155 ms
eu_cookie_compliance.min.js
506 ms
gtm.js
483 ms
gtag.js
465 ms
gtag.ajax.js
463 ms
popover.js
513 ms
tooltip.js
525 ms
cinp_cookies.js
506 ms
cinp_consent_to_gtm.js
488 ms
cinp_cookies_popin.js
468 ms
views_slideshow.js
526 ms
json2.js
546 ms
jquery.cycle.all.js
527 ms
views_slideshow_cycle.js
502 ms
jquery.hoverIntent.js
474 ms
fontawesome-webfont.woff
691 ms
icomoon.ttf
544 ms
immo-2024.jpg
703 ms
inp-slider.jpg
602 ms
themes-homepage.png
511 ms
ID_CNP_white.svg
662 ms
ID_CNHS-92-white.svg
658 ms
essonne-white.png
576 ms
Logo2018-CdN77-white.svg
636 ms
versaille-white.png
632 ms
cookie.svg
649 ms
paris.notaires.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
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
paris.notaires.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
Browser errors were logged to the console
Page has valid source maps
paris.notaires.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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paris.notaires.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 Paris.notaires.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.
paris.notaires.fr
Open Graph data is detected on the main page of Paris Notaires. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: