A Pontuação deste Site é

Com Ranking Similar

2
IOL - NOTÍCIAS, EMPRESAS E BLOGS.
iol.pt
2
GEOCOMPASS
geocompass.pt
2
EMPRESA DE TRANSPORTES-INDISLOG TRANSPORTES LDA
indislog.com
2
MODA ESPORTIVA, MODA PRAIA E NATAÇÃO - TAQUION
taquion.com.br
2
HOMEPAGE - IDEALBIZ
idealbiz.pt
2
EPOXITINTAS
epoxitintas.com.br
2
ESCOLA DE CÃES
escoladecaes.pt

Últimos Sites Analisados

29
KIMIPLAN LDA
kimiplan.pt
33
WISHIRT T-SHIRTS PERSONALIZADAS
wishirt.com
37
IMOTOR - CARROS USADOS, AUTOMÓVEIS USADOS
imotor.pt
19
JORGE DANIEL MENDES FERREIRA
jorgedanielmendesferreira.com
19
ESCOLA DE CÃES
escoladecaes.com
2
GEOCOMPASS
geocompass.pt

Top das Tecnologias

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

2 escoladecaes.pt Última Análise: 2 semanas

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

Desktop

Móvel

Performance Desktop Score 82%
Best Practices Desktop Score 73%
SEO Desktop Score 80%
Progressive Web App Desktop Score 18%
Performance Mobile Score 52%
Best Practices Mobile Score 67%
SEO Mobile Score 83%
Progressive Web App Mobile Score 17%
Autoridade da Página Autoridade 1%
Autoridade do Domínio Autoridade do Domínio 8%
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 14 Carateres
ESCOLA DE CÃES
Descrição Meta 54 Carateres
Na Escola de Cães Treinamos, Tratamos e Passeamos Cães
URL Efetivo 22 Carateres
http://escoladecaes.pt
Excerto Conteúdo da página
Escola de Cães ...
Núvem de Keywords Densidade
para5 treino5 seja4 fundamental3 processo3 tutor3 isso3 todo3 cães2 escola2
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
para 5
treino 5
seja 4
fundamental 3
processo 3
tutor 3
isso 3
todo 3
cães 2
escola 2
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
ESCOLA DE CÃES
http://escoladecaes.pt
Na Escola de Cães Treinamos, Tratamos e Passeamos Cães
Robots.txt Ficheiro não encontrado
Sitemap.xml Ficheiro não encontrado
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~12.16 KB
Tamanho do Código: ~7.83 KB
Tamanho do Texto: ~4.32 KB Ratio: 35.55%

Redes Sociais

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
Reduce unused JavaScript Potential savings of 437 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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
Reduce unused CSS Potential savings of 61 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid enormous network payloads Total size was 2,830 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Eliminate render-blocking resources Potential savings of 600 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Initial server response time was short Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Does not use HTTPS 38 insecure requests 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 served over 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
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 138 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)
Minimize third-party usage Third-party code blocked the main thread for 70 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.342
Cumulative Layout Shift measures the movement of visible elements within the viewport
Keep request counts low and transfer sizes small 56 requests • 2,830 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 32 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests 24 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
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Defer offscreen images Potential savings of 1,708 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 56 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Serve images in next-gen formats Potential savings of 1,522 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Móvel

Screenshot Móvel
Serve images in next-gen formats Potential savings of 1,522 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce the impact of third-party code Third-party code blocked the main thread for 730 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
Does not use HTTPS 38 insecure requests 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 served over 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
Total Blocking Time 420 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size 138 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)
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Avoid enormous network payloads Total size was 2,832 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce unused JavaScript Potential savings of 453 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid chaining critical requests 24 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
Cumulative Layout Shift 0.365
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 420 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 1,990 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
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
Speed Index 9.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Properly size images Potential savings of 510 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 3.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce unused CSS Potential savings of 61 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy 32 resources found
A long cache lifetime can speed up repeat visits to your page
Includes front-end JavaScript libraries with known security vulnerabilities 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize main-thread work 2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 13.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
First Contentful Paint (3G) 5520 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Initial server response time was short Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it
Keep request counts low and transfer sizes small 56 requests • 2,832 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

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: Wed, 15 Sep 2021 00:24:48 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.25
Set-Cookie: ci_session=a%3A5%3A%7Bs%3A10%3A%22session_id%22%3Bs%3A32%3A%22d4e1432022c789c98a568c401f0faa0e%22%3Bs%3A10%3A%22ip_address%22%3Bs%3A14%3A%22185.31.158.187%22%3Bs%3A10%3A%22user_agent%22%3Bb%3A0%3Bs%3A13%3A%22last_activity%22%3Bi%3A1631665488%3Bs%3A9%3A%22user_data%22%3Bs%3A0%3A%22%22%3B%7D12962c892f1ff26c673112aa92f1a0d3; expires=Wed, 15-Sep-2021 02:24:48 GMT; Max-Age=7200; path=/
Content-Type: text/html
Registos DNS Registros de recursos DNS associados a um nome de host
Clique aqui para listar os Registos DNS

Comentários