Powered by https://www.piqes.com.br ()
examinado em : 23-11-16 17:19:29
siga as recomendações deste relatório de saúde para manter seu site saudável
Manual: A plataforma de destino para a saúde masculina
O título da sua página não excede 60 caracteres. Está bem.
Tratamentos com eficácia comprovada. Trate a sua queda capilar e melhore o seu sono de forma segura e prática, sem sair de casa.
Sua meta descrição não excede 150 caracteres. Está bem.
Seu site não tem nenhuma palavra-chave meta.
Palavra-chave | Ocorrência | Densidade | Possível Spam |
---|---|---|---|
de | 29 | 2.749 % | No |
tratamento | 14 | 1.327 % | No |
em | 12 | 1.137 % | No |
para | 12 | 1.137 % | No |
queda | 11 | 1.043 % | No |
é | 11 | 1.043 % | No |
meses | 10 | 0.948 % | No |
os | 10 | 0.948 % | No |
mais | 9 | 0.853 % | No |
Minoxidil | 8 | 0.758 % | No |
Finasterida | 8 | 0.758 % | No |
seu | 7 | 0.664 % | No |
fios | 7 | 0.664 % | No |
dos | 7 | 0.664 % | No |
capilar | 7 | 0.664 % | No |
da | 7 | 0.664 % | No |
já | 7 | 0.664 % | No |
agora | 6 | 0.569 % | No |
DHT | 6 | 0.569 % | No |
Começar | 5 | 0.474 % | No |
Palavra-chave | Ocorrência | Densidade | Possível Spam |
---|---|---|---|
queda capilar | 6 | 0.569 % | No |
Começar agora | 5 | 0.474 % | No |
de novos | 4 | 0.379 % | No |
Finasterida e | 4 | 0.379 % | No |
o tratamento | 4 | 0.379 % | No |
Dia 1 | 4 | 0.379 % | No |
1 3 | 4 | 0.379 % | No |
3 meses | 4 | 0.379 % | No |
Verified review | 4 | 0.379 % | No |
fios e | 3 | 0.284 % | No |
a queda | 3 | 0.284 % | No |
novos fios | 3 | 0.284 % | No |
homens que | 3 | 0.284 % | No |
que fizeram | 3 | 0.284 % | No |
dos fios | 3 | 0.284 % | No |
Plano Completo | 3 | 0.284 % | No |
Completo Com | 3 | 0.284 % | No |
Com Finasterida | 3 | 0.284 % | No |
e Minoxidil | 3 | 0.284 % | No |
Minoxidil Verified | 3 | 0.284 % | No |
Palavra-chave | Ocorrência | Densidade | Possível Spam |
---|---|---|---|
Dia 1 3 | 4 | 0.379 % | No |
1 3 meses | 4 | 0.379 % | No |
de novos fios | 3 | 0.284 % | No |
Plano Completo Com | 3 | 0.284 % | No |
Completo Com Finasterida | 3 | 0.284 % | No |
Com Finasterida e | 3 | 0.284 % | No |
Finasterida e Minoxidil | 3 | 0.284 % | No |
e Minoxidil Verified | 3 | 0.284 % | No |
Minoxidil Verified review | 3 | 0.284 % | No |
Verified review Dia | 3 | 0.284 % | No |
review Dia 1 | 3 | 0.284 % | No |
DHT um hormônio | 2 | 0.19 % | No |
um hormônio masculino | 2 | 0.19 % | No |
no couro cabeludo | 2 | 0.19 % | No |
a queda de | 2 | 0.19 % | No |
dos homens que | 2 | 0.19 % | No |
homens que fizeram | 2 | 0.19 % | No |
que fizeram tratamento | 2 | 0.19 % | No |
para queda capilar | 2 | 0.19 % | No |
de queda capilar | 2 | 0.19 % | No |
Palavra-chave | Ocorrência | Densidade | Possível Spam |
---|---|---|---|
Dia 1 3 meses | 4 | 0.379 % | No |
Plano Completo Com Finasterida | 3 | 0.284 % | No |
Completo Com Finasterida e | 3 | 0.284 % | No |
Com Finasterida e Minoxidil | 3 | 0.284 % | No |
Finasterida e Minoxidil Verified | 3 | 0.284 % | No |
e Minoxidil Verified review | 3 | 0.284 % | No |
Verified review Dia 1 | 3 | 0.284 % | No |
review Dia 1 3 | 3 | 0.284 % | No |
DHT um hormônio masculino | 2 | 0.19 % | No |
dos homens que fizeram | 2 | 0.19 % | No |
homens que fizeram tratamento | 2 | 0.19 % | No |
Minoxidil Verified review Dia | 2 | 0.19 % | No |
Eu to aqui de | 2 | 0.19 % | No |
to aqui de prova | 2 | 0.19 % | No |
realmente em mim funcionou | 2 | 0.19 % | No |
Adorei o produto e | 2 | 0.19 % | No |
o produto e realmente | 2 | 0.19 % | No |
produto e realmente está | 2 | 0.19 % | No |
e realmente está funcionando | 2 | 0.19 % | No |
Entrega grátis e discreta | 2 | 0.19 % | No |
As palavras-chave mais usadas não correspondem às palavras-chave meta.
Seu site não tem mapa do site
1055
Teste de Razão Texto/HTML : 16%
Seu site não tem 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.
Os links do seu site são amigáveis para SEO.
O site falhou no teste de e-mail de texto simples.1e-mail de texto simples encontrado.
A página tem tipo de documento.
Seu site não possui nenhuma imagem sem texto alternativo.
Seu site não possui nenhuma tag HTML depreciada.
O tamanho da página HTML é > 100 KB
A compactação GZIP está desativada.
Seu site não possui CSS embutido.
seu site tem 5 CSS interno.
O site falhou no teste de esquema de microdados.
SL | Hospedar | Aula | TTL | Tipo | PRI | Alvo | IP |
---|---|---|---|---|---|---|---|
1 | proxy-ssl-geo.webflow.com | IN | 58 | A | 44.238.105.202 | ||
2 | proxy-ssl-geo.webflow.com | IN | 58 | A | 44.227.170.101 | ||
3 | proxy-ssl-geo.webflow.com | IN | 58 | A | 44.238.31.106 | ||
4 | hello.manual.com.br | IN | 58 | CNAME | proxy-ssl.webflow.com |
O site falhou no teste de canonização de IP.
O site falhou no teste de canonização do URL.
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
Potential savings of 2,510 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Saber mais
Optimized images load faster and consume less cellular data. Saber mais
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Saber mais
18 resources found
A long cache lifetime can speed up repeat visits to your page. Saber mais
Third-party code blocked the main thread for 1,550 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. Saber mais
1,140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
4.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Saber mais
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Saber mais
180 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. Saber mais
Potential savings of 124 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Saber mais
Potential savings of 19 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Saber mais
Total size was 1,538 KiB
Large network payloads cost users real money and are highly correlated with long load times. Saber mais
6.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Saber mais
15 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. Saber mais
405 elements
A large DOM will increase memory usage, cause longer Saber mais
Redirects introduce additional delays before the page can be loaded. Saber mais
Minifying JavaScript files can reduce payload sizes and script parse time. Saber mais
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Saber mais
70 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. Saber mais
Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Saber mais
Optimized images load faster and consume less cellular data. Saber mais
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Saber mais
18 resources found
A long cache lifetime can speed up repeat visits to your page. Saber mais
Third-party code blocked the main thread for 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. Saber mais
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Saber mais
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Saber mais
450 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. Saber mais
Potential savings of 251 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Saber mais
Potential savings of 20 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Saber mais
Total size was 1,663 KiB
Large network payloads cost users real money and are highly correlated with long load times. Saber mais
2.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Saber mais
15 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. Saber mais
402 elements
A large DOM will increase memory usage, cause longer Saber mais
Redirects introduce additional delays before the page can be loaded. Saber mais
Minifying JavaScript files can reduce payload sizes and script parse time. Saber mais
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Saber mais
110 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. Saber mais