Powered by https://sitedoctor.peoplentools.com ()
health report : https://www.aydoo.fr/
examined at : 24-05-13 12:41:24
follow recommendations of this health report to keep your site healthy
Powered by https://sitedoctor.peoplentools.com ()
examined at : 24-05-13 12:41:24
follow recommendations of this health report to keep your site healthy
Comparateur assurances pas cher en ligne
Your page title does not exceed 60 characters. It's fine.
Aydoo est un comparateur assurances innovant, comparateur indépendant il ne se fait pas payer par les assureurs qu'il compare
Your meta description does not exceed 150 characters. It's fine.
Your site do not have any meta keyword.
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| de | 72 | 5.252 % | No |
| d’assurance | 45 | 3.282 % | No |
| les | 42 | 3.063 % | No |
| vous | 28 | 2.042 % | No |
| des | 25 | 1.823 % | No |
| en | 25 | 1.823 % | No |
| la | 24 | 1.751 % | No |
| à | 24 | 1.751 % | No |
| votre | 15 | 1.094 % | No |
| le | 14 | 1.021 % | No |
| comparateurs | 14 | 1.021 % | No |
| pour | 14 | 1.021 % | No |
| police | 12 | 0.875 % | No |
| comparateur | 12 | 0.875 % | No |
| une | 11 | 0.802 % | No |
| vos | 11 | 0.802 % | No |
| besoins | 10 | 0.729 % | No |
| – | 10 | 0.729 % | No |
| assurance | 9 | 0.656 % | No |
| il | 8 | 0.584 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| comparateurs d’assurance | 13 | 0.948 % | No |
| que vous | 11 | 0.802 % | No |
| la police | 10 | 0.729 % | No |
| comparateur d’assurance | 10 | 0.729 % | No |
| vos besoins | 9 | 0.656 % | No |
| de la | 9 | 0.656 % | No |
| un comparateur | 8 | 0.584 % | No |
| en ligne | 7 | 0.511 % | No |
| d’assurance et | 6 | 0.438 % | No |
| les comparateurs | 6 | 0.438 % | No |
| une assurance | 5 | 0.365 % | No |
| il est | 5 | 0.365 % | No |
| et de | 5 | 0.365 % | No |
| comparer les | 5 | 0.365 % | No |
| vous avez | 5 | 0.365 % | No |
| garanties et | 5 | 0.365 % | No |
| et les | 5 | 0.365 % | No |
| trouver la | 4 | 0.292 % | No |
| compagnies d’assurance | 4 | 0.292 % | No |
| sur le | 4 | 0.292 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| un comparateur d’assurance | 6 | 0.438 % | No |
| les comparateurs d’assurance | 5 | 0.365 % | No |
| les différentes offres | 4 | 0.292 % | No |
| à vos besoins | 4 | 0.292 % | No |
| Une fois que | 4 | 0.292 % | No |
| fois que vous | 4 | 0.292 % | No |
| que vous avez | 4 | 0.292 % | No |
| prendre en compte | 4 | 0.292 % | No |
| de la police | 4 | 0.292 % | No |
| sur le marché | 3 | 0.219 % | No |
| trouver la police | 3 | 0.219 % | No |
| la police d’assurance | 3 | 0.219 % | No |
| comparer les différentes | 3 | 0.219 % | No |
| utiliser un comparateur | 3 | 0.219 % | No |
| les détails de | 3 | 0.219 % | No |
| d’assurance il est | 3 | 0.219 % | No |
| comparateurs d’assurance vous | 3 | 0.219 % | No |
| d’assurance vous permettent | 3 | 0.219 % | No |
| vos besoins en | 3 | 0.219 % | No |
| besoins en assurance | 3 | 0.219 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Une fois que vous | 4 | 0.292 % | No |
| fois que vous avez | 4 | 0.292 % | No |
| comparer les différentes offres | 3 | 0.219 % | No |
| comparateurs d’assurance vous permettent | 3 | 0.219 % | No |
| vos besoins en assurance | 3 | 0.219 % | No |
| une liste de devis | 3 | 0.219 % | No |
| liste de devis personnalisés | 3 | 0.219 % | No |
| les différentes offres en | 3 | 0.219 % | No |
| les garanties et les | 3 | 0.219 % | No |
| – Une fois que | 3 | 0.219 % | No |
| disponibles sur le marché | 2 | 0.146 % | No |
| sur le marché il | 2 | 0.146 % | No |
| il peut être difficile | 2 | 0.146 % | No |
| peut être difficile de | 2 | 0.146 % | No |
| être difficile de s’y | 2 | 0.146 % | No |
| difficile de s’y retrouver | 2 | 0.146 % | No |
| Je compare les offres | 2 | 0.146 % | No |
| trouver la police d’assurance | 2 | 0.146 % | No |
| la police d’assurance parfaite | 2 | 0.146 % | No |
| police d’assurance parfaite pour | 2 | 0.146 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://www.aydoo.fr/sitemap_index.xml
1371
Text/HTML Ratio Test : 4%
Your site have robot.txt
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" /> directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a> if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
Links of your site are SEO friendly.
Site passed plain text email test. No plain text email found.
Page have doc type.
Your site have 2 images without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is disabled.
Your site have 4 inline css.
Your site have 10 internal css.
Site failed micro data schema test.
| SL | Host | Class | TTL | Type | PRI | Target | IP |
|---|---|---|---|---|---|---|---|
| 1 | www.aydoo.fr | IN | 3600 | A | 87.98.161.117 |
Site failed IP canonicalization test.
Site passed URL canonicalization test.
<link rel="canonical" href="https://mywebsite.com/home" /><link rel="canonical" href="https://www.mywebsite.com/home" />
Aggregates all network requests and groups them by typeLearn More
Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Potential savings of 67 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Potential savings of 18 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 13 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 869 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
2.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
30 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 More
226 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More
Aggregates all network requests and groups them by typeLearn More
Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Potential savings of 64 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 13 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 1,109 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
31 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 More
226 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More