Follow recommendations of this health report to keep your site healthy
Examined at : 2023-01-30 11:43:56
Score
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| € | 101 | 12.242 % | No |
| mit | 98 | 11.879 % | No |
| und | 84 | 10.182 % | No |
| Pizza | 41 | 4.97 % | No |
| Salat | 27 | 3.273 % | No |
| Champignons | 23 | 2.788 % | No |
| Zwiebeln | 22 | 2.667 % | No |
| Sahnesauce | 18 | 2.182 % | No |
| Rigatoni | 15 | 1.818 % | No |
| Salami | 13 | 1.576 % | No |
| Schinken | 12 | 1.455 % | No |
| Spaghetti | 12 | 1.455 % | No |
| gemischter | 11 | 1.333 % | No |
| Calzone | 11 | 1.333 % | No |
| Mozzarella | 10 | 1.212 % | No |
| Tomaten | 10 | 1.212 % | No |
| Tortellini | 10 | 1.212 % | No |
| Hähnchenstreifen | 9 | 1.091 % | No |
| Spinat | 9 | 1.091 % | No |
| Thunfisch | 9 | 1.091 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| € Pizza | 39 | 4.727 % | No |
| 950 € | 30 | 3.636 % | No |
| 850 € | 18 | 2.182 % | No |
| € Salat | 14 | 1.697 % | No |
| € Rigatoni | 13 | 1.576 % | No |
| 1000 € | 13 | 1.576 % | No |
| Salat mit | 12 | 1.455 % | No |
| gemischter Salat | 11 | 1.333 % | No |
| mit Schinken | 10 | 1.212 % | No |
| € Spaghetti | 10 | 1.212 % | No |
| und Sahnesauce | 10 | 1.212 % | No |
| € Calzone | 9 | 1.091 % | No |
| 800 € | 9 | 1.091 % | No |
| und TomatenSahnesauce | 8 | 0.97 % | No |
| roten Zwiebeln | 8 | 0.97 % | No |
| mit Thunfisch | 7 | 0.848 % | No |
| mit Champignons | 7 | 0.848 % | No |
| Champignons und | 7 | 0.848 % | No |
| und Mozzarella | 6 | 0.727 % | No |
| mit Rinderhackfleisch | 6 | 0.727 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| 950 € Pizza | 25 | 3.03 % | No |
| gemischter Salat mit | 11 | 1.333 % | No |
| 1000 € Calzone | 8 | 0.97 % | No |
| 850 € Rigatoni | 5 | 0.606 % | No |
| Champignons Broccoli und | 5 | 0.606 % | No |
| scharf mit scharfer | 5 | 0.606 % | No |
| 850 € Pizza | 5 | 0.606 % | No |
| Salat mit Schinken | 4 | 0.485 % | No |
| 900 € Pizza | 4 | 0.485 % | No |
| mit scharfer Salami | 4 | 0.485 % | No |
| 850 € Spaghetti | 4 | 0.485 % | No |
| Mozzarella 950 € | 4 | 0.485 % | No |
| und Mozzarella 950 | 4 | 0.485 % | No |
| und Sahnesauce 850 | 4 | 0.485 % | No |
| TomatenSahnesauce 850 € | 4 | 0.485 % | No |
| und TomatenSahnesauce 850 | 4 | 0.485 % | No |
| Sahnesauce 850 € | 4 | 0.485 % | No |
| scharfer Salami und | 3 | 0.364 % | No |
| TomatenSahnesauce 1000 € | 3 | 0.364 % | No |
| und TomatenSahnesauce 1000 | 3 | 0.364 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| und Mozzarella 950 € | 4 | 0.485 % | No |
| gemischter Salat mit Schinken | 4 | 0.485 % | No |
| und TomatenSahnesauce 850 € | 4 | 0.485 % | No |
| Mozzarella 950 € Pizza | 4 | 0.485 % | No |
| und Sahnesauce 850 € | 4 | 0.485 % | No |
| scharf mit scharfer Salami | 4 | 0.485 % | No |
| und TomatenSahnesauce 1000 € | 3 | 0.364 % | No |
| und Käse 750 € | 3 | 0.364 % | No |
| und Sahnesauce 800 € | 3 | 0.364 % | No |
| Paprika 950 € Pizza | 3 | 0.364 % | No |
| und Paprika 950 € | 3 | 0.364 % | No |
| Champignons Broccoli und Sahnesauce | 3 | 0.364 % | No |
| und Sahnesauce 950 € | 3 | 0.364 % | No |
| TomatenSahnesauce 850 € Rigatoni | 3 | 0.364 % | No |
| und Rucola 950 € | 2 | 0.242 % | No |
| Mare mit Meeresfrüchten und | 2 | 0.242 % | No |
| Rucola 950 € Pizza | 2 | 0.242 % | No |
| mit Tomatensauce 750 € | 2 | 0.242 % | No |
| mit Hähnchenstreifen roten Zwiebeln | 2 | 0.242 % | No |
| Champignons und Paprika 950 | 2 | 0.242 % | No |
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.
| SL | Host | Class | TTL | Type | PRI | Target | IP |
| 1 | pizzeriapaparazzibamberg.de | IN | 300 | A | 52.48.64.111 | ||
| 2 | pizzeriapaparazzibamberg.de | IN | 300 | A | 54.171.90.223 | ||
| 3 | pizzeriapaparazzibamberg.de | IN | 300 | NS | ns1.takeaway.com | ||
| 4 | pizzeriapaparazzibamberg.de | IN | 300 | NS | ns2.takeaway.com | ||
| 5 | www.pizzeriapaparazzibamberg.de | IN | 295 | CNAME | pizzeriapaparazzibamberg.de |
<link rel="canonical" href="https://mywebsite.com/home" /><link rel="canonical" href="https://www.mywebsite.com/home" />| url | https://www.pizzeriapaparazzibamberg.de/ | content type | text/html; charset=utf-8 |
| http code | 200 | header size | 285 |
| request size | 167 | filetime | -1 |
| ssl verify result | 20 | redirect count | 0 |
| total time | 1.682488 | namelookup time | 0.335541 |
| connect time | 0.535108 | pretransfer time | 0.86813 |
| size upload | 0 | size download | 192705 |
| speed download | 114535 | speed upload | 0 |
| download content length | 192705 | upload content length | 0 |
| starttransfer time | 1.194867 | redirect time | 0 |
| redirect url | primary ip | 54.171.90.223 | |
| certinfo | primary port | 443 | |
| local ip | 208.91.198.131 | local port | 60780 |
| http version | 2 | protocol | 2 |
| ssl verifyresult | 0 | scheme | HTTPS |
| appconnect time us | 1403163 | connect time us | 535108 |
| namelookup time us | 335541 | pretransfer time us | 868130 |
| redirect time us | 0 | starttransfer time us | 1194867 |
| total time us | 1682488 |
41 requests • 2,638 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 3,520 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
Potential savings of 349 KiB
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
36 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 210 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
7620 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
230 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.2 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 524 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 30 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 10 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 2,638 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
20 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
960 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
42 requests • 2,701 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 1,070 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
Potential savings of 349 KiB
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
37 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
40 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
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 31 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 10 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 2,701 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
21 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
960 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