Powered by https://0ab.org ()
examined at : 23-09-02 19:10:31
follow recommendations of this health report to keep your site healthy
Whole Hoggs - The Whole Hoggs
Your page title does not exceed 60 characters. It's fine.
The Whole Hoggs was founded by Peter & Susan Whelan in 2010. All of the pigs are born on the farm and live a long and happy life on the 60 acre farm.
Your meta description does not exceed 150 characters. It's fine.
Your site do not have any meta keyword.
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
3 | 1.695 % | No | |
Hoggs | 3 | 1.695 % | No |
Products | 2 | 1.13 % | No |
Contact | 2 | 1.13 % | No |
Honest2Goodness | 2 | 1.13 % | No |
Slaney | 2 | 1.13 % | No |
Glasnevin | 2 | 1.13 % | No |
Saturday | 2 | 1.13 % | No |
year | 2 | 1.13 % | No |
stall | 2 | 1.13 % | No |
susanwhelan7hotmailcom | 1 | 0.565 % | No |
Select | 1 | 0.565 % | No |
Page | 1 | 0.565 % | No |
effect | 1 | 0.565 % | No |
longer | 1 | 0.565 % | No |
home | 1 | 0.565 % | Yes |
deliveries | 1 | 0.565 % | No |
service | 1 | 0.565 % | No |
initially | 1 | 0.565 % | No |
introduced | 1 | 0.565 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Whole Hoggs | 2 | 1.13 % | No |
Hoggs About | 2 | 1.13 % | No |
About Us | 2 | 1.13 % | No |
Us Our | 2 | 1.13 % | No |
Our Products | 2 | 1.13 % | No |
Products Contact | 2 | 1.13 % | No |
Contact Us | 2 | 1.13 % | No |
at Honest2Goodness | 2 | 1.13 % | No |
See us | 2 | 1.13 % | No |
us on | 2 | 1.13 % | No |
0879419866 0868147459 | 1 | 0.565 % | No |
0868147459 susanwhelan7hotmailcom | 1 | 0.565 % | No |
susanwhelan7hotmailcom Twitter | 1 | 0.565 % | No |
Twitter Twitter | 1 | 0.565 % | No |
Twitter Whole | 1 | 0.565 % | No |
Us Select | 1 | 0.565 % | No |
Select Page | 1 | 0.565 % | No |
Page With | 1 | 0.565 % | No |
With immediate | 1 | 0.565 % | No |
immediate effect | 1 | 0.565 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Whole Hoggs About | 2 | 1.13 % | No |
Hoggs About Us | 2 | 1.13 % | No |
About Us Our | 2 | 1.13 % | No |
Us Our Products | 2 | 1.13 % | No |
Our Products Contact | 2 | 1.13 % | No |
Products Contact Us | 2 | 1.13 % | No |
See us on | 2 | 1.13 % | No |
0879419866 0868147459 susanwhelan7hotmailcom | 1 | 0.565 % | No |
0868147459 susanwhelan7hotmailcom Twitter | 1 | 0.565 % | No |
susanwhelan7hotmailcom Twitter Twitter | 1 | 0.565 % | No |
Twitter Twitter Whole | 1 | 0.565 % | No |
Twitter Whole Hoggs | 1 | 0.565 % | No |
Contact Us Select | 1 | 0.565 % | No |
Us Select Page | 1 | 0.565 % | No |
Select Page With | 1 | 0.565 % | No |
Page With immediate | 1 | 0.565 % | No |
With immediate effect | 1 | 0.565 % | No |
immediate effect we | 1 | 0.565 % | No |
effect we are | 1 | 0.565 % | No |
we are no | 1 | 0.565 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Whole Hoggs About Us | 2 | 1.13 % | No |
Hoggs About Us Our | 2 | 1.13 % | No |
About Us Our Products | 2 | 1.13 % | No |
Us Our Products Contact | 2 | 1.13 % | No |
Our Products Contact Us | 2 | 1.13 % | No |
0879419866 0868147459 susanwhelan7hotmailcom Twitter | 1 | 0.565 % | No |
0868147459 susanwhelan7hotmailcom Twitter Twitter | 1 | 0.565 % | No |
susanwhelan7hotmailcom Twitter Twitter Whole | 1 | 0.565 % | No |
Twitter Twitter Whole Hoggs | 1 | 0.565 % | No |
Twitter Whole Hoggs About | 1 | 0.565 % | No |
Products Contact Us Select | 1 | 0.565 % | No |
Contact Us Select Page | 1 | 0.565 % | No |
Us Select Page With | 1 | 0.565 % | No |
Select Page With immediate | 1 | 0.565 % | No |
Page With immediate effect | 1 | 0.565 % | No |
With immediate effect we | 1 | 0.565 % | No |
immediate effect we are | 1 | 0.565 % | No |
effect we are no | 1 | 0.565 % | No |
we are no longer | 1 | 0.565 % | No |
are no longer doing | 1 | 0.565 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://www.thewholehoggs.com/sitemap_index.xml
177
Text/HTML Ratio Test : 2%
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.2plain text email found.
Page have doc type.
Your site have 19 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 12 inline css.
Your site have 6 internal css.
Site failed micro data schema test.
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" />
Potential savings of 300 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 21 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
43 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 14,100 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
7,860 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
19.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 948 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
430 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 9 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 76 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 7,925 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
24.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
23 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
368 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
65 user timings
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
Potential savings of 120 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 41 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
50 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 1,650 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
660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
3.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 561 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
210 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 505 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 76 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 8,526 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
23 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
368 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
56 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
100 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