Powered by https://www.baaed.com ()
health report : https://business.zoeay.com
examined at : 25-04-22 15:55:23
follow recommendations of this health report to keep your site healthy
Powered by https://www.baaed.com ()
examined at : 25-04-22 15:55:23
follow recommendations of this health report to keep your site healthy
business
Your page title does not exceed 60 characters. It's fine.
Your site do not have any meta description.
Your site do not have any meta keyword.
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| elit | 31 | 3.638 % | No |
| dolor | 29 | 3.404 % | No |
| amet | 29 | 3.404 % | No |
| sit | 29 | 3.404 % | No |
| ipsum | 29 | 3.404 % | No |
| Lorem | 29 | 3.404 % | No |
| adipiscing | 29 | 3.404 % | No |
| sed | 27 | 3.169 % | No |
| eiusmod | 26 | 3.052 % | No |
| ut | 25 | 2.934 % | No |
| incididunt | 24 | 2.817 % | No |
| labore | 24 | 2.817 % | No |
| tempor | 24 | 2.817 % | No |
| dolore | 18 | 2.113 % | No |
| consectetur | 17 | 1.995 % | No |
| magna | 14 | 1.643 % | No |
| aliqua | 14 | 1.643 % | No |
| Ut | 12 | 1.408 % | No |
| veniam | 10 | 1.174 % | No |
| ad | 10 | 1.174 % | Yes |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Lorem ipsum | 29 | 3.404 % | No |
| adipiscing elit | 29 | 3.404 % | No |
| sit amet | 29 | 3.404 % | No |
| dolor sit | 29 | 3.404 % | No |
| ipsum dolor | 29 | 3.404 % | No |
| sed do | 27 | 3.169 % | No |
| elit sed | 27 | 3.169 % | No |
| do eiusmod | 26 | 3.052 % | No |
| tempor incididunt | 24 | 2.817 % | No |
| ut labore | 24 | 2.817 % | No |
| incididunt ut | 24 | 2.817 % | No |
| eiusmod tempor | 23 | 2.7 % | No |
| labore et | 18 | 2.113 % | No |
| et dolore | 18 | 2.113 % | No |
| amet consectetur | 17 | 1.995 % | No |
| consectetur adipiscing | 17 | 1.995 % | No |
| dolore magna | 14 | 1.643 % | No |
| magna aliqua | 14 | 1.643 % | No |
| aliqua Ut | 10 | 1.174 % | No |
| Ut enim | 10 | 1.174 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| dolor sit amet | 29 | 3.404 % | No |
| ipsum dolor sit | 29 | 3.404 % | No |
| Lorem ipsum dolor | 29 | 3.404 % | No |
| adipiscing elit sed | 27 | 3.169 % | No |
| elit sed do | 27 | 3.169 % | No |
| sed do eiusmod | 26 | 3.052 % | No |
| tempor incididunt ut | 24 | 2.817 % | No |
| incididunt ut labore | 24 | 2.817 % | No |
| do eiusmod tempor | 23 | 2.7 % | No |
| eiusmod tempor incididunt | 23 | 2.7 % | No |
| ut labore et | 18 | 2.113 % | No |
| labore et dolore | 18 | 2.113 % | No |
| consectetur adipiscing elit | 17 | 1.995 % | No |
| sit amet consectetur | 17 | 1.995 % | No |
| amet consectetur adipiscing | 17 | 1.995 % | No |
| et dolore magna | 14 | 1.643 % | No |
| dolore magna aliqua | 14 | 1.643 % | No |
| ad minim veniam | 10 | 1.174 % | No |
| aliqua Ut enim | 10 | 1.174 % | No |
| magna aliqua Ut | 10 | 1.174 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| ipsum dolor sit amet | 29 | 3.404 % | No |
| Lorem ipsum dolor sit | 29 | 3.404 % | No |
| adipiscing elit sed do | 27 | 3.169 % | No |
| elit sed do eiusmod | 26 | 3.052 % | No |
| tempor incididunt ut labore | 24 | 2.817 % | No |
| sed do eiusmod tempor | 23 | 2.7 % | No |
| do eiusmod tempor incididunt | 23 | 2.7 % | No |
| eiusmod tempor incididunt ut | 23 | 2.7 % | No |
| ut labore et dolore | 18 | 2.113 % | No |
| incididunt ut labore et | 18 | 2.113 % | No |
| amet consectetur adipiscing elit | 17 | 1.995 % | No |
| sit amet consectetur adipiscing | 17 | 1.995 % | No |
| dolor sit amet consectetur | 17 | 1.995 % | No |
| consectetur adipiscing elit sed | 15 | 1.761 % | No |
| et dolore magna aliqua | 14 | 1.643 % | No |
| labore et dolore magna | 14 | 1.643 % | No |
| dolore magna aliqua Ut | 10 | 1.174 % | No |
| magna aliqua Ut enim | 10 | 1.174 % | No |
| aliqua Ut enim ad | 10 | 1.174 % | No |
| Ut enim ad minim | 10 | 1.174 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://business.zoeay.com/wp-sitemap.xml
852
Text/HTML Ratio Test : 10%
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 passed plain text email test. No plain text email found.
Page have doc type.
Your site have 5 images without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is disabled.
Your site does not have any inline css.
Your site have 4 internal css.
Site passed micro data schema test. 2 results found.
| SL | Host | Class | TTL | Type | PRI | Target | IP |
|---|---|---|---|---|---|---|---|
| 1 | business.zoeay.com | IN | 9607 | A | 45.79.58.186 |
Site failed 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 750 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 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.5 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 5 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 19 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 68 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 3,413 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
80 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,003 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
40 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 410 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 39 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
0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
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.5 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 5 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 247 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 68 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 3,634 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
80 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,003 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
30 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