(Took us an average of 1.4 seconds to load)
|Table of Contents|
|Minor HTML issues found on homepage|
|How can this website be improved?|
|Websites linked to|
Basic information for barjouville.fr
Email or contact page: [email protected]
Social media profiles:
Using HTTPS: Yes 🙂
HTML errors found on homepage
<link href="https://fonts.googleapis.com/css?family=Montserrat:400,700|Material+Icons" rel="stylesheet">
Bad value “https://fonts.googleapis.com/css?family=Montserrat:400,700|Material+Icons” for attribute “href” on element “link”: Illegal character in query: “|” is not allowed.
ckground-color: ; }header.intr
CSS: “background-color”: Parse Error.
Bad start tag in “p” in “noscript” in “head”.
="" /></p></noscript> <
Stray end tag “noscript”.
Stray end tag “head”.
></head><body style="position: relative; min-height: 100%; top: 0px;"><hea
Start tag “body” seen but an element of the same type was already open.
OVERALL SITE SPEED: AVERAGE (details below)
CUMULATIVE LAYOUT SHIFT SCORE: AVERAGE. Have you ever been reading an article online when something suddenly changes on the page? Without warning, the text moves, and you’ve lost your place. Or even worse: you’re about to tap a link or a button, but in the instant before your finger lands, BOOM – the link moves, and you end up clicking something else! This is a measure of how often this is happening on your website.
FIRST CONTENTFUL PAINT MS SCORE: AVERAGE. This measures the time taken for the first thing on your website to load when a visitor goes there.
FIRST INPUT DELAY MS SCORE: AVERAGE. How long it takes for your website to react if the user interacts with it in some way, such as clicking a link or button.
LARGEST CONTENTFUL PAINT MS SCORE: AVERAGE. Measures how long the main part of the website takes to load.
Opportunities for improvement
Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time. [Learn more](https://web.dev/uses-responsive-images/).
Potential savings of 2,014 KiB
Avoid multiple page redirects: Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects/).
Potential savings of 230 ms
Enable text compression: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression/).
Potential savings of 42 KiB
Efficiently encode images: Optimized images load faster and consume less cellular data. [Learn more](https://web.dev/uses-optimized-images/).
Potential savings of 2,955 KiB
Remove unused CSS: Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. [Learn more](https://web.dev/unused-css-rules/).
Potential savings of 81 KiB
Potential savings of 66 KiB
Potential savings of 13 KiB
Minify CSS: Minifying CSS files can reduce network payload sizes. [Learn more](https://web.dev/unminified-css/).
Potential savings of 6 KiB
Eliminate render-blocking resources: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
Potential savings of 650 ms
Potential savings of 374 KiB
Serve images in next-gen formats: Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images/).
Potential savings of 5,060 KiB
Defer offscreen images: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
Potential savings of 776 KiB