Follow recommendations of this health report to keep your site healthy
Examined at : 2021-06-16 16:28:17
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Chocolates | 8 | 3.042 % | No |
Orders | 8 | 3.042 % | No |
Account | 6 | 2.281 % | No |
Fire? | 6 | 2.281 % | No |
Sign | 4 | 1.521 % | No |
EAT | 4 | 1.521 % | No |
Flaming | 4 | 1.521 % | No |
EXPERIENCE | 4 | 1.521 % | No |
CHOCOLATE | 4 | 1.521 % | No |
chocolate | 4 | 1.521 % | No |
Store | 4 | 1.521 % | No |
Custom | 4 | 1.521 % | No |
beans | 3 | 1.141 % | No |
cocoa | 3 | 1.141 % | No |
Home | 3 | 1.141 % | Yes |
website | 3 | 1.141 % | No |
cookies | 3 | 1.141 % | No |
Bean | 3 | 1.141 % | No |
Bar | 3 | 1.141 % | No |
ITDON’T | 2 | 0.76 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
the Chocolates | 6 | 2.281 % | No |
on Fire? | 6 | 2.281 % | No |
Are the | 6 | 2.281 % | No |
Chocolates on | 6 | 2.281 % | No |
Custom Orders | 4 | 1.521 % | No |
About Store | 4 | 1.521 % | No |
JUST EAT | 4 | 1.521 % | No |
My Account | 4 | 1.521 % | No |
Orders My | 4 | 1.521 % | No |
CHOCOLATE EXPERIENCE | 4 | 1.521 % | No |
EAT CHOCOLATE | 4 | 1.521 % | No |
Fire? Are | 3 | 1.141 % | No |
to Bar | 3 | 1.141 % | No |
cocoa beans | 3 | 1.141 % | No |
Bar About | 3 | 1.141 % | No |
Home Custom | 3 | 1.141 % | No |
Orders Bean | 3 | 1.141 % | No |
Bean to | 3 | 1.141 % | No |
Sign In | 2 | 0.76 % | No |
EXPERIENCE ITDON’T | 2 | 0.76 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Are the Chocolates | 6 | 2.281 % | No |
the Chocolates on | 6 | 2.281 % | No |
Chocolates on Fire? | 6 | 2.281 % | No |
EAT CHOCOLATE EXPERIENCE | 4 | 1.521 % | No |
JUST EAT CHOCOLATE | 4 | 1.521 % | No |
Orders My Account | 4 | 1.521 % | No |
on Fire? Are | 3 | 1.141 % | No |
to Bar About | 3 | 1.141 % | No |
Bean to Bar | 3 | 1.141 % | No |
Orders Bean to | 3 | 1.141 % | No |
Custom Orders Bean | 3 | 1.141 % | No |
Home Custom Orders | 3 | 1.141 % | No |
Bar About Store | 3 | 1.141 % | No |
Fire? Are the | 3 | 1.141 % | No |
Account Sign out | 2 | 0.76 % | No |
CHOCOLATE EXPERIENCE IT | 2 | 0.76 % | No |
Account Orders My | 2 | 0.76 % | No |
DON’T JUST EAT | 2 | 0.76 % | No |
ITDON’T JUST EAT | 2 | 0.76 % | No |
EXPERIENCE ITDON’T JUST | 2 | 0.76 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
the Chocolates on Fire? | 6 | 2.281 % | No |
Are the Chocolates on | 6 | 2.281 % | No |
JUST EAT CHOCOLATE EXPERIENCE | 4 | 1.521 % | No |
on Fire? Are the | 3 | 1.141 % | No |
Home Custom Orders Bean | 3 | 1.141 % | No |
Fire? Are the Chocolates | 3 | 1.141 % | No |
to Bar About Store | 3 | 1.141 % | No |
Orders Bean to Bar | 3 | 1.141 % | No |
Custom Orders Bean to | 3 | 1.141 % | No |
Bean to Bar About | 3 | 1.141 % | No |
Chocolates on Fire? Are | 3 | 1.141 % | No |
ITDON’T JUST EAT CHOCOLATE | 2 | 0.76 % | No |
My Account Sign out | 2 | 0.76 % | No |
DON’T JUST EAT CHOCOLATE | 2 | 0.76 % | No |
Account Orders My Account | 2 | 0.76 % | No |
EAT CHOCOLATE EXPERIENCE IT | 2 | 0.76 % | No |
Signed in as fillergodaddycom | 2 | 0.76 % | No |
EAT CHOCOLATE EXPERIENCE ITDON’T | 2 | 0.76 % | No |
CHOCOLATE EXPERIENCE ITDON’T JUST | 2 | 0.76 % | No |
EXPERIENCE ITDON’T JUST EAT | 2 | 0.76 % | 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 | Flamingchocolates.ca | IN | 3600 | A | 72.167.191.69 | ||
2 | Flamingchocolates.ca | IN | 3600 | NS | ns76.domaincontrol.com | ||
3 | Flamingchocolates.ca | IN | 3600 | NS | ns75.domaincontrol.com | ||
4 | Flamingchocolates.ca | IN | 3600 | MX | 20 | mx2.zoho.com | |
5 | Flamingchocolates.ca | IN | 3600 | MX | 10 | mx.zoho.com | |
6 | Flamingchocolates.ca | IN | 3600 | MX | 30 | mx3.zoho.com |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://flamingchocolates.ca/ | content type | text/html;charset=utf-8 |
http code | 200 | header size | 2451 |
request size | 310 | filetime | -1 |
ssl verify result | 0 | redirect count | 1 |
total time | 0.34879 | namelookup time | 0.122402 |
connect time | 0.154785 | pretransfer time | 0.20008 |
size upload | 0 | size download | 124354 |
speed download | 357339 | speed upload | 0 |
download content length | -1 | upload content length | -1 |
starttransfer time | 0.304765 | redirect time | 0.112312 |
redirect url | primary ip | 72.167.191.69 | |
certinfo | primary port | 443 | |
local ip | 68.65.123.107 | local port | 53306 |
http version | 3 | protocol | 2 |
ssl verifyresult | 0 | scheme | HTTPS |
appconnect time us | 126081 | connect time us | 154785 |
namelookup time us | 122402 | pretransfer time us | 200080 |
redirect time us | 112312 | starttransfer time us | 304765 |
total time us | 348790 |
48 requests • 649 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
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
0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 330 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
2583 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.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 179 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
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 649 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
2 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
352 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 630 ms
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
50 requests • 562 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
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
0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 20 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
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.1 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 87 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
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 562 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
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
2 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
354 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 190 ms
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