Powered by https://sitedoctor.peoplentools.com ()
health report : https://yakyetitoursandtrekking.com/
examined at : 25-04-16 08:08:51
follow recommendations of this health report to keep your site healthy
Powered by https://sitedoctor.peoplentools.com ()
examined at : 25-04-16 08:08:51
follow recommendations of this health report to keep your site healthy
Yak & Yeti Tours & Trekking Pvt. Ltd – Explore Nepal with us
Your page title does not exceed 60 characters. It's fine.
Your site do not have any meta description.
Your site do not have any meta keyword.
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Trek | 22 | 1.598 % | No |
| Tour | 20 | 1.452 % | No |
| Kathmandu | 15 | 1.089 % | No |
| Day | 14 | 1.017 % | No |
| tour | 12 | 0.871 % | No |
| Trekking | 11 | 0.799 % | No |
| journey | 11 | 0.799 % | No |
| Everest | 10 | 0.726 % | No |
| Base | 10 | 0.726 % | No |
| Camp | 10 | 0.726 % | No |
| Annapurna | 9 | 0.654 % | No |
| Days | 9 | 0.654 % | No |
| Reviews | 8 | 0.581 % | No |
| Tours | 8 | 0.581 % | No |
| adventure | 7 | 0.508 % | No |
| offers | 7 | 0.508 % | No |
| Yak | 7 | 0.508 % | No |
| Yeti | 7 | 0.508 % | No |
| NA | 7 | 0.508 % | No |
| Heritage | 6 | 0.436 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Base Camp | 10 | 0.726 % | No |
| Day Tour | 10 | 0.726 % | No |
| Camp Trek | 8 | 0.581 % | No |
| Yak Yeti | 7 | 0.508 % | No |
| Full Day | 6 | 0.436 % | No |
| Yeti Tours | 6 | 0.436 % | No |
| in a | 6 | 0.436 % | No |
| Everest Base | 5 | 0.363 % | No |
| of the | 5 | 0.363 % | No |
| journey through | 5 | 0.363 % | No |
| NA From | 5 | 0.363 % | No |
| Region Trekking | 4 | 0.29 % | No |
| Trek Everest | 4 | 0.29 % | No |
| Day Kathmandu | 4 | 0.29 % | No |
| on an | 4 | 0.29 % | No |
| Tours Trekking | 4 | 0.29 % | No |
| offers a | 4 | 0.29 % | No |
| the birthplace | 4 | 0.29 % | No |
| birthplace of | 4 | 0.29 % | No |
| a day | 4 | 0.29 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Base Camp Trek | 8 | 0.581 % | No |
| Yak Yeti Tours | 6 | 0.436 % | No |
| Everest Base Camp | 5 | 0.363 % | No |
| Camp Trek Everest | 4 | 0.29 % | No |
| Yeti Tours Trekking | 4 | 0.29 % | No |
| the birthplace of | 4 | 0.29 % | No |
| in a day | 4 | 0.29 % | No |
| Days NA From | 4 | 0.29 % | No |
| Ghorepani Poonhill Annapurna | 3 | 0.218 % | No |
| Full Day Kathmandu | 3 | 0.218 % | No |
| Day Kathmandu Sightseeing | 3 | 0.218 % | No |
| 7 Heritage Full | 3 | 0.218 % | No |
| Heritage Full Day | 3 | 0.218 % | No |
| Full Day Tour | 3 | 0.218 % | No |
| Chandragiri Day Tour | 3 | 0.218 % | No |
| Bhaktapur Day Tour | 3 | 0.218 % | No |
| Tour Embark on | 3 | 0.218 % | No |
| Embark on an | 3 | 0.218 % | No |
| journey through the | 3 | 0.218 % | No |
| 40 Get it | 3 | 0.218 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Everest Base Camp Trek | 4 | 0.29 % | No |
| Base Camp Trek Everest | 4 | 0.29 % | No |
| Yak Yeti Tours Trekking | 4 | 0.29 % | No |
| Full Day Kathmandu Sightseeing | 3 | 0.218 % | No |
| 7 Heritage Full Day | 3 | 0.218 % | No |
| Heritage Full Day Tour | 3 | 0.218 % | No |
| Tour Embark on an | 3 | 0.218 % | No |
| 40 Get it now | 3 | 0.218 % | No |
| 3 Days NA From | 3 | 0.218 % | No |
| Gokyo Ri And Everest | 2 | 0.145 % | No |
| Ri And Everest Base | 2 | 0.145 % | No |
| And Everest Base Camp | 2 | 0.145 % | No |
| Camp Trek Everest Base | 2 | 0.145 % | No |
| Trek Everest Base Camp | 2 | 0.145 % | No |
| Camp Trek Everest Three | 2 | 0.145 % | No |
| Trek Everest Three Pass | 2 | 0.145 % | No |
| Everest Three Pass Trek | 2 | 0.145 % | No |
| Base Camp Trek Annapurna | 2 | 0.145 % | No |
| Ghorepani Poonhill Annapurna Trek | 2 | 0.145 % | No |
| kathmandu Outskirt Tour – | 2 | 0.145 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://yakyetitoursandtrekking.com/?sitemap.xml
1377
Text/HTML Ratio Test : 29%
Your site have robot.txt
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.
Links of your site are SEO friendly.
Site failed plain text email test.5plain text email found.
Page have doc type.
Your site have 4 images without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is disabled.
Your site have 21 inline css.
Your site have 7 internal css.
Site failed micro data schema test.
| SL | Host | Class | TTL | Type | PRI | Target | IP |
|---|---|---|---|---|---|---|---|
| 1 | yakyetitoursandtrekking.com | IN | 14400 | A | 69.10.54.26 | ||
| 2 | yakyetitoursandtrekking.com | IN | 21600 | NS | ns2.techkarmi.com | ||
| 3 | yakyetitoursandtrekking.com | IN | 21600 | NS | ns1.techkarmi.com | ||
| 4 | yakyetitoursandtrekking.com | IN | 14400 | MX | 0 | yakyetitoursandtrekking.com |
Site failed IP canonicalization test.
Site passed URL canonicalization test.
<link rel="canonical" href="https://mywebsite.com/home" /><link rel="canonical" href="https://www.mywebsite.com/home" />
Aggregates all network requests and groups them by typeLearn More
Potential savings of 2,050 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 28 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
74 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.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 1,371 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
40 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 2,815 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 152 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 8,383 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
50 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
859 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 6 KiB
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
30 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
Aggregates all network requests and groups them by typeLearn More
Potential savings of 510 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 270 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
71 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.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 536 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
220 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,197 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 153 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 16,059 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
50 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
859 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 6 KiB
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
20 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