Page summary

Summary

Metric	Value
Page metrics
Performance Score	90
Total Page Transfer Size	93.4 KB
Requests	6
Timing metrics
TTFB [median]	117 ms
First Paint [median]	237 ms
Fully Loaded [median]	743 ms
Google Web Vitals
TTFB [median]	117 ms
First Contentful Paint (FCP) [median]	237 ms
Largest Contentful Paint (LCP) [median]	416 ms
Cumulative Layout Shift (CLS) [median]	0.00
Interaction To Next Paint (INP) [median]	240 ms
Total Blocking Time [median]	53 ms
Max Potential FID [median]	99 ms
CPU metrics
CPU long tasks [median]	2
CPU longest task duration	157 ms
CPU last long task happens at	571 ms
Visual Metrics
First Visual Change [median]	266 ms
Speed Index [median]	433 ms
Visual Complete 85% [median]	433 ms
Visual Complete 99% [median]	466 ms
Last Visual Change [median]	466 ms

Timings Summary

Waterfall

Run 2 SpeedIndex median

Video

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.3 sCPU Long Task duration 157 ms

0.5 sFirst Contentful Paint 416 msLCP <H1> 416 msFirst Visual Change 433 msVisual Complete 85% 433 msVisual Complete 95% 433 msHeading 433 msDOM Content Loaded Time 444 msLast Visual Change 466 msVisual Complete 99% 466 ms

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 8.1.1.

Coach score

• Total score 89
• Performance score 90
• Privacy score 88
• Best practice score 86

Performance advice (90)

Show/hide details

Title	Advice	Score
Have a fast largest contentful paint (largestContentfulPaint)	You can add fetchPriority="high" to the image to increase the load priority in Chrome.	95
Description: Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance.
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 5 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 90.1 kB the next access.	50
Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.
Offenders: https://www.antiquites-en-france.com/__ovh/common/img/misconfig.png https://www.antiquites-en-france.com/__ovh/common/img/icon-book.png https://www.antiquites-en-france.com/__ovh/common/font/lato-light-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-regular-webfont.woff https://www.antiquites-en-france.com/__ovh/common/img/favicon.ico
Always compress text content (compressAssets)	The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	90
Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
Offenders: URL Transfer size Content size https://www.antiquites-en-france.com/ 5.4 KB 5.3 KB
The favicon should be small and cacheable (favicon)	The favicon size is 12 kB bytes. That's quite big, can you make it smaller? The favicon has no cache time.	0
Description: It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type.
Offenders: https://www.antiquites-en-france.com/__ovh/common/img/favicon.ico
Avoid too many fonts (fewFonts)	The page has 2 font requests. Do you really need them? What value does the fonts give the user?	80
Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive.
Offenders: https://www.antiquites-en-france.com/__ovh/common/font/lato-light-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-regular-webfont.woff
Avoid missing and error requests (responseOk)	The page has 1 error response. The page has 1 response with code 404.	90
Description: Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it.
Offenders: https://www.antiquites-en-france.com/

Best practice advice (86)

Show/hide details

Title	Advice	Score
Declare a doctype in your document (doctype)	The page is missing a doctype. Please use <!DOCTYPE html>.	0
Description: The <!DOCTYPE> declaration is not an HTML tag; it is an instruction to the web browser about what version of HTML the page is written in.
Meta description (metaDescription)	The page is missing a meta description.	0
Description: Use a page description to make the page more relevant to search engines.
Avoid unnecessary headers (unnecessaryHeaders)	There are 6 responses that sets both a max-age and expires header. There are 6 responses that sets a pragma no-cache header (that is a request header). There are 6 responses that sets a server header.	82
Description: Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
Offenders: https://www.antiquites-en-france.com/ https://www.antiquites-en-france.com/ https://www.antiquites-en-france.com/ https://www.antiquites-en-france.com/__ovh/common/img/misconfig.png https://www.antiquites-en-france.com/__ovh/common/img/misconfig.png https://www.antiquites-en-france.com/__ovh/common/img/misconfig.png https://www.antiquites-en-france.com/__ovh/common/img/icon-book.png https://www.antiquites-en-france.com/__ovh/common/img/icon-book.png https://www.antiquites-en-france.com/__ovh/common/img/icon-book.png https://www.antiquites-en-france.com/__ovh/common/font/lato-light-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-light-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-light-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-regular-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-regular-webfont.woff https://www.antiquites-en-france.com/__ovh/common/font/lato-regular-webfont.woff https://www.antiquites-en-france.com/__ovh/common/img/favicon.ico https://www.antiquites-en-france.com/__ovh/common/img/favicon.ico https://www.antiquites-en-france.com/__ovh/common/img/favicon.ico

Privacy advice (88)

Show/hide details

Title	Advice	Score
Use a good Content-Security-Policy header to make sure you you avoid Cross Site Scripting (XSS) attacks. (contentSecurityPolicyHeader)	Set a Content-Security-Policy header to make sure you are not open for Cross Site Scripting (XSS) attacks. You can start with setting a Content-Security-Policy-Report-Only header, that will only report the violation, not stop the download.	0
Description: Content Security Policy is delivered via a HTTP response header, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed. https://scotthelme.co.uk/content-security-policy-an-introduction/.
Offenders: https://www.antiquites-en-france.com/
Set a referrer-policy header to make sure you do not leak user information. (referrerPolicyHeader)	Set a referrer-policy header to make sure you do not leak user information.	0
Description: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.
Offenders: https://www.antiquites-en-france.com/

Page info

Page info
Title	Site not installed
Width	1350
Height	886
DOM elements	48
Avg DOM depth	5
Max DOM depth	8
Iframes	0
Script tags	0
Local storage	0 b
Session storage	0 b
Network Information API	4g

Technologies used to build the page.

Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.

Wappalyzer didn't find any information.

Data from run 2

Visual Metrics

Browser Metrics

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element type	H1
Element/tag	<h1></h1>
Render time	416 ms
Element render delay	298 ms
TTFB	117 ms
Resource delay	0 ms
Resource load duration	0 ms
Elements that needed recalculate style before LCP	273
Time spent in recalculate style before LCP	18.821 ms
Load time	0 ms
Size (width*height)	11988
DOM path
div:eq(3) > div:eq(0) > div > div > div > div > h1> div:eq(3) > div:eq(0) > div > div > div > div > h1>

The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

Detected Cumulative Layout Shift

No layout shift detected.

Interaction to Next Paint

Interaction to Next Paint (INP) is a metric that try to measure responsiveness. It's useful if you are testing user journeys. Read more about Interaction to Next Paint.

Long Animation Frames

Read more about the Long Animation Frames API here here.

The top 10 longest animation frames entries

Server timings

There are no Server Timings.

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

Visual Elements

PageXray

How the page is built.

Largest assets on the page (by transfer size)

Requests and sizes per content type

Data per domain

Expires and last modified statistics

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

Render blocking requests

Render blocking information directly from Chrome.

Render information

CPU

Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

Long Tasks

Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

CPU last long task happened at 571 ms

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Time spent per request

CPU time spent

Third party

Third party requests categorised by Third party web version 0.26.2.

Third party requests and tools

First party requests and sizes per content type

Calculated using .*antiquites-en-france.* (use --firstParty to configure).

Third party requests and sizes per content type

Axe

Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.10.2. Read more about axe-core .

Violations

Median number of violations for all the runs. Check each individual run to see all the violations.