Follow recommendations of this health report to keep your site healthy
Examined at : 2021-02-17 14:15:26
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Publishers | 6 | 4.615 % | No |
Advertisers | 6 | 4.615 % | No |
days | 4 | 3.077 % | No |
Login | 4 | 3.077 % | No |
Home | 2 | 1.538 % | Yes |
publishers | 2 | 1.538 % | No |
total | 2 | 1.538 % | No |
Impressions | 2 | 1.538 % | No |
Join | 2 | 1.538 % | No |
traffic | 2 | 1.538 % | No |
Ads | 2 | 1.538 % | No |
Triansh | 2 | 1.538 % | No |
user | 2 | 1.538 % | No |
advertisers | 2 | 1.538 % | No |
Clicks | 2 | 1.538 % | No |
Terms | 2 | 1.538 % | No |
signup | 2 | 1.538 % | No |
Statistic | 2 | 1.538 % | No |
Social | 2 | 1.538 % | No |
reminder | 2 | 1.538 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
30 days | 3 | 2.308 % | No |
67 Clicks | 2 | 1.538 % | No |
Terms for | 2 | 1.538 % | No |
New account | 2 | 1.538 % | No |
account Login | 2 | 1.538 % | No |
Login Password | 2 | 1.538 % | No |
Password reminder | 2 | 1.538 % | No |
Join Now | 2 | 1.538 % | No |
Triansh Ads | 2 | 1.538 % | No |
Now Login | 2 | 1.538 % | No |
Advertisers Publishers | 2 | 1.538 % | No |
last 30 | 1 | 0.769 % | No |
days Advertisers | 1 | 0.769 % | No |
Advertisers Advertisers | 1 | 0.769 % | No |
Home Advertisers | 1 | 0.769 % | No |
Advertisers get | 1 | 0.769 % | No |
get Genuine | 1 | 0.769 % | No |
Genuine high | 1 | 0.769 % | No |
high Traffic | 1 | 0.769 % | No |
Traffic with | 1 | 0.769 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
New account Login | 2 | 1.538 % | No |
account Login Password | 2 | 1.538 % | No |
Login Password reminder | 2 | 1.538 % | No |
Join Now Login | 2 | 1.538 % | No |
Home Advertisers New | 1 | 0.769 % | No |
Advertisers Advertisers get | 1 | 0.769 % | No |
the last 30 | 1 | 0.769 % | No |
last 30 days | 1 | 0.769 % | No |
30 days Advertisers | 1 | 0.769 % | No |
days Advertisers Advertisers | 1 | 0.769 % | No |
Genuine high Traffic | 1 | 0.769 % | No |
Advertisers get Genuine | 1 | 0.769 % | No |
get Genuine high | 1 | 0.769 % | No |
Traffic in the | 1 | 0.769 % | No |
high Traffic with | 1 | 0.769 % | No |
Traffic with 250 | 1 | 0.769 % | No |
with 250 USD | 1 | 0.769 % | No |
in the last | 1 | 0.769 % | No |
Clicks 30 days | 1 | 0.769 % | No |
days Traffic in | 1 | 0.769 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
New account Login Password | 2 | 1.538 % | No |
account Login Password reminder | 2 | 1.538 % | No |
Home Advertisers New account | 1 | 0.769 % | No |
Advertisers Advertisers get Genuine | 1 | 0.769 % | No |
in the last 30 | 1 | 0.769 % | No |
the last 30 days | 1 | 0.769 % | No |
last 30 days Advertisers | 1 | 0.769 % | No |
30 days Advertisers Advertisers | 1 | 0.769 % | No |
days Advertisers Advertisers get | 1 | 0.769 % | No |
get Genuine high Traffic | 1 | 0.769 % | No |
Advertisers get Genuine high | 1 | 0.769 % | No |
days Traffic in the | 1 | 0.769 % | No |
Genuine high Traffic with | 1 | 0.769 % | No |
high Traffic with 250 | 1 | 0.769 % | No |
Traffic with 250 USD | 1 | 0.769 % | No |
with 250 USD dollar | 1 | 0.769 % | No |
Traffic in the last | 1 | 0.769 % | No |
Clicks 30 days Traffic | 1 | 0.769 % | No |
30 days Traffic in | 1 | 0.769 % | No |
USD dollar as a | 1 | 0.769 % | 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 | ads.triansh.com | IN | 299 | A | 65.60.61.221 |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://ads.triansh.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 377 |
request size | 184 | filetime | -1 |
ssl verify result | 0 | redirect count | 0 |
total time | 0.306483 | namelookup time | 0.000334 |
connect time | 0.05367 | pretransfer time | 0.172619 |
size upload | 0 | size download | 25359 |
speed download | 82872 | speed upload | 0 |
download content length | -1 | upload content length | -1 |
starttransfer time | 0.306349 | redirect time | 0 |
redirect url | primary ip | 65.60.61.221 | |
certinfo | primary port | 443 | |
local ip | 107.167.87.194 | local port | 40022 |
http version | 3 | protocol | 2 |
ssl verifyresult | 0 | scheme | HTTPS |
appconnect time us | 172355 | connect time us | 53670 |
namelookup time us | 334 | pretransfer time us | 172619 |
redirect time us | 0 | starttransfer time us | 306349 |
total time us | 306483 |
86 requests • 1,003 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 1,740 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
58 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 50 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
390 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn More
6450 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
600 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
2.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 27 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 45 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 35 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn More
Total size was 1,003 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
7.0 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 126 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn More
40 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
361 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 58 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
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
85 requests • 1,187 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 490 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
58 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
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn More
90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
Potential savings of 27 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 116 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 34 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn More
Total size was 1,187 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
2.0 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 227 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn More
40 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
361 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 58 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
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