Follow recommendations of this health report to keep your site healthy
Examined at : 2023-01-12 16:21:06
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
mây | 123 | 2.857 % | No |
nhựa | 119 | 2.764 % | No |
ghế | 106 | 2.462 % | No |
Bàn | 68 | 1.58 % | No |
bàn | 43 | 0.999 % | No |
Ghế | 32 | 0.743 % | No |
sản | 31 | 0.72 % | No |
Nhựa | 21 | 0.488 % | No |
được | 21 | 0.488 % | No |
Mây | 20 | 0.465 % | No |
phẩm | 20 | 0.465 % | No |
vườn | 20 | 0.465 % | No |
hàng | 19 | 0.441 % | No |
Giường | 19 | 0.441 % | No |
là | 19 | 0.441 % | No |
công | 18 | 0.418 % | No |
tắm | 18 | 0.418 % | No |
ngoài | 18 | 0.418 % | No |
cho | 18 | 0.418 % | No |
nắng | 18 | 0.418 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
mây nhựa | 105 | 2.439 % | No |
Bàn ghế | 63 | 1.463 % | No |
ghế mây | 55 | 1.278 % | No |
bàn ghế | 34 | 0.79 % | No |
Mây Nhựa | 17 | 0.395 % | No |
tắm nắng | 17 | 0.395 % | No |
Ghế mây | 16 | 0.372 % | No |
sản xuất | 16 | 0.372 % | No |
ngoài trời | 14 | 0.325 % | No |
sản phẩm | 14 | 0.325 % | No |
giả mây | 13 | 0.302 % | No |
Giường mây | 13 | 0.302 % | No |
thư giãn | 13 | 0.302 % | No |
Minh Phát | 13 | 0.302 % | No |
sân vườn | 12 | 0.279 % | No |
Nhựa Minh | 12 | 0.279 % | No |
bể bơi | 12 | 0.279 % | No |
Xích đu | 12 | 0.279 % | No |
Hà Nội | 11 | 0.256 % | No |
kết hợp | 10 | 0.232 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
ghế mây nhựa | 52 | 1.208 % | No |
Bàn ghế mây | 34 | 0.79 % | No |
bàn ghế mây | 19 | 0.441 % | No |
Ghế mây nhựa | 16 | 0.372 % | No |
Giường mây nhựa | 13 | 0.302 % | No |
Nhựa Minh Phát | 12 | 0.279 % | No |
Bộ bàn ghế | 10 | 0.232 % | No |
nhựa tắm nắng | 9 | 0.209 % | No |
mây nhựa tắm | 9 | 0.209 % | No |
vườn Bàn ghế | 8 | 0.186 % | No |
Mây Nhựa Minh | 8 | 0.186 % | No |
nhựa giả mây | 8 | 0.186 % | No |
Cafe Bàn ghế | 7 | 0.163 % | No |
mây nhựa Xích | 6 | 0.139 % | No |
Ghê mây nhựa | 6 | 0.139 % | No |
mây nhựa kết | 6 | 0.139 % | No |
nhựa kết hợp | 6 | 0.139 % | No |
thự Bàn ghế | 6 | 0.139 % | No |
mây nhựa Cafe | 6 | 0.139 % | No |
nhựa Xích đu | 6 | 0.139 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Bàn ghế mây nhựa | 34 | 0.79 % | No |
bàn ghế mây nhựa | 17 | 0.395 % | No |
Bộ bàn ghế mây | 10 | 0.232 % | No |
mây nhựa tắm nắng | 9 | 0.209 % | No |
Mây Nhựa Minh Phát | 8 | 0.186 % | No |
vườn Bàn ghế mây | 7 | 0.163 % | No |
Cafe Bàn ghế mây | 6 | 0.139 % | No |
mây nhựa Xích đu | 6 | 0.139 % | No |
mây nhựa thư giãn | 6 | 0.139 % | No |
mây nhựa kết hợp | 6 | 0.139 % | No |
ghế mây nhựa Cafe | 6 | 0.139 % | No |
Ghê mây nhựa tắm | 6 | 0.139 % | No |
biệt thự Bàn ghế | 5 | 0.116 % | No |
mây nhựa Home Stay | 4 | 0.093 % | No |
ghế mây nhựa ngoài | 4 | 0.093 % | No |
Mây Nhựa Minh | 4 | 0.093 % | No |
khu vực Hà Nội | 4 | 0.093 % | No |
mây nhựa sân vườn | 4 | 0.093 % | No |
Mây Nhựa Minh Phát | 4 | 0.093 % | No |
ghế mây nhựa sân | 4 | 0.093 % | 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 | maynhuaminhphat.com | IN | 295 | A | 103.57.222.24 | ||
2 | maynhuaminhphat.com | IN | 3600 | NS | ns1.inet.vn | ||
3 | maynhuaminhphat.com | IN | 3600 | NS | ns3.inet.vn | ||
4 | maynhuaminhphat.com | IN | 3600 | NS | ns2.inet.vn |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://maynhuaminhphat.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 881 |
request size | 282 | filetime | -1 |
ssl verify result | 0 | redirect count | 1 |
total time | 2.648782 | namelookup time | 0.004132 |
connect time | 0.143965 | pretransfer time | 0.552265 |
size upload | 0 | size download | 133944 |
speed download | 50568 | speed upload | 0 |
download content length | 0 | upload content length | 0 |
starttransfer time | 0.698133 | redirect time | 1.528233 |
redirect url | primary ip | 103.57.222.24 | |
certinfo | primary port | 443 | |
local ip | 172.104.121.245 | local port | 45032 |
64 requests • 14,719 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 600 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 51 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
40 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 70 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
5548 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
350 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.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,144 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 5,217 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 86 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 14,719 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
3.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
7 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
993 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
Potential savings of 15 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
64 requests • 12,997 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 60 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 51 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
40 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
20 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 3,655 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 6,266 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 84 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 12,997 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
7 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
993 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
Potential savings of 15 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