Follow recommendations of this health report to keep your site healthy
Examined at : 2022-06-24 11:12:10
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Beli | 17 | 5.06 % | No |
sekarang | 16 | 4.762 % | No |
Body | 12 | 3.571 % | No |
Care | 11 | 3.274 % | No |
Beauty | 9 | 2.679 % | No |
Bath | 6 | 1.786 % | No |
Anda | 5 | 1.488 % | No |
Buffet | 5 | 1.488 % | No |
untuk | 4 | 1.19 % | No |
Produk | 4 | 1.19 % | No |
Face | 4 | 1.19 % | No |
ke | 4 | 1.19 % | No |
Mask | 3 | 0.893 % | No |
dan | 3 | 0.893 % | No |
di | 3 | 0.893 % | No |
Shop | 3 | 0.893 % | No |
Indonesia | 3 | 0.893 % | No |
Collagen | 3 | 0.893 % | No |
3 | 0.893 % | No | |
Make | 3 | 0.893 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Beli sekarang | 16 | 4.762 % | No |
sekarang Beli | 7 | 2.083 % | No |
Bath Body | 5 | 1.488 % | No |
Beauty Buffet | 5 | 1.488 % | No |
Face Care | 4 | 1.19 % | No |
Men Promo | 3 | 0.893 % | No |
Up Men | 3 | 0.893 % | No |
Make Up | 3 | 0.893 % | No |
Body care | 3 | 0.893 % | No |
Care Body | 3 | 0.893 % | No |
care Make | 3 | 0.893 % | No |
Body Face | 3 | 0.893 % | No |
Skin Care | 3 | 0.893 % | No |
Care Skin | 3 | 0.893 % | No |
Beauty Care | 3 | 0.893 % | No |
Katalog Beauty | 3 | 0.893 % | No |
Semua Katalog | 3 | 0.893 % | No |
Care Bath | 3 | 0.893 % | No |
Rp180000 Beli | 2 | 0.595 % | No |
Buffet Shop | 2 | 0.595 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Beli sekarang Beli | 7 | 2.083 % | No |
sekarang Beli sekarang | 7 | 2.083 % | No |
Bath Body Face | 3 | 0.893 % | No |
Up Men Promo | 3 | 0.893 % | No |
Make Up Men | 3 | 0.893 % | No |
care Make Up | 3 | 0.893 % | No |
Body care Make | 3 | 0.893 % | No |
Face Care Body | 3 | 0.893 % | No |
Body Face Care | 3 | 0.893 % | No |
Care Body care | 3 | 0.893 % | No |
Skin Care Bath | 3 | 0.893 % | No |
Care Skin Care | 3 | 0.893 % | No |
Beauty Care Skin | 3 | 0.893 % | No |
Katalog Beauty Care | 3 | 0.893 % | No |
Semua Katalog Beauty | 3 | 0.893 % | No |
Care Bath Body | 3 | 0.893 % | No |
Beli sekarang Vitamin | 2 | 0.595 % | No |
Pink Collagen Radiant | 2 | 0.595 % | No |
sekarang Pink Collagen | 2 | 0.595 % | No |
Plus Whitening Q10 | 2 | 0.595 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Beli sekarang Beli sekarang | 7 | 2.083 % | No |
Bath Body Face Care | 3 | 0.893 % | No |
Make Up Men Promo | 3 | 0.893 % | No |
Semua Katalog Beauty Care | 3 | 0.893 % | No |
Katalog Beauty Care Skin | 3 | 0.893 % | No |
Beauty Care Skin Care | 3 | 0.893 % | No |
Care Skin Care Bath | 3 | 0.893 % | No |
Skin Care Bath Body | 3 | 0.893 % | No |
Care Bath Body Face | 3 | 0.893 % | No |
Body Face Care Body | 3 | 0.893 % | No |
Face Care Body care | 3 | 0.893 % | No |
Care Body care Make | 3 | 0.893 % | No |
Body care Make Up | 3 | 0.893 % | No |
care Make Up Men | 3 | 0.893 % | No |
sekarang Beli sekarang Vitamin | 2 | 0.595 % | No |
Beli sekarang Milk Plus | 2 | 0.595 % | No |
sekarang Beli sekarang Milk | 2 | 0.595 % | No |
Beli sekarang Pink Collagen | 2 | 0.595 % | No |
sekarang Milk Plus Whitening | 2 | 0.595 % | No |
Milk Plus Whitening Q10 | 2 | 0.595 % | 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 | beautybuffet.co.id | IN | 14388 | A | 45.13.255.119 | ||
2 | beautybuffet.co.id | IN | 86400 | NS | ns2.niagahoster.com | ||
3 | beautybuffet.co.id | IN | 86400 | NS | ns1.niagahoster.com | ||
4 | beautybuffet.co.id | IN | 14400 | MX | 0 | beautybuffet.co.id |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://beautybuffet.co.id/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 1264 |
request size | 327 | filetime | -1 |
ssl verify result | 0 | redirect count | 1 |
total time | 8.900102 | namelookup time | 0.004179 |
connect time | 0.217697 | pretransfer time | 0.65167 |
size upload | 0 | size download | 149481 |
speed download | 16795 | speed upload | 0 |
download content length | 149481 | upload content length | -1 |
starttransfer time | 0.884455 | redirect time | 7.164494 |
redirect url | primary ip | 45.13.255.119 | |
certinfo | primary port | 443 | |
local ip | 204.48.18.59 | local port | 42326 |
32 requests • 861 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 270 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 52 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
0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
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
3060 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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
Potential savings of 525 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 13 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 861 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
12 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
638 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
32 requests • 294 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 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.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 40 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 13 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 294 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
11 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
638 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