Follow recommendations of this health report to keep your site healthy
Examined at : 2023-03-31 14:02:21
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
trẻ | 26 | 3.321 % | No |
ago | 17 | 2.171 % | No |
dục | 17 | 2.171 % | No |
cho | 15 | 1.916 % | No |
Giáo | 14 | 1.788 % | No |
Kiến | 12 | 1.533 % | No |
thức | 11 | 1.405 % | No |
mẹ | 8 | 1.022 % | No |
ngày | 8 | 1.022 % | No |
Review | 8 | 1.022 % | No |
cách | 8 | 1.022 % | No |
Trường | 7 | 0.894 % | No |
ở | 6 | 0.766 % | No |
và | 6 | 0.766 % | No |
giúp | 6 | 0.766 % | No |
Con | 6 | 0.766 % | No |
sinh | 6 | 0.766 % | No |
Kinh | 6 | 0.766 % | No |
hay | 6 | 0.766 % | No |
trường | 5 | 0.639 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Giáo dục | 13 | 1.66 % | No |
Kiến thức | 11 | 1.405 % | No |
ngày ago | 8 | 1.022 % | No |
cho trẻ | 8 | 1.022 % | No |
Review Trường | 7 | 0.894 % | No |
ở trẻ | 6 | 0.766 % | No |
ago Giáo | 6 | 0.766 % | No |
nghiệm hay | 5 | 0.639 % | No |
dục sớm | 5 | 0.639 % | No |
sớm cho | 5 | 0.639 % | No |
1 tháng | 5 | 0.639 % | No |
tháng ago | 5 | 0.639 % | No |
Con Khỏe | 5 | 0.639 % | No |
Cận thị | 5 | 0.639 % | No |
thị ở | 5 | 0.639 % | No |
Nuôi Con | 5 | 0.639 % | No |
Kinh nghiệm | 5 | 0.639 % | No |
cách phòng | 5 | 0.639 % | No |
và cách | 5 | 0.639 % | No |
trẻ sơ | 4 | 0.511 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
sớm cho trẻ | 5 | 0.639 % | No |
Nuôi Con Khỏe | 5 | 0.639 % | No |
1 tháng ago | 5 | 0.639 % | No |
ago Giáo dục | 5 | 0.639 % | No |
Kinh nghiệm hay | 5 | 0.639 % | No |
Cận thị ở | 5 | 0.639 % | No |
và cách phòng | 5 | 0.639 % | No |
thị ở trẻ | 5 | 0.639 % | No |
dục sớm cho | 5 | 0.639 % | No |
phổ biến hiện | 4 | 0.511 % | No |
sơ sinh Nguyên | 4 | 0.511 % | No |
trẻ phổ biến | 4 | 0.511 % | No |
cho trẻ phổ | 4 | 0.511 % | No |
Cẩm nang cho | 4 | 0.511 % | No |
giáo dục sớm | 4 | 0.511 % | No |
pháp giáo dục | 4 | 0.511 % | No |
phương pháp giáo | 4 | 0.511 % | No |
biến hiện nay | 4 | 0.511 % | No |
bà mẹ trẻ | 4 | 0.511 % | No |
nang cho các | 4 | 0.511 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
dục sớm cho trẻ | 5 | 0.639 % | No |
Cận thị ở trẻ | 5 | 0.639 % | No |
và cách phòng ngừa | 4 | 0.511 % | No |
nang cho các bà | 4 | 0.511 % | No |
phương pháp giáo dục | 4 | 0.511 % | No |
pháp giáo dục sớm | 4 | 0.511 % | No |
giáo dục sớm cho | 4 | 0.511 % | No |
sớm cho trẻ phổ | 4 | 0.511 % | No |
cho trẻ phổ biến | 4 | 0.511 % | No |
trẻ phổ biến hiện | 4 | 0.511 % | No |
phổ biến hiện nay | 4 | 0.511 % | No |
Cẩm nang cho các | 4 | 0.511 % | No |
các bà mẹ trẻ | 4 | 0.511 % | No |
cho các bà mẹ | 4 | 0.511 % | No |
tháng ago Giáo dục | 4 | 0.511 % | No |
thị ở trẻ sơ | 4 | 0.511 % | No |
ở trẻ sơ sinh | 4 | 0.511 % | No |
trẻ sơ sinh Nguyên | 4 | 0.511 % | No |
sơ sinh Nguyên nhân | 4 | 0.511 % | No |
sinh Nguyên nhân triệu | 4 | 0.511 % | 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 | giaoductretho.com | IN | 3596 | A | 165.22.97.88 | ||
2 | giaoductretho.com | IN | 3600 | NS | ns1.matbao.com | ||
3 | giaoductretho.com | IN | 3600 | NS | ns2.matbao.com |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://giaoductretho.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 840 |
request size | 274 | filetime | -1 |
ssl verify result | 0 | redirect count | 1 |
total time | 2.077935 | namelookup time | 0.004154 |
connect time | 0.088638 | pretransfer time | 0.330741 |
size upload | 0 | size download | 123066 |
speed download | 59225 | speed upload | 0 |
download content length | 0 | upload content length | 0 |
starttransfer time | 1.402837 | redirect time | 0.422921 |
redirect url | primary ip | 165.22.97.88 | |
certinfo | primary port | 443 | |
local ip | 172.104.121.245 | local port | 36002 |
234 requests • 5,342 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 3,150 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
42 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 3,800 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
9390 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
3,040 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
9.4 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 188 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 164 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 98 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 5,342 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
19.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. 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
1,062 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 3 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
132 requests • 4,778 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 580 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 15 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
9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 200 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
190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.6 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 201 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 2,145 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 96 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 4,778 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
4.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. 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
1,081 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 3 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