Powered by https://testweb.ai ()
examined at : 24-09-05 16:23:30
follow recommendations of this health report to keep your site healthy
Công ty cổ phần Miraway giải pháp công nghệ
Your page title does not exceed 60 characters. It's fine.
Miraway - doanh nghiệp cung cấp giải pháp công nghệ trải nghiệm giao dịch khách hàng top 20 thế giới
Your meta description does not exceed 150 characters. It's fine.
miraway
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
hàng | 64 | 2.588 % | No |
khách | 45 | 1.82 % | No |
và | 30 | 1.213 % | No |
pháp | 29 | 1.173 % | No |
Giải | 25 | 1.011 % | No |
hiểu | 22 | 0.89 % | No |
thêm | 22 | 0.89 % | No |
Tìm | 22 | 0.89 % | No |
nghiệm | 22 | 0.89 % | No |
thông | 20 | 0.809 % | No |
trải | 19 | 0.768 % | No |
thống | 17 | 0.687 % | No |
kênh | 14 | 0.566 % | No |
tảng | 14 | 0.566 % | No |
Hệ | 14 | 0.566 % | No |
tự | 13 | 0.526 % | No |
quản | 12 | 0.485 % | No |
minh | 12 | 0.485 % | No |
tiếp | 12 | 0.485 % | No |
Nền | 11 | 0.445 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
khách hàng | 45 | 1.82 % | No |
Giải pháp | 22 | 0.89 % | No |
hiểu thêm | 22 | 0.89 % | No |
Tìm hiểu | 22 | 0.89 % | No |
trải nghiệm | 19 | 0.768 % | No |
nghiệm khách | 15 | 0.607 % | No |
Hệ thống | 14 | 0.566 % | No |
thông minh | 12 | 0.485 % | No |
Nền tảng | 11 | 0.445 % | No |
quản lý | 9 | 0.364 % | No |
hàng đa | 8 | 0.323 % | No |
đa kênh | 8 | 0.323 % | No |
dữ liệu | 8 | 0.323 % | No |
liệu khách | 7 | 0.283 % | No |
nhận diện | 7 | 0.283 % | No |
tự động | 7 | 0.283 % | No |
giải pháp | 7 | 0.283 % | No |
phục vụ | 7 | 0.283 % | No |
thêm Giải | 7 | 0.283 % | No |
tại tất | 6 | 0.243 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Tìm hiểu thêm | 22 | 0.89 % | No |
nghiệm khách hàng | 15 | 0.607 % | No |
trải nghiệm khách | 13 | 0.526 % | No |
khách hàng đa | 8 | 0.323 % | No |
hàng đa kênh | 8 | 0.323 % | No |
liệu khách hàng | 7 | 0.283 % | No |
hiểu thêm Giải | 7 | 0.283 % | No |
thêm Giải pháp | 7 | 0.283 % | No |
dữ liệu khách | 7 | 0.283 % | No |
thêm Hệ thống | 6 | 0.243 % | No |
hiểu thêm Hệ | 6 | 0.243 % | No |
cận khách hàng | 6 | 0.243 % | No |
tiếp cận khách | 6 | 0.243 % | No |
và tiếp cận | 6 | 0.243 % | No |
trị trải nghiệm | 6 | 0.243 % | No |
Giải pháp quản | 6 | 0.243 % | No |
tại tất cả | 6 | 0.243 % | No |
hàng tại tất | 6 | 0.243 % | No |
khách hàng tại | 6 | 0.243 % | No |
thêm Nền tảng | 6 | 0.243 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
trải nghiệm khách hàng | 13 | 0.526 % | No |
khách hàng đa kênh | 8 | 0.323 % | No |
nghiệm khách hàng đa | 8 | 0.323 % | No |
dữ liệu khách hàng | 7 | 0.283 % | No |
Tìm hiểu thêm Giải | 7 | 0.283 % | No |
hiểu thêm Giải pháp | 7 | 0.283 % | No |
Tìm hiểu thêm Nền | 6 | 0.243 % | No |
khách hàng tại tất | 6 | 0.243 % | No |
và tiếp cận khách | 6 | 0.243 % | No |
tiếp cận khách hàng | 6 | 0.243 % | No |
Tìm hiểu thêm Hệ | 6 | 0.243 % | No |
hiểu thêm Hệ thống | 6 | 0.243 % | No |
hiểu thêm Nền tảng | 6 | 0.243 % | No |
nhất Tìm hiểu thêm | 6 | 0.243 % | No |
hàng tại tất cả | 6 | 0.243 % | No |
thêm Giải pháp quản | 6 | 0.243 % | No |
tích dữ liệu khách | 4 | 0.162 % | No |
phục vụ Giải pháp | 4 | 0.162 % | No |
tự phục vụ Giải | 4 | 0.162 % | No |
đặt lịch xếp hàng | 3 | 0.121 % | No |
miraway
The most using keywords do not match with meta keywords.
Your site have sitemap
https://miraway.vn/sitemap.xml
2473
Text/HTML Ratio Test : 5%
Your site have robot.txt
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.
Links of your site are SEO friendly.
Site failed plain text email test.1plain text email found.
Page have doc type.
Your site does not have any image without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is enabled.
Your site have 26 inline css.
Your site have 4 internal css.
Site failed micro data schema test.
SL | Host | Class | TTL | Type | PRI | Target | IP |
---|---|---|---|---|---|---|---|
1 | miraway.vn | IN | 86400 | A | 14.225.7.177 | ||
2 | miraway.vn | IN | 600 | NS | diana.ns.cloudflare.com | ||
3 | miraway.vn | IN | 600 | NS | isaac.ns.cloudflare.com | ||
4 | miraway.vn | IN | 86400 | MX | 5 | ALT1.ASPMX.L.GOOGLE.COM | |
5 | miraway.vn | IN | 86400 | MX | 10 | ASPMX2.GOOGLEMAIL.COM | |
6 | miraway.vn | IN | 86400 | MX | 5 | ALT2.ASPMX.L.GOOGLE.COM | |
7 | miraway.vn | IN | 86400 | MX | 1 | ASPMX.L.GOOGLE.COM | |
8 | miraway.vn | IN | 86400 | MX | 10 | ASPMX.L4.GOOGLE.COM |
Site passed IP canonicalization test.
Site failed URL canonicalization test.
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
Aggregates all network requests and groups them by typeLearn 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
0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 260 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
160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.9 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 30 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 240 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
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 1,485 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
2 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
635 elements
A large DOM will increase memory usage, cause longer Learn More
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
Aggregates all network requests and groups them by typeLearn 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 blocked the main thread for 90 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
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.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 30 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 203 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 25 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 1,444 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
2 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
649 elements
A large DOM will increase memory usage, cause longer Learn More
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