Follow recommendations of this health report to keep your site healthy
Examined at : 2022-05-10 19:52:15
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Tour | 19 | 1.857 % | No |
Island | 12 | 1.173 % | No |
Learn | 11 | 1.075 % | No |
Pigeon | 11 | 1.075 % | No |
Fishing | 10 | 0.978 % | No |
– | 8 | 0.782 % | No |
Sri | 8 | 0.782 % | No |
Watching | 8 | 0.782 % | No |
Whale | 8 | 0.782 % | No |
Trincomalee | 8 | 0.782 % | No |
Private | 7 | 0.684 % | No |
Romantic | 7 | 0.684 % | No |
Dinner | 7 | 0.684 % | No |
experience | 6 | 0.587 % | No |
Dolphin | 6 | 0.587 % | No |
Kind | 6 | 0.587 % | No |
Place | 6 | 0.587 % | No |
Bar | 5 | 0.489 % | No |
Restaurant | 5 | 0.489 % | No |
fish | 5 | 0.489 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Learn More | 11 | 1.075 % | No |
Pigeon Island | 11 | 1.075 % | No |
of the | 9 | 0.88 % | No |
Fishing Tour | 7 | 0.684 % | No |
Romantic Dinner | 7 | 0.684 % | No |
with us | 6 | 0.587 % | No |
My Kind | 6 | 0.587 % | No |
Private Tour | 6 | 0.587 % | No |
– Private | 6 | 0.587 % | No |
Whale Dolphin | 6 | 0.587 % | No |
Dolphin Watching | 6 | 0.587 % | No |
Enjoy the | 5 | 0.489 % | No |
Bar Restaurant | 5 | 0.489 % | No |
in Trincomalee | 5 | 0.489 % | No |
best with | 5 | 0.489 % | No |
the best | 5 | 0.489 % | No |
of Place | 5 | 0.489 % | No |
us Learn | 5 | 0.489 % | No |
Kind of | 5 | 0.489 % | No |
is a | 4 | 0.391 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Whale Dolphin Watching | 6 | 0.587 % | No |
– Private Tour | 6 | 0.587 % | No |
with us Learn | 5 | 0.489 % | No |
Enjoy the best | 5 | 0.489 % | No |
the best with | 5 | 0.489 % | No |
best with us | 5 | 0.489 % | No |
us Learn More | 5 | 0.489 % | No |
My Kind of | 5 | 0.489 % | No |
Kind of Place | 5 | 0.489 % | No |
Tour Whale Dolphin | 4 | 0.391 % | No |
of Place Bar | 3 | 0.293 % | No |
Fun Fishing Tour | 3 | 0.293 % | No |
Dolphin Watching Tour | 3 | 0.293 % | No |
Place Bar Restaurant | 3 | 0.293 % | No |
Pigeon Island Tour | 3 | 0.293 % | No |
available as a | 2 | 0.196 % | No |
also available as | 2 | 0.196 % | No |
Learn More Romantic | 2 | 0.196 % | No |
looking for a | 2 | 0.196 % | No |
is also available | 2 | 0.196 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
with us Learn More | 5 | 0.489 % | No |
best with us Learn | 5 | 0.489 % | No |
the best with us | 5 | 0.489 % | No |
Enjoy the best with | 5 | 0.489 % | No |
My Kind of Place | 5 | 0.489 % | No |
Tour Whale Dolphin Watching | 4 | 0.391 % | No |
of Place Bar Restaurant | 3 | 0.293 % | No |
Whale Dolphin Watching Tour | 3 | 0.293 % | No |
Kind of Place Bar | 3 | 0.293 % | No |
combination of Sri Lankan | 2 | 0.196 % | No |
Private Tour Trolling Fishing | 2 | 0.196 % | No |
– Private Tour Trolling | 2 | 0.196 % | No |
Watching – Private Tour | 2 | 0.196 % | No |
Tour Trolling Fishing – | 2 | 0.196 % | No |
Trolling Fishing – Private | 2 | 0.196 % | No |
Fishing – Private Tour | 2 | 0.196 % | No |
perfect combination of Sri | 2 | 0.196 % | No |
and European class and | 2 | 0.196 % | No |
of Sri Lankan excellence | 2 | 0.196 % | No |
Sri Lankan excellence and | 2 | 0.196 % | 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 | trincovisit.com | IN | 300 | A | 172.67.198.179 | ||
2 | trincovisit.com | IN | 300 | A | 104.21.50.7 | ||
3 | trincovisit.com | IN | 86400 | NS | nero.ns.cloudflare.com | ||
4 | trincovisit.com | IN | 86400 | NS | frida.ns.cloudflare.com | ||
5 | trincovisit.com | IN | 14400 | MX | 5 | mx1.hostinger.it | |
6 | trincovisit.com | IN | 14400 | MX | 10 | mx2.hostinger.it | |
7 | trincovisit.com | IN | 300 | AAAA | 2606:4700:3037::6815:3207 | ||
8 | trincovisit.com | IN | 300 | AAAA | 2606:4700:3036::ac43:c6b3 |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://trincovisit.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 1877 |
request size | 266 | filetime | -1 |
ssl verify result | 0 | redirect count | 1 |
total time | 1.272355 | namelookup time | 0.012793 |
connect time | 0.014643 | pretransfer time | 0.248857 |
size upload | 0 | size download | 187013 |
speed download | 146981 | speed upload | 0 |
download content length | 0 | upload content length | 0 |
starttransfer time | 0.916362 | redirect time | 0.351679 |
redirect url | primary ip | 104.21.50.7 | |
certinfo | primary port | 443 | |
local ip | 139.99.33.102 | local port | 40388 |
80 requests • 1,768 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 1,650 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 35 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
57 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
8160 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.6 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 12 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 63 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,768 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
3.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
25 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
871 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
77 requests • 1,711 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 460 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 35 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
57 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.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
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 63 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,711 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
25 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
871 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