Follow recommendations of this health report to keep your site healthy
Examined at : 2020-12-12 06:05:04
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Moor | 24 | 1.312 % | No |
Baildon | 22 | 1.203 % | No |
dog | 12 | 0.656 % | No |
moor | 11 | 0.601 % | No |
common | 10 | 0.547 % | No |
access | 10 | 0.547 % | Yes |
pm | 8 | 0.437 % | No |
rights | 8 | 0.437 % | No |
local | 7 | 0.383 % | No |
Act | 7 | 0.383 % | No |
agree | 6 | 0.328 % | No |
urban | 6 | 0.328 % | No |
horses | 6 | 0.328 % | No |
land | 6 | 0.328 % | No |
July | 6 | 0.328 % | No |
CROW | 5 | 0.273 % | No |
wind | 5 | 0.273 % | No |
Land | 5 | 0.273 % | No |
woodland | 5 | 0.273 % | No |
dogs | 5 | 0.273 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Baildon Moor | 20 | 1.093 % | No |
of the | 13 | 0.711 % | No |
the moor | 8 | 0.437 % | No |
to the | 8 | 0.437 % | No |
on the | 8 | 0.437 % | No |
Moor is | 7 | 0.383 % | No |
2014 at | 7 | 0.383 % | No |
of Baildon | 7 | 0.383 % | No |
2013 at | 6 | 0.328 % | No |
with the | 5 | 0.273 % | No |
wind farm | 5 | 0.273 % | No |
in the | 5 | 0.273 % | No |
is not | 5 | 0.273 % | No |
says July | 5 | 0.273 % | No |
is a | 4 | 0.219 % | No |
I have | 4 | 0.219 % | No |
of access | 4 | 0.219 % | No |
to be | 4 | 0.219 % | No |
Friends of | 4 | 0.219 % | No |
do not | 4 | 0.219 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Baildon Moor is | 7 | 0.383 % | No |
of Baildon Moor | 6 | 0.328 % | No |
Friends of Baildon | 4 | 0.219 % | No |
on the moor | 4 | 0.219 % | No |
Moor is a | 4 | 0.219 % | No |
a wind farm | 3 | 0.164 % | No |
on the Moor | 3 | 0.164 % | No |
Baildon Moor as | 3 | 0.164 % | No |
wind farm on | 3 | 0.164 % | No |
on Baildon Moor | 3 | 0.164 % | No |
12 2014 at | 2 | 0.109 % | No |
this is only | 2 | 0.109 % | No |
the CROW Act | 2 | 0.109 % | No |
of the CROW | 2 | 0.109 % | No |
your email address | 2 | 0.109 % | No |
rights of way | 2 | 0.109 % | No |
The Friends of | 2 | 0.109 % | No |
public rights of | 2 | 0.109 % | No |
CROW access rights | 2 | 0.109 % | No |
21 2013 at | 2 | 0.109 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Friends of Baildon Moor | 4 | 0.219 % | No |
Baildon Moor is a | 4 | 0.219 % | No |
a wind farm on | 3 | 0.164 % | No |
of the CROW Act | 2 | 0.109 % | No |
public rights of way | 2 | 0.109 % | No |
wind farm on Baildon | 2 | 0.109 % | No |
farm on Baildon Moor | 2 | 0.109 % | No |
Moor The Friends of | 2 | 0.109 % | No |
The Friends of Baildon | 2 | 0.109 % | No |
of Baildon Moor is | 2 | 0.109 % | No |
Baildon Moor The Friends | 2 | 0.109 % | No |
says July 12 2014 | 2 | 0.109 % | No |
July 12 2014 at | 2 | 0.109 % | No |
Hannie says July 12 | 2 | 0.109 % | No |
section 193 of the | 1 | 0.055 % | No |
is a common registered | 1 | 0.055 % | No |
common because the section | 1 | 0.055 % | No |
urban common because the | 1 | 0.055 % | No |
socalled urban common because | 1 | 0.055 % | No |
Moor is a common | 1 | 0.055 % | 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 | baildonmoor.org | IN | 3597 | A | 89.238.188.209 | ||
2 | baildonmoor.org | IN | 3597 | NS | d.ns.ns247.net | ||
3 | baildonmoor.org | IN | 3597 | NS | b.ns.ns247.net | ||
4 | baildonmoor.org | IN | 3597 | NS | c.ns.ns247.net | ||
5 | baildonmoor.org | IN | 3597 | NS | a.ns.ns247.net | ||
6 | baildonmoor.org | IN | 3600 | MX | 10 | mail.baildonmoor.org |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | http://baildonmoor.org/wordpress/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 826 |
request size | 423 | filetime | -1 |
ssl verify result | 0 | redirect count | 2 |
total time | 1.756389 | namelookup time | 1.9E-5 |
connect time | 2.0E-5 | pretransfer time | 4.7E-5 |
size upload | 0 | size download | 49746 |
speed download | 28322 | speed upload | 0 |
download content length | -1 | upload content length | -1 |
starttransfer time | 0.619247 | redirect time | 0.949211 |
redirect url | primary ip | 89.238.188.209 | |
certinfo | primary port | 80 | |
local ip | 204.48.18.59 | local port | 49128 |
46 requests • 614 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 4,040 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 7 KiB
Optimized images load faster and consume less cellular data. Learn More
Potential savings of 275 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
32 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 0 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
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn More
12117 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
40 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 3 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 24 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 228 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn More
Total size was 614 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
Potential savings of 35 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. 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
358 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 2 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
47 requests • 607 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 1,090 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 7 KiB
Optimized images load faster and consume less cellular data. Learn More
Potential savings of 275 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
32 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 0 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
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn More
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.0 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
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 20 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 222 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn More
Total size was 607 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
0.3 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 36 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. 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
358 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 380 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 2 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