A Pontuação deste Site é

Com Ranking Similar

47
Instituto Português do Mar e da Atmosfera
meteo.pt
47
ACHIX - TELEFONES DE EMPRESAS E ASSISTÊNCIAS DO BRASIL.
achix.com.br
47
FREE ADVERTISEMENT IN INDIA, FREE CLASSIFIEDS IN INDIA
kippee.com
47
DIÁRIO DE NOTÍCIAS MADEIRA | DNOTICIAS.PT
dnoticias.pt
47
→ CineFire // FILMAGEM DE CASAMENTO, Atendemos todo Brasil.
cinefire.com.br
47
CONSERVADORA DE FACHADAS 3357 19 61
limpeza-de-fachada-31-3357-19-61.webnode.com

Últimos Sites Analisados

29
KIMIPLAN LDA
kimiplan.pt
37
IMOTOR - CARROS USADOS, AUTOMÓVEIS USADOS
imotor.pt
45
WISHIRT T-SHIRTS PERSONALIZADAS
wishirt.com
19
JORGE DANIEL MENDES FERREIRA
jorgedanielmendesferreira.com
19
ESCOLA DE CÃES
escoladecaes.com
2
GEOCOMPASS
geocompass.pt
20
KABUM! - EXPLOSO DE PREOS BAIXOS!
kabum.com.br

Top das Tecnologias

Google Font API
Font Scripts
Gzip
Compress
Apache
Web Servers
Google Analytics
Analytics
WordPress
CMS
Nginx
Web Servers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks

47 eqilibrium.net Última Análise: 2 semanas

Sucesso 63% passos de análise realizados
Aviso 30% total de avisos
Erros 7% de erros detetados. Estes erros exigem ação rápida

Desktop

Móvel

Performance Desktop Score 94%
Best Practices Desktop Score 79%
SEO Desktop Score 83%
Progressive Web App Desktop Score 37%
Performance Mobile Score 58%
Best Practices Mobile Score 71%
SEO Mobile Score 71%
Progressive Web App Mobile Score 36%
Autoridade da Página Autoridade 33%
Autoridade do Domínio Autoridade do Domínio 23%
Moz Rank 0.0/10
Taxas de Rejeição Taxa 0%
Charset Encoding
Excelente, a codificação de idioma / carateres é especificada: UTF-8
Tag Título 94 Carateres
E.QI.LIBRIUM HERBS - HERBOLARIO DE FITOTERAPIA CHINA - FARMACOPEA - MEDICINA TRADICIONAL CHINA
Descrição Meta 294 Carateres
La Fitoterapia China es utilizada para tratar una gran variedad de enfermedades y problemas. Sus remedios son 100% naturales, hechos de plantas y sus derivados y son, sin duda alguna, eficaces y de accion rapida. La Fitoterapia China es utilizada hace miles de años con efectos extraordinarios.
URL Efetivo 29 Carateres
https://www.eqilibrium.net/es
Excerto Conteúdo da página
E.Qi.Librium Herbs - Herbolario de Fitoterapia China - Farmacopea - Medicina Tradicional China ...
Núvem de Keywords Densidade
blue6 poppy6 precio6 código6 unitario6 cuenta6 esta5 noticias4 entrar4 contraseña4
Consistência das Keyword A densidade de palavras-chave é um dos principais termos em SEO
Keyword Freq. Título Descrição Domínio H1 H2
blue 6
poppy 6
precio 6
código 6
unitario 6
cuenta 6
esta 5
noticias 4
entrar 4
contraseña 4
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
E.QI.LIBRIUM HERBS - HERBOLARIO DE FITOTERAPIA CHINA - FARMA
https://www.eqilibrium.net/es
La Fitoterapia China es utilizada para tratar una gran variedad de enfermedades y problemas. Sus remedios son 100% naturales, hechos de plantas y sus
Robots.txt Ficheiro detetado
Sitemap.xml Ficheiro detetado
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~107.31 KB
Tamanho do Código: ~69.43 KB
Tamanho do Texto: ~37.87 KB Ratio: 35.30%

Redes Sociais

Delicious Total: 0
Facebook Total: 153
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Tecnologias Aplicadas

Disponível Apenas a Usuários Registrados

Faça o registo GRATUITO e rápido para conseguir consultar um relatório mais detalhado sobre este e outros sites de língua Portuguesa

Entrar

PWA - Manifest

O Manifesto do aplicativo web não é válido
O seu site não tem um ficheiro manifest.json válido, leia mais em Web App Manifesto

Desktop

Screenshot do Desktop
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats Potential savings of 480 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
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Server Backend Latencies 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
Network Round Trip Times 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
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS Potential savings of 31 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
Minimize third-party usage Third-party code blocked the main thread for 40 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
Cumulative Layout Shift 0.074
Cumulative Layout Shift measures the movement of visible elements within the viewport
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy 41 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Preload key requests Potential savings of 350 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids enormous network payloads Total size was 1,207 KiB
Large network payloads cost users real money and are highly correlated with long load times
Keep request counts low and transfer sizes small 52 requests • 1,207 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 420 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 18 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 8 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
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid an excessive DOM size 1,019 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Estimated Input Latency 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
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused JavaScript Potential savings of 203 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce initial server response time Root document took 770 ms
Keep the server response time for the main document short because all other requests depend on it

Móvel

Screenshot Móvel
Max Potential First Input Delay 340 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 3.1 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 610 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
JavaScript execution time 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 480 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
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid chaining critical requests 8 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Server Backend Latencies 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
Remove unused CSS Potential savings of 31 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
Remove unused JavaScript Potential savings of 203 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Estimated Input Latency 40 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
Time to Interactive 6.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 6690 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint 6.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce initial server response time Root document took 790 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift 0.036
Cumulative Layout Shift measures the movement of visible elements within the viewport
First CPU Idle 5.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Speed Index 4.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Preload key requests Potential savings of 1,830 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Avoids enormous network payloads Total size was 1,251 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid an excessive DOM size 1,019 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Keep request counts low and transfer sizes small 52 requests • 1,251 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Network Round Trip Times 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
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Serve static assets with an efficient cache policy 41 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Potential savings of 480 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
Minimize main-thread work 2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

Dicas de Otimização e Velocidade

Disponível Apenas a Usuários Registrados

Faça o registo GRATUITO e rápido para conseguir consultar um relatório mais detalhado sobre este e outros sites de língua Portuguesa

Entrar

Ranking Alexa

99,999,999

Ranking Global

99,999,999

-
Tráfego
Busca

Domínio Disponível

Disponível Apenas a Usuários Registrados

Faça o registo GRATUITO e rápido para conseguir consultar um relatório mais detalhado sobre este e outros sites de língua Portuguesa

Entrar

Informações do Servidor

Resposta do Header Os cabeçalhos HTTP carregam informações sobre o navegador do cliente, a página solicitada e o servidor
HTTP/1.1 200 OK
Date: Mon, 14 Sep 2020 11:03:02 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Set-Cookie: sid_customer_860bd=80d8f9c5edb7dc6e5a85156ed8f89809-1-C; expires=Tue, 15-Sep-2020 11:03:03 GMT; Max-Age=86400; path=/; domain=.eqilibrium.net; HttpOnly
Vary: User-Agent
Content-Type: text/html; charset=utf-8
Registos DNS Registros de recursos DNS associados a um nome de host
Clique aqui para listar os Registos DNS

Comentários