Tools & Wizards About Us
public.geofoncier.fr screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

public.geofoncier.fr

Géofoncier Public

Page Load Speed

3.6 sec in total

First Response

435 ms

Resources Loaded

2.8 sec

Page Rendered

309 ms

public.geofoncier.fr screenshot

About Website

Click here to check amazing Public Geofoncier content for France. Otherwise, check out these important facts you probably never knew about public.geofoncier.fr

Consultez le plan cadastral d'une parcelle ou le plan de bornage d'un terrain sur Geofoncier.fr, un service de l'Ordre des géomètres-experts.

Visit public.geofoncier.fr

Key Findings

We analyzed Public.geofoncier.fr page load time and found that the first response time was 435 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

public.geofoncier.fr performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value32.7 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value3,220 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.648

9/100

15%

TTI (Time to Interactive)

Value27.8 s

0/100

10%

Network Requests Diagram

public.geofoncier.fr

435 ms

gtm.js

98 ms

tarteaucitron.js

136 ms

icon

76 ms

all.min.css

219 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 93% of them (77 requests) were addressed to the original Public.geofoncier.fr, 2% (2 requests) were made to Cdn.jsdelivr.net and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Public.geofoncier.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.5 kB (2%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Public.geofoncier.fr main page is 2.2 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. 55% of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 14.2 kB

  • Original 18.5 kB
  • After minification 14.9 kB
  • After compression 4.4 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 3.6 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 14.2 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.1 kB
  • After minification 2.1 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. Public Geofoncier images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 21.3 kB

  • Original 2.1 MB
  • After minification 2.1 MB
  • After compression 2.0 MB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 4.1 kB

  • Original 77.9 kB
  • After minification 77.9 kB
  • After compression 73.8 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. Public.geofoncier.fr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 74 (91%)

Requests Now

81

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Geofoncier. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

public.geofoncier.fr

public.geofoncier.fr

435 ms

gtm.js

gtm.js

98 ms

tarteaucitron.js

tarteaucitron.js

136 ms

icon

icon

76 ms

all.min.css

all.min.css

219 ms

all.min.js

all.min.js

897 ms

key.js

key.js

412 ms

jquery.min.js

jquery.min.js

515 ms

jquery-ui.min.js

jquery-ui.min.js

649 ms

jquery.highlight.js

jquery.highlight.js

413 ms

splide.min.js

splide.min.js

62 ms

splide.min.css

splide.min.css

73 ms

materialize.min.css

materialize.min.css

514 ms

materialize.min.js

materialize.min.js

703 ms

datatables.min.css

datatables.min.css

517 ms

datatables-search-highlight.css

datatables-search-highlight.css

604 ms

datatables.min.js

datatables.min.js

1362 ms

rowsGroup.js

rowsGroup.js

611 ms

datatables-search-highlight.min.js

datatables-search-highlight.min.js

698 ms

proj4.js

proj4.js

803 ms

turf.min.js

turf.min.js

1036 ms

togeojson.js

togeojson.js

792 ms

leaflet.css

leaflet.css

799 ms

leaflet.js

leaflet.js

1038 ms

easy-button.js

easy-button.js

1032 ms

leaflet_control_custom.js

leaflet_control_custom.js

1033 ms

NonTiledLayer.js

NonTiledLayer.js

1034 ms

leaflet.extra-markers.min.css

leaflet.extra-markers.min.css

1038 ms

leaflet.extra-markers.min.js

leaflet.extra-markers.min.js

1038 ms

sogefi-datatable.min.css

sogefi-datatable.min.css

1040 ms

sogefi-leaflet.min.css

sogefi-leaflet.min.css

1079 ms

sogefi.css

sogefi.css

1079 ms

leaflet.geometryutil.js

leaflet.geometryutil.js

1087 ms

sogefi.js

sogefi.js

1086 ms

leaflet-map.js

leaflet-map.js

1120 ms

loader.js

loader.js

1171 ms

form_modal.js

form_modal.js

1172 ms

sidebar.min.css

sidebar.min.css

1178 ms

sidebar.min.js

sidebar.min.js

1178 ms

autocomplete.css

autocomplete.css

1213 ms

layers.css

layers.css

1263 ms

matomo.js

matomo.js

47 ms

legend.css

legend.css

1108 ms

matomo.php

matomo.php

473 ms

minimap.css

minimap.css

1021 ms

leaflet.fullscreen.css

leaflet.fullscreen.css

877 ms

leaflet-measure.css

leaflet-measure.css

909 ms

Leaflet.Coordinates-0.1.5.css

Leaflet.Coordinates-0.1.5.css

1257 ms

color.css

color.css

1257 ms

carto.css

carto.css

1253 ms

form_sogefi.css

form_sogefi.css

1167 ms

geofoncier.css

geofoncier.css

1161 ms

autocomplete.js

autocomplete.js

1128 ms

xmlToJson.js

xmlToJson.js

1076 ms

wicket.js

wicket.js

1073 ms

wicket-leaflet.js

wicket-leaflet.js

984 ms

vectorStyle.js

vectorStyle.js

974 ms

cadastre_geofoncier_sogefi.js

cadastre_geofoncier_sogefi.js

968 ms

queryBuilder.js

queryBuilder.js

745 ms

ficheConsultExport.js

ficheConsultExport.js

744 ms

layers.js

layers.js

748 ms

geofoncier_sogefi.js

geofoncier_sogefi.js

741 ms

wms-capabilities.js

wms-capabilities.js

740 ms

addLayer.js

addLayer.js

740 ms

jquery.quicksearch.min.js

jquery.quicksearch.min.js

740 ms

minimap.min.js

minimap.min.js

739 ms

Leaflet.fullscreen.min.js

Leaflet.fullscreen.min.js

714 ms

leaflet-measure.min.js

leaflet-measure.min.js

707 ms

Leaflet.Coordinates-0.1.5.min.js

Leaflet.Coordinates-0.1.5.min.js

702 ms

L.Control.ZoomLabel.js

L.Control.ZoomLabel.js

696 ms

layers_geofoncier.js

layers_geofoncier.js

697 ms

model.js

model.js

663 ms

onglet_annuaire.js

onglet_annuaire.js

613 ms

onglet_localiser.js

onglet_localiser.js

630 ms

onglet_historique.js

onglet_historique.js

695 ms

controller.js

controller.js

695 ms

locate.png

locate.png

664 ms

layers_r.png

layers_r.png

613 ms

geometre.svg

geometre.svg

613 ms

histo.svg

histo.svg

661 ms

legend.svg

legend.svg

663 ms

tarteaucitron.css

tarteaucitron.css

97 ms

tarteaucitron.en.js

tarteaucitron.en.js

115 ms

Accessibility Review

public.geofoncier.fr accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

High

Image elements do not have [alt] attributes

Best Practices

public.geofoncier.fr best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

public.geofoncier.fr SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Public.geofoncier.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 Public.geofoncier.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.

Social Sharing Optimization

public.geofoncier.fr

Open Graph description is not detected on the main page of Public Geofoncier. 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: