Powered by https://sitehealthcheck.net ()
examined at : 24-04-10 19:51:15
follow recommendations of this health report to keep your site healthy
Automated Meeting Reports, Transcripts, Notes, Video, Coaching, Scheduling | Read
Your page title exceeds 60 characters. It's not good.
In a hybrid world, Read improves meeting wellness through better scheduling, real-time analytics, summaries, transcription, playback, and automated recommendations. On average, Read identifies 20 meeting hours a month that could be eliminated.
Your meta description exceeds 150 characters. It's not good.
Your site do not have any meta keyword.
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Read | 15 | 3 % | No |
meetings | 9 | 1.8 % | No |
AI | 9 | 1.8 % | No |
items | 5 | 1 % | No |
summaries | 5 | 1 % | No |
free | 5 | 1 % | Yes |
Summaries | 4 | 0.8 % | No |
questions | 4 | 0.8 % | No |
key | 4 | 0.8 % | No |
meeting | 4 | 0.8 % | No |
messages | 4 | 0.8 % | No |
action | 3 | 0.6 % | No |
Meetings | 3 | 0.6 % | No |
Summarize | 3 | 0.6 % | No |
Productivity | 3 | 0.6 % | No |
transcripts | 3 | 0.6 % | No |
data | 3 | 0.6 % | No |
emails | 3 | 0.6 % | No |
Meeting | 3 | 0.6 % | No |
productivity | 3 | 0.6 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Read AI | 6 | 1.2 % | No |
your meetings | 4 | 0.8 % | No |
action items | 3 | 0.6 % | No |
items and | 3 | 0.6 % | No |
key questions | 3 | 0.6 % | No |
meeting summaries | 2 | 0.4 % | No |
Productivity AI | 2 | 0.4 % | No |
for your | 2 | 0.4 % | No |
email and | 2 | 0.4 % | No |
and key | 2 | 0.4 % | No |
Meetings Meeting | 2 | 0.4 % | No |
and messages | 2 | 0.4 % | No |
emails and | 2 | 0.4 % | No |
your data | 2 | 0.4 % | No |
with your | 2 | 0.4 % | No |
and more | 2 | 0.4 % | No |
Get started | 2 | 0.4 % | No |
started for | 2 | 0.4 % | No |
for free | 2 | 0.4 % | No |
meet Unbiased | 1 | 0.2 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
started for free | 2 | 0.4 % | No |
action items and | 2 | 0.4 % | No |
Get started for | 2 | 0.4 % | No |
items and key | 2 | 0.4 % | No |
and key questions | 2 | 0.4 % | No |
Read AI’s Terms | 1 | 0.2 % | No |
wherever you meet | 1 | 0.2 % | No |
from millions of | 1 | 0.2 % | No |
data from millions | 1 | 0.2 % | No |
harnesses data from | 1 | 0.2 % | No |
Read harnesses data | 1 | 0.2 % | No |
feedback Read harnesses | 1 | 0.2 % | No |
programmatic feedback Read | 1 | 0.2 % | No |
Unbiased programmatic feedback | 1 | 0.2 % | No |
meet Unbiased programmatic | 1 | 0.2 % | No |
you meet Unbiased | 1 | 0.2 % | No |
meeting summaries wherever | 1 | 0.2 % | No |
summaries wherever you | 1 | 0.2 % | No |
of interactions incorporating | 1 | 0.2 % | No |
for meeting summaries | 1 | 0.2 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Get started for free | 2 | 0.4 % | No |
items and key questions | 2 | 0.4 % | No |
Read AI’s Terms of | 1 | 0.2 % | No |
you meet Unbiased programmatic | 1 | 0.2 % | No |
interactions incorporating both verbal | 1 | 0.2 % | No |
of interactions incorporating both | 1 | 0.2 % | No |
millions of interactions incorporating | 1 | 0.2 % | No |
from millions of interactions | 1 | 0.2 % | No |
data from millions of | 1 | 0.2 % | No |
harnesses data from millions | 1 | 0.2 % | No |
Read harnesses data from | 1 | 0.2 % | No |
feedback Read harnesses data | 1 | 0.2 % | No |
programmatic feedback Read harnesses | 1 | 0.2 % | No |
Unbiased programmatic feedback Read | 1 | 0.2 % | No |
meet Unbiased programmatic feedback | 1 | 0.2 % | No |
wherever you meet Unbiased | 1 | 0.2 % | No |
both verbal and visual | 1 | 0.2 % | No |
summaries wherever you meet | 1 | 0.2 % | No |
meeting summaries wherever you | 1 | 0.2 % | No |
for meeting summaries wherever | 1 | 0.2 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://www.read.ai/sitemap.xml
500
Text/HTML Ratio Test : 7%
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.
Some links of your site are not SEO friendly.
Site failed plain text email test.1plain text email found.
Page have doc type.
Your site have 53 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 10 inline css.
Your site have 22 internal css.
Site failed micro data schema test.
SL | Host | Class | TTL | Type | PRI | Target | IP |
---|---|---|---|---|---|---|---|
1 | read.ai | IN | 300 | A | 99.83.190.102 | ||
2 | read.ai | IN | 300 | A | 75.2.70.75 | ||
3 | read.ai | IN | 60 | NS | ns-1395.awsdns-46.org | ||
4 | read.ai | IN | 60 | NS | ns-168.awsdns-21.com | ||
5 | read.ai | IN | 60 | NS | ns-1739.awsdns-25.co.uk | ||
6 | read.ai | IN | 60 | NS | ns-731.awsdns-27.net | ||
7 | read.ai | IN | 60 | MX | 1 | aspmx.l.google.com | |
8 | read.ai | IN | 60 | MX | 10 | aspmx2.googlemail.com | |
9 | read.ai | IN | 60 | MX | 10 | aspmx3.googlemail.com | |
10 | read.ai | IN | 60 | MX | 5 | alt1.aspmx.l.google.com | |
11 | read.ai | IN | 60 | MX | 5 | alt2.aspmx.l.google.com |
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 2,100 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
18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 4,370 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
4,710 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
6.8 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
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 227 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 98 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,320 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
10.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
26 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
648 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 780 ms
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
20 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 210 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
22 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 170 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
220 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.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
350 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 544 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 99 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,437 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
26 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
648 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 230 ms
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
160 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