Follow recommendations of this health report to keep your site healthy
Examined at : 2022-01-16 21:50:30
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Gnome | 191 | 12.197 % | No |
cart | 162 | 10.345 % | No |
Add | 162 | 10.345 % | No |
Garden | 55 | 3.512 % | No |
Gnomes | 47 | 3.001 % | No |
Read | 28 | 1.788 % | No |
– | 11 | 0.702 % | No |
Select | 10 | 0.639 % | No |
options | 9 | 0.575 % | No |
Female | 7 | 0.447 % | No |
Plush | 7 | 0.447 % | No |
Halloween | 7 | 0.447 % | No |
Statue | 7 | 0.447 % | No |
Male | 7 | 0.447 % | No |
Swing | 7 | 0.447 % | No |
Bird | 7 | 0.447 % | No |
Hat | 7 | 0.447 % | No |
Beer | 6 | 0.383 % | No |
Eating | 5 | 0.319 % | No |
Outdoor | 5 | 0.319 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
to cart | 162 | 10.345 % | No |
Add to | 162 | 10.345 % | No |
2497 Add | 50 | 3.193 % | No |
cart Gnome | 43 | 2.746 % | No |
Garden Gnome | 38 | 2.427 % | No |
Read more | 28 | 1.788 % | No |
2797 Add | 26 | 1.66 % | No |
Gnome with | 25 | 1.596 % | No |
Gnome on | 24 | 1.533 % | No |
Gnome 2497 | 21 | 1.341 % | No |
2997 Add | 20 | 1.277 % | No |
3497 Add | 19 | 1.213 % | No |
more Gnome | 17 | 1.086 % | No |
cart Garden | 13 | 0.83 % | No |
6000 Read | 12 | 0.766 % | No |
1497 Add | 11 | 0.702 % | No |
Garden Gnomes | 10 | 0.639 % | No |
Select options | 9 | 0.575 % | No |
Gnome 3497 | 8 | 0.511 % | No |
Gnome 2797 | 8 | 0.511 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Add to cart | 162 | 10.345 % | No |
2497 Add to | 50 | 3.193 % | No |
to cart Gnome | 43 | 2.746 % | No |
2797 Add to | 26 | 1.66 % | No |
2997 Add to | 20 | 1.277 % | No |
Gnome 2497 Add | 20 | 1.277 % | No |
3497 Add to | 19 | 1.213 % | No |
Read more Gnome | 17 | 1.086 % | No |
to cart Garden | 13 | 0.83 % | No |
6000 Read more | 12 | 0.766 % | No |
1497 Add to | 11 | 0.702 % | No |
cart Garden Gnome | 9 | 0.575 % | No |
Gnome 2797 Add | 8 | 0.511 % | No |
Gnome 3497 Add | 8 | 0.511 % | No |
cart Gnome with | 7 | 0.447 % | No |
more Gnome on | 7 | 0.447 % | No |
Garden Gnome 3497 | 7 | 0.447 % | No |
Gnome on Swing | 6 | 0.383 % | No |
Gnomes 1497 Add | 6 | 0.383 % | No |
more Gnome with | 6 | 0.383 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
2497 Add to cart | 50 | 3.193 % | No |
Add to cart Gnome | 43 | 2.746 % | No |
2797 Add to cart | 26 | 1.66 % | No |
Gnome 2497 Add to | 20 | 1.277 % | No |
2997 Add to cart | 20 | 1.277 % | No |
3497 Add to cart | 19 | 1.213 % | No |
Add to cart Garden | 13 | 0.83 % | No |
1497 Add to cart | 11 | 0.702 % | No |
to cart Garden Gnome | 9 | 0.575 % | No |
6000 Read more Gnome | 9 | 0.575 % | No |
Gnome 2797 Add to | 8 | 0.511 % | No |
Gnome 3497 Add to | 8 | 0.511 % | No |
to cart Gnome with | 7 | 0.447 % | No |
Read more Gnome on | 7 | 0.447 % | No |
Garden Gnome 3497 Add | 7 | 0.447 % | No |
Read more Gnome with | 6 | 0.383 % | No |
Gnomes 1497 Add to | 6 | 0.383 % | No |
Add to cart The | 6 | 0.383 % | No |
2500 Add to cart | 5 | 0.319 % | No |
Gnomes 2997 Add to | 5 | 0.319 % | 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 | thegnomeshop.ca | IN | 300 | A | 104.21.10.131 | ||
2 | thegnomeshop.ca | IN | 300 | A | 172.67.131.122 | ||
3 | thegnomeshop.ca | IN | 3600 | NS | may.ns.cloudflare.com | ||
4 | thegnomeshop.ca | IN | 3600 | NS | amir.ns.cloudflare.com | ||
5 | thegnomeshop.ca | IN | 300 | MX | 0 | _dc-mx.2c9d756f858a.thegnomeshop.ca | |
6 | thegnomeshop.ca | IN | 300 | AAAA | 2606:4700:3036::6815:a83 | ||
7 | thegnomeshop.ca | IN | 300 | AAAA | 2606:4700:3031::ac43:837a |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://thegnomeshop.ca/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 990 |
request size | 133 | filetime | -1 |
ssl verify result | 0 | redirect count | 0 |
total time | 1.011929 | namelookup time | 0.000441 |
connect time | 0.050684 | pretransfer time | 0.12934 |
size upload | 0 | size download | 408581 |
speed download | 404135 | speed upload | 0 |
download content length | -1 | upload content length | -1 |
starttransfer time | 0.447362 | redirect time | 0 |
redirect url | primary ip | 104.21.10.131 | |
certinfo | primary port | 443 | |
local ip | 68.65.123.107 | local port | 38070 |
http version | 3 | protocol | 2 |
ssl verifyresult | 0 | scheme | HTTPS |
appconnect time us | 129079 | connect time us | 50684 |
namelookup time us | 441 | pretransfer time us | 129340 |
redirect time us | 0 | starttransfer time us | 447362 |
total time us | 1011929 |
182 requests • 3,234 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 2,790 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 127 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
103 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 520 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
8812 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
1,410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
Potential savings of 47 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
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 275 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 3,234 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
10.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
83 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
2,532 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
195 requests • 4,254 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 570 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 420 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
116 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 160 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
470 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
Potential savings of 47 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 360 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 273 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 4,254 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
83 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
2,531 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