Latest Performance Report for:
http://courstoujours.be/
GTmetrix Grade
Performance
100%Structure
99%Web Vitals
Largest Contentful PaintLCP
345msTotal Blocking TimeTBT
0msCumulative Layout ShiftCLS
0Speed Visualization
0s
0.1s
0.1s
0.1s
0.2s
0.2s
0.3s
0.3s
0.3s
0.4s
Top Issues
These audits are identified as the top issues impacting your performance.
Focus on these audits first
These audits likely have the largest impact on your page performance.
Structure audits do not directly affect your Performance Score, but improving the audits seen here can help as a starting point for overall performance gains.
See all Structure auditsPage Details
Your page content is broken down into the following:
357ms
Fully Loaded Time
Total Page Size - 89.0KB
Total Page Requests - 10
More from GTmetrix
Additional tips and suggestions based on your page analysis.
Need help with optimization?
Find a developer with our partner Fiverr to optimize your performance
Tips and Tricks for using GTmetrix
Shortcuts, guides and pointers for making the most out of GTmetrix
Understand and assess Waterfall Charts
Learn to identify and point out potential issues in your page load
Access Analysis Options with a GTmetrix account
Block ads, capture video, change connection speeds, etc
Performance Metrics
The following metrics are generated using Lighthouse Performance data.
First Contentful Paint
How quickly content like text or images are painted onto your page.
A good user experience is 0.9s or less. Learn more.
Time to Interactive
How long it takes for your page to become fully interactive.
A good user experience is 2.5s or less. Learn more.
Speed Index
How quickly the contents of your page are visibly populated.
A good user experience is 1.3s or less. Learn more.
Total Blocking Time
How much time is blocked by scripts during your page loading process.
A good user experience is 150ms or less. Learn more.
Largest Contentful Paint
How long it takes for the largest element of content (e.g. a hero image) to be painted on your page.
A good user experience is 1.2s or less. Learn more.
Cumulative Layout Shift
How much your page's layout shifts as it loads.
A good user experience is a score of 0.1 or less. Learn more.
Browser Timings
These timings are milestones reported by the browser.
Redirect Duration
Connection Duration
Backend Duration
Time to First Byte (TTFB)
First Paint
DOM Interactive Time
DOM Content Loaded Time
Onload Time
Fully Loaded Time
| Impact | Audit | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Low | Use a Content Delivery Network (CDN) | 4 resources found | |||||||||||||||||||||||
|
CDNs can give an equally fast web experience to your users across the globe. Learn how to improve this
|
|||||||||||||||||||||||||
| Low | Avoid enormous network payloads LCP | Total size was 89.0KB | |||||||||||||||||||||||
|
Large network payloads cost users real money and are highly correlated with long load times. Learn how to improve this
|
|||||||||||||||||||||||||
| Low | Avoid multiple page redirects FCP LCP | Potential savings of 27ms | |||||||||||||||||||||||
|
Redirects introduce additional delays before the page can be loaded. Learn how to improve this
|
|||||||||||||||||||||||||
| Low | Ensure text remains visible during webfont load FCP LCP | 2 fonts found | |||||||||||||||||||||||
|
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn how to improve this
|
|||||||||||||||||||||||||
| Low | Reduce JavaScript execution time TBT | 12ms spent executing JavaScript | |||||||||||||||||||||||
|
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to improve this
|
|||||||||||||||||||||||||
| Low | Reduce initial server response time FCP LCP | Root document took 97ms | |||||||||||||||||||||||
|
Keep the server response time for the main document short because all other requests depend on it. Learn how to improve this
|
|||||||||||||||||||||||||
| Low | Avoid chaining critical requests FCP LCP | 4 chains found | |||||||||||||||||||||||
|
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to improve thisMaximum critical path latency: 272ms Initial Navigation
|
|||||||||||||||||||||||||
| N/A | Avoid an excessive DOM size TBT | 36 elements | |||||||||||||||||||||||
|
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to improve this
|
|||||||||||||||||||||||||
| N/A | Largest Contentful Paint element LCP | 1 element found | |||||||||||||||||||||||
|
This is the largest contentful element painted within the viewport.
|
|||||||||||||||||||||||||
| N/A | Avoid large layout shifts CLS | 1 element found | |||||||||||||||||||||||
|
These DOM elements contribute most to the CLS of the page. Learn how to improve this
|
|||||||||||||||||||||||||
| N/A | Minimize main-thread work TBT | Main-thread busy for 142ms | |||||||||||||||||||||||
|
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to improve this
|
|||||||||||||||||||||||||
| N/A | User Timing marks and measures | ||||||||||||||||||||||||
|
No user timings and/or marks found. Learn more |
|||||||||||||||||||||||||
| N/A | Reduce the impact of third-party code TBT | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| Show No Impact Audits | |||||||||||||||||||||||||
| None | Avoid CSS @import FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Enable text compression FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Use a <meta name="viewport"> tag with width or initial-scale TBT | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Use video formats for animated content LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Use passive listeners to improve scrolling performance | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Properly size images | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Don't lazy load Largest Contentful Paint image | LCP was lazy loaded | |||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Serve static assets with an efficient cache policy | 0 resources found | |||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Efficiently encode images | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Eliminate render-blocking resources FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Preconnect to required origins FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Avoid document.write() | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Avoid long main-thread tasks TBT | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Preload Largest Contentful Paint image LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Reduce unused CSS FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Serve images in next-gen formats | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Avoid serving legacy JavaScript to modern browsers TBT | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Defer offscreen images | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Minify CSS FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Avoid non-composited animations CLS | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Enable Keep-Alive FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Minify JavaScript FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Avoid unload event listeners | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Remove duplicate modules in JavaScript bundles TBT | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Combine images using CSS sprites FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Preload key requests FCP LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Reduce unused JavaScript LCP | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Lazy load third-party resources with facades TBT | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
| None | Use HTTP/2 for all resources | ||||||||||||||||||||||||
|
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||
What do these audits mean?
These audits are best practices established by Google to help build websites for optimal front-end performance.
Each audit is assessed based on your adherence to them and ordered by the most likely impact to your page's performance.
Note that Structure audits do not directly affect your Performance score, however addressing them can serve as good starting point to improve page load times overall. Additionally, some of the audits are correlated and thus, fixing one audit may affect others.
Learn about all the auditsNeed optimization help?
We've written various guides and articles to help you improve your page performance:
Need Assistance?
We can recommend partners to further assist you with optimizing your site. Contact us and we'll point you in the right direction.
Need expert help?
Find a developer with our partner Fiverr to optimize your performanceWaterfall Chart
A request-by-request visualization of the page load. Learn how to read a waterfall chart.
Page Load Video
See your page load with videos
Logged in users can record a video of this page loading and pinpoint exactly where bottlenecks and stoppages occur.
Slow playback up to 4x to visualize loading behaviour
Jump to major milestones like First Paint and Onload
Download and embed videos
Report History
A series of graphs to keep track of your page performance over time. Learn how to use the History Graphs.
Page metrics
- 1d
- 1w
- 1m
- 3m
- 6m
- 1y
- All
Page sizes and request counts
- 1d
- 1w
- 1m
- 3m
- 6m
- 1y
- All
Page scores
- 1d
- 1w
- 1m
- 3m
- 6m
- 1y
- All
This history graph has more reports available
Get more data points in your history when you log in.
Log in to get more historical data, add notes, and download your history data
Login Sign up for free!History Date Range
We're only displaying the first 3 reports, but more are available.
A higher resolution (at least 840px wide) is required to display the Report History graphs
Tip: rotating your device into landscape mode may give you the necessary resolution to view the graphs.