Follow recommendations of this health report to keep your site healthy
Examined at : 2023-01-09 14:39:32
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
nhà | 178 | 2.92 % | No |
tại | 103 | 1.69 % | No |
trọn | 76 | 1.247 % | No |
gói | 76 | 1.247 % | No |
nước | 72 | 1.181 % | No |
Xây | 68 | 1.116 % | No |
Mẫu | 58 | 0.952 % | No |
tầng | 48 | 0.788 % | No |
xây | 45 | 0.738 % | No |
lý | 44 | 0.722 % | No |
nguồn | 44 | 0.722 % | No |
giá | 44 | 0.722 % | No |
Xử | 42 | 0.689 % | No |
₫ | 40 | 0.656 % | No |
kế | 38 | 0.623 % | No |
thiết | 35 | 0.574 % | No |
công | 34 | 0.558 % | No |
Hà | 33 | 0.541 % | No |
hàng | 32 | 0.525 % | No |
hiện | 31 | 0.509 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
trọn gói | 76 | 1.247 % | No |
nhà trọn | 75 | 1.231 % | No |
gói tại | 56 | 0.919 % | No |
Xây nhà | 56 | 0.919 % | No |
lý nguồn | 42 | 0.689 % | No |
Xử lý | 42 | 0.689 % | No |
nguồn nước | 42 | 0.689 % | No |
nước tại | 40 | 0.656 % | No |
Mẫu nhà | 39 | 0.64 % | No |
thiết kế | 34 | 0.558 % | No |
hiện đại | 28 | 0.459 % | No |
Báo giá | 28 | 0.459 % | No |
xây nhà | 26 | 0.427 % | No |
nhà phố | 23 | 0.377 % | No |
lọc nước | 21 | 0.345 % | No |
₫ Thêm | 20 | 0.328 % | No |
Thêm vào | 20 | 0.328 % | No |
giỏ hàng | 20 | 0.328 % | No |
Hà Nội | 20 | 0.328 % | No |
tại Hà | 20 | 0.328 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
nhà trọn gói | 75 | 1.231 % | No |
trọn gói tại | 56 | 0.919 % | No |
Xây nhà trọn | 55 | 0.902 % | No |
lý nguồn nước | 42 | 0.689 % | No |
Xử lý nguồn | 42 | 0.689 % | No |
nguồn nước tại | 40 | 0.656 % | No |
Thêm vào giỏ | 20 | 0.328 % | No |
₫ Thêm vào | 20 | 0.328 % | No |
vào giỏ hàng | 20 | 0.328 % | No |
Chi phí xây | 16 | 0.263 % | No |
Mẫu nhà phố | 15 | 0.246 % | No |
Máy lọc nước | 14 | 0.23 % | No |
phí xây nhà | 12 | 0.197 % | No |
Mẫu nhà ống | 12 | 0.197 % | No |
giá thiết kế | 12 | 0.197 % | No |
Báo giá thiết | 12 | 0.197 % | No |
tại Hà Nội | 12 | 0.197 % | No |
nhà cấp 4 | 10 | 0.164 % | No |
xây nhà trọn | 10 | 0.164 % | No |
gói tại Hà | 10 | 0.164 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
nhà trọn gói tại | 56 | 0.919 % | No |
Xây nhà trọn gói | 55 | 0.902 % | No |
Xử lý nguồn nước | 42 | 0.689 % | No |
lý nguồn nước tại | 40 | 0.656 % | No |
Thêm vào giỏ hàng | 20 | 0.328 % | No |
₫ Thêm vào giỏ | 20 | 0.328 % | No |
Chi phí xây nhà | 12 | 0.197 % | No |
Báo giá thiết kế | 12 | 0.197 % | No |
xây nhà trọn gói | 10 | 0.164 % | No |
trọn gói tại Hà | 10 | 0.164 % | No |
công xây nhà trọn | 8 | 0.131 % | No |
Mẫu nhà cấp 4 | 8 | 0.131 % | No |
Kế Thi công xây | 8 | 0.131 % | No |
Thi công xây nhà | 8 | 0.131 % | No |
Thiết Kế Thi công | 8 | 0.131 % | No |
nhà trọn gói nhà | 8 | 0.131 % | No |
phong cách hiện đại | 7 | 0.115 % | No |
gói nhà Biệt Thự | 7 | 0.115 % | No |
Báo giá thi công | 7 | 0.115 % | No |
giá thiết kế nội | 7 | 0.115 % | 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 | ahthomes.com | IN | 296 | A | 103.221.221.88 | ||
2 | ahthomes.com | IN | 86400 | NS | haley.ns.cloudflare.com | ||
3 | ahthomes.com | IN | 86400 | NS | kyrie.ns.cloudflare.com |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://ahthomes.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 760 |
request size | 129 | filetime | -1 |
ssl verify result | 0 | redirect count | 0 |
total time | 0.718797 | namelookup time | 0.014294 |
connect time | 0.078669 | pretransfer time | 0.331914 |
size upload | 0 | size download | 437345 |
speed download | 608440 | speed upload | 0 |
download content length | -1 | upload content length | 0 |
starttransfer time | 0.398139 | redirect time | 0 |
redirect url | primary ip | 103.221.221.88 | |
certinfo | primary port | 443 | |
local ip | 172.104.121.245 | local port | 60064 |
79 requests • 2,130 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 0 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
48 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 990 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
3630 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
5,170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
6.8 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 149 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 48 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 2,130 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
17.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
13 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
5,981 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 10 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
41 requests • 450 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
35 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.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
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 37 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 450 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
13 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
6,259 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 10 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