Follow recommendations of this health report to keep your site healthy
Examined at : 2022-07-06 13:34:25
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Top | 20 | 6.309 % | No |
June | 10 | 3.155 % | No |
success | 6 | 1.893 % | Yes |
computer | 5 | 1.577 % | No |
skills | 5 | 1.577 % | No |
generate | 5 | 1.577 % | No |
money | 5 | 1.577 % | Yes |
Favourites | 5 | 1.577 % | No |
Grand | 4 | 1.262 % | No |
City | 3 | 0.946 % | No |
ten | 3 | 0.946 % | No |
Business | 3 | 0.946 % | No |
World's | 3 | 0.946 % | No |
Great | 3 | 0.946 % | No |
Atlantic | 3 | 0.946 % | No |
Greatest | 3 | 0.946 % | No |
Inspirational | 2 | 0.631 % | No |
age | 2 | 0.631 % | No |
March | 2 | 0.631 % | No |
real | 2 | 0.631 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Top 10 | 17 | 5.363 % | No |
in 2022 | 8 | 2.524 % | No |
What are | 6 | 1.893 % | No |
are the | 6 | 1.893 % | No |
Best Top | 6 | 1.893 % | No |
skills generate | 5 | 1.577 % | No |
money in | 5 | 1.577 % | No |
generate money | 5 | 1.577 % | No |
2022 Best | 5 | 1.577 % | No |
10 computer | 5 | 1.577 % | No |
computer skills | 5 | 1.577 % | No |
Grand success | 4 | 1.262 % | No |
World's Top | 3 | 0.946 % | No |
the World's | 3 | 0.946 % | No |
Favourites What | 3 | 0.946 % | No |
Atlantic City | 3 | 0.946 % | No |
2022 What | 3 | 0.946 % | No |
In The | 3 | 0.946 % | No |
10 Most | 3 | 0.946 % | No |
25 2022 | 3 | 0.946 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Best Top 10 | 6 | 1.893 % | No |
What are the | 6 | 1.893 % | No |
skills generate money | 5 | 1.577 % | No |
money in 2022 | 5 | 1.577 % | No |
generate money in | 5 | 1.577 % | No |
Top 10 computer | 5 | 1.577 % | No |
10 computer skills | 5 | 1.577 % | No |
computer skills generate | 5 | 1.577 % | No |
the World's Top | 3 | 0.946 % | No |
World's Top 10 | 3 | 0.946 % | No |
Top 10 Most | 3 | 0.946 % | No |
Favourites What are | 3 | 0.946 % | No |
25 2022 Best | 3 | 0.946 % | No |
June 25 2022 | 3 | 0.946 % | No |
2022 Best Top | 3 | 0.946 % | No |
are the World's | 3 | 0.946 % | No |
2022 What are | 3 | 0.946 % | No |
singer March 23 | 2 | 0.631 % | No |
Top 10 dogs | 2 | 0.631 % | No |
American singer March | 2 | 0.631 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
10 computer skills generate | 5 | 1.577 % | No |
Best Top 10 computer | 5 | 1.577 % | No |
generate money in 2022 | 5 | 1.577 % | No |
skills generate money in | 5 | 1.577 % | No |
computer skills generate money | 5 | 1.577 % | No |
Top 10 computer skills | 5 | 1.577 % | No |
June 25 2022 Best | 3 | 0.946 % | No |
2022 What are the | 3 | 0.946 % | No |
2022 Best Top 10 | 3 | 0.946 % | No |
World's Top 10 Most | 3 | 0.946 % | No |
the World's Top 10 | 3 | 0.946 % | No |
are the World's Top | 3 | 0.946 % | No |
What are the World's | 3 | 0.946 % | No |
Favourites What are the | 3 | 0.946 % | No |
in Atlantic City New | 2 | 0.631 % | No |
… Favourites What are | 2 | 0.631 % | No |
2022 Best king of | 2 | 0.631 % | No |
Best king of pop | 2 | 0.631 % | No |
what are Top 10 | 2 | 0.631 % | No |
are Top 10 real | 2 | 0.631 % | 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 | blogspot.l.googleusercontent.com | IN | 298 | A | 142.251.12.132 | ||
2 | grandsuccess786.blogspot.com | IN | 3600 | CNAME | blogspot.l.googleusercontent.com | ||
3 | blogspot.l.googleusercontent.com | IN | 300 | AAAA | 2404:6800:4003:c11::84 |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://grandsuccess786.blogspot.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 570 |
request size | 161 | filetime | -1 |
ssl verify result | 0 | redirect count | 0 |
total time | 0.829494 | namelookup time | 0.012426 |
connect time | 0.01394 | pretransfer time | 0.149734 |
size upload | 0 | size download | 247099 |
speed download | 297891 | speed upload | 0 |
download content length | -1 | upload content length | 0 |
starttransfer time | 0.639153 | redirect time | 0 |
redirect url | primary ip | 142.251.12.132 | |
certinfo | primary port | 443 | |
local ip | 139.99.33.102 | local port | 60896 |
38 requests • 872 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 150 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
14 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 320 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
3990 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
420 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.7 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 97 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 181 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 872 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
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 More
317 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 1,110 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
37 requests • 871 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 20 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
14 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
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
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 217 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 871 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
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 More
317 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