Follow recommendations of this health report to keep your site healthy
Examined at : 2025-05-24 02:22:40
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Menu | 4 | 7.273 % | No |
Home | 3 | 5.455 % | Yes |
Tour | 3 | 5.455 % | No |
Merch | 3 | 5.455 % | No |
Contact | 3 | 5.455 % | No |
Deluxe | 2 | 3.636 % | No |
Ghosts | 2 | 3.636 % | No |
Edition | 2 | 3.636 % | No |
Backyard | 2 | 3.636 % | No |
Close | 2 | 3.636 % | No |
Open | 2 | 3.636 % | Yes |
Abi | 1 | 1.818 % | No |
Preorder | 1 | 1.818 % | No |
© | 1 | 1.818 % | No |
Signup | 1 | 1.818 % | No |
List | 1 | 1.818 % | No |
1 | 1.818 % | No | |
Skip | 1 | 1.818 % | No |
fullsize | 1 | 1.818 % | No |
View | 1 | 1.818 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Home About | 3 | 5.455 % | No |
About Tour | 3 | 5.455 % | No |
Tour Merch | 3 | 5.455 % | No |
Merch Contact | 3 | 5.455 % | No |
Deluxe Edition | 2 | 3.636 % | No |
Close Menu | 2 | 3.636 % | No |
in the | 2 | 3.636 % | No |
Ghosts in | 2 | 3.636 % | No |
Menu Home | 2 | 3.636 % | No |
Menu Close | 2 | 3.636 % | No |
Backyard Deluxe | 2 | 3.636 % | No |
Open Menu | 2 | 3.636 % | No |
Contact Open | 2 | 3.636 % | No |
the Backyard | 2 | 3.636 % | No |
fullsize Preorder | 1 | 1.818 % | No |
Preorder Here | 1 | 1.818 % | No |
Here Email | 1 | 1.818 % | No |
View fullsize | 1 | 1.818 % | No |
© Abi | 1 | 1.818 % | No |
Email List | 1 | 1.818 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Home About Tour | 3 | 5.455 % | No |
About Tour Merch | 3 | 5.455 % | No |
Tour Merch Contact | 3 | 5.455 % | No |
the Backyard Deluxe | 2 | 3.636 % | No |
Close Menu Home | 2 | 3.636 % | No |
in the Backyard | 2 | 3.636 % | No |
Ghosts in the | 2 | 3.636 % | No |
Menu Home About | 2 | 3.636 % | No |
Menu Close Menu | 2 | 3.636 % | No |
Backyard Deluxe Edition | 2 | 3.636 % | No |
Open Menu Close | 2 | 3.636 % | No |
Contact Open Menu | 2 | 3.636 % | No |
Merch Contact Open | 2 | 3.636 % | No |
View fullsize Preorder | 1 | 1.818 % | No |
fullsize Preorder Here | 1 | 1.818 % | No |
Preorder Here Email | 1 | 1.818 % | No |
Here Email List | 1 | 1.818 % | No |
preorder View fullsize | 1 | 1.818 % | No |
Skip to Content | 1 | 1.818 % | No |
Signup © Abi | 1 | 1.818 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Home About Tour Merch | 3 | 5.455 % | No |
About Tour Merch Contact | 3 | 5.455 % | No |
Ghosts in the Backyard | 2 | 3.636 % | No |
in the Backyard Deluxe | 2 | 3.636 % | No |
the Backyard Deluxe Edition | 2 | 3.636 % | No |
Menu Home About Tour | 2 | 3.636 % | No |
Close Menu Home About | 2 | 3.636 % | No |
Menu Close Menu Home | 2 | 3.636 % | No |
Open Menu Close Menu | 2 | 3.636 % | No |
Contact Open Menu Close | 2 | 3.636 % | No |
Merch Contact Open Menu | 2 | 3.636 % | No |
Tour Merch Contact Open | 2 | 3.636 % | No |
preorder View fullsize Preorder | 1 | 1.818 % | No |
View fullsize Preorder Here | 1 | 1.818 % | No |
fullsize Preorder Here Email | 1 | 1.818 % | No |
Preorder Here Email List | 1 | 1.818 % | No |
for preorder View fullsize | 1 | 1.818 % | No |
Skip to Content Home | 1 | 1.818 % | No |
Signup © Abi Carter | 1 | 1.818 % | No |
Here Email List Signup | 1 | 1.818 % | 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 | ext-sq.squarespace.com | IN | 94 | A | 198.49.23.145 | ||
2 | ext-sq.squarespace.com | IN | 94 | A | 198.185.159.145 | ||
3 | ext-sq.squarespace.com | IN | 94 | A | 198.49.23.144 | ||
4 | ext-sq.squarespace.com | IN | 94 | A | 198.185.159.144 | ||
5 | www.abicartermusic.com | IN | 14365 | CNAME | ext-sq.squarespace.com |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://www.abicartermusic.com/ | content type | text/html;charset=utf-8 |
http code | 200 | header size | 430 |
request size | 216 | filetime | -1 |
ssl verify result | 0 | redirect count | 0 |
total time | 0.132907 | namelookup time | 0.016936 |
connect time | 0.034553 | pretransfer time | 0.078671 |
size upload | 0 | size download | 104975 |
speed download | 795265 | speed upload | 0 |
download content length | -1 | upload content length | -1 |
starttransfer time | 0.099202 | redirect time | 0 |
redirect url | primary ip | 198.49.23.145 | |
certinfo | primary port | 443 | |
local ip | 62.171.178.218 | local port | 36430 |
Aggregates all network requests and groups them by typeLearn More
Est savings of 1,160 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
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 200 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
100 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
10 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
Est savings of 401 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Est savings of 148 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,242 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
0.8 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
360 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
5 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
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
Est savings of 160 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
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 200 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
200 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
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
10 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
Est savings of 974 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Est savings of 149 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,756 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
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
362 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
5 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
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