Powered by https://testweb.ai ()
health report : https://copyshop.vn/
examined at : 24-10-10 17:29:04
follow recommendations of this health report to keep your site healthy
Powered by https://testweb.ai ()
examined at : 24-10-10 17:29:04
follow recommendations of this health report to keep your site healthy
Copy Shop - Giải pháp in ấn
Your page title does not exceed 60 characters. It's fine.
Bìa đựng hồ sơ
Your meta description does not exceed 150 characters. It's fine.
Your site do not have any meta keyword.
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| TPHCM | 94 | 6.763 % | No |
| tại | 81 | 5.827 % | No |
| giá | 52 | 3.741 % | No |
| rẻ | 50 | 3.597 % | No |
| thẻ | 32 | 2.302 % | No |
| viên | 12 | 0.863 % | No |
| bìa | 11 | 0.791 % | No |
| thư | 11 | 0.791 % | No |
| giấy | 10 | 0.719 % | No |
| hàng | 10 | 0.719 % | No |
| bì | 10 | 0.719 % | No |
| da | 10 | 0.719 % | No |
| menu | 9 | 0.647 % | No |
| nhựa | 8 | 0.576 % | No |
| Đọc | 8 | 0.576 % | No |
| tiếp | 8 | 0.576 % | No |
| khen | 8 | 0.576 % | No |
| phẩm | 7 | 0.504 % | No |
| bao | 5 | 0.36 % | No |
| phong | 5 | 0.36 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| tại TPHCM | 81 | 5.827 % | No |
| TPHCM In | 73 | 5.252 % | No |
| giá rẻ | 50 | 3.597 % | No |
| rẻ tại | 36 | 2.59 % | No |
| In thẻ | 29 | 2.086 % | No |
| TPHCM in | 10 | 0.719 % | No |
| rẻ TPHCM | 8 | 0.576 % | No |
| Đọc tiếp | 8 | 0.576 % | No |
| bìa da | 6 | 0.432 % | No |
| viên tại | 6 | 0.432 % | No |
| viên giá | 6 | 0.432 % | No |
| thẻ sinh | 5 | 0.36 % | No |
| sinh viên | 5 | 0.36 % | No |
| menu bìa | 5 | 0.36 % | No |
| theo yêu | 5 | 0.36 % | No |
| bì tại | 5 | 0.36 % | No |
| phong bì | 5 | 0.36 % | No |
| thư phong | 5 | 0.36 % | No |
| bì thư | 5 | 0.36 % | No |
| thư bì | 5 | 0.36 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| tại TPHCM In | 68 | 4.892 % | No |
| giá rẻ tại | 36 | 2.59 % | No |
| rẻ tại TPHCM | 36 | 2.59 % | No |
| TPHCM In thẻ | 23 | 1.655 % | No |
| giá rẻ TPHCM | 8 | 0.576 % | No |
| viên tại TPHCM | 6 | 0.432 % | No |
| viên giá rẻ | 6 | 0.432 % | No |
| sinh viên tại | 5 | 0.36 % | No |
| In bao thư | 5 | 0.36 % | No |
| thư bì thư | 5 | 0.36 % | No |
| bì thư phong | 5 | 0.36 % | No |
| thư phong bì | 5 | 0.36 % | No |
| phong bì tại | 5 | 0.36 % | No |
| bì tại TPHCM | 5 | 0.36 % | No |
| bao thư bì | 5 | 0.36 % | No |
| theo yêu cầu | 5 | 0.36 % | No |
| TPHCM Đọc tiếp | 5 | 0.36 % | No |
| Đọc tiếp In | 5 | 0.36 % | No |
| thẻ sinh viên | 5 | 0.36 % | No |
| In thẻ sinh | 5 | 0.36 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| giá rẻ tại TPHCM | 36 | 2.59 % | No |
| rẻ tại TPHCM In | 28 | 2.014 % | No |
| tại TPHCM In thẻ | 23 | 1.655 % | No |
| bao thư bì thư | 5 | 0.36 % | No |
| viên tại TPHCM In | 5 | 0.36 % | No |
| sinh viên tại TPHCM | 5 | 0.36 % | No |
| thẻ sinh viên tại | 5 | 0.36 % | No |
| TPHCM Đọc tiếp In | 5 | 0.36 % | No |
| In thẻ sinh viên | 5 | 0.36 % | No |
| TPHCM In thẻ sinh | 5 | 0.36 % | No |
| In bao thư bì | 5 | 0.36 % | No |
| thư bì thư phong | 5 | 0.36 % | No |
| bì thư phong bì | 5 | 0.36 % | No |
| thư phong bì tại | 5 | 0.36 % | No |
| giá rẻ TPHCM In | 5 | 0.36 % | No |
| phong bì tại TPHCM | 5 | 0.36 % | No |
| bì tại TPHCM In | 5 | 0.36 % | No |
| In catalogue giá rẻ | 4 | 0.288 % | No |
| folder giá rẻ tại | 4 | 0.288 % | No |
| tại TPHCM In bìa | 4 | 0.288 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://copyshop.vn/sitemap_index.xml
1390
Text/HTML Ratio Test : 3%
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.5plain text email found.
Page have doc type.
Your site have 4 images without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is disabled.
Your site have 88 inline css.
Your site have 76 internal css.
Site failed micro data schema test.
| SL | Host | Class | TTL | Type | PRI | Target | IP |
|---|---|---|---|---|---|---|---|
| 1 | copyshop.vn | IN | 360 | A | 103.77.162.35 | ||
| 2 | copyshop.vn | IN | 354 | NS | ns2.dotvndns.vn | ||
| 3 | copyshop.vn | IN | 354 | NS | ns1.dotvndns.vn | ||
| 4 | copyshop.vn | IN | 354 | NS | nsbak.dotvndns.com | ||
| 5 | copyshop.vn | IN | 354 | NS | ns3.dotvndns.vn | ||
| 6 | copyshop.vn | IN | 360 | MX | 10 | mail.copyshop.vn |
Site failed IP canonicalization test.
Site passed 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 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
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
3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 60 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
50 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
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
180 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 339 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 36 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 769 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
3.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
9 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,400 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
10 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
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
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 80 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
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
230 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 358 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 35 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,146 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
9 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,400 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
150 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