A Pontuação deste Site é

Com Ranking Similar

51
BioPeixe - aquariofilia & aquarismo aquario peixe
biopeixe.com
51
FNAC - CULTURA, TECNOLOGIA, LAZER
fnac.pt
51
CTT: PARTICULARES, EMPRESAS E GRUPO CTT
ctt.pt
51
QCQ - QUALQUERCOISAQUI
qualquercoisaqui.blogspot.com.br
51
Professor Personal | Curso de inglês com professor particular em SP
professorpersonal.com.br
51
ATIVIDADES PARA PROFESSORES
atividadesparaprofessores.com.br
51
Jornal Diário da Lagoa
diariodalagoa.com

Últimos Sites Analisados

56
CODISTEC
codistec.com
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

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

51 ctt.pt Última Análise: 2 semanas

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

Desktop

Móvel

Performance Desktop Score 83%
Best Practices Desktop Score 79%
SEO Desktop Score 82%
Progressive Web App Desktop Score 56%
Performance Mobile Score 60%
Best Practices Mobile Score 79%
SEO Mobile Score 89%
Progressive Web App Mobile Score 0%
Autoridade da Página Autoridade 46%
Autoridade do Domínio Autoridade do Domínio 64%
Moz Rank 4.6/10
Taxas de Rejeição Taxa 0%
Charset Encoding
Excelente, a codificação de idioma / carateres é especificada: UTF-8
Tag Título 39 Carateres
CTT: PARTICULARES, EMPRESAS E GRUPO CTT
Descrição Meta 91 Carateres
500 anos de dedicação, empenho e profissionalismo, para aproximar os portugueses e o mundo.
URL Efetivo 37 Carateres
https://www.ctt.pt/particulares/index
Excerto Conteúdo da página
CTT: Particulares, Empresas e Grupo CTT Consulte os al...
Núvem de Keywords Densidade
mais28 saiba16 para12 online9 correio8 casa8 enviar8 links7 rápidos7 encontrar7
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
mais 28
saiba 16
para 12
online 9
correio 8
casa 8
enviar 8
links 7
rápidos 7
encontrar 7
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
CTT: PARTICULARES, EMPRESAS E GRUPO CTT
https://www.ctt.pt/particulares/index
500 anos de dedicação, empenho e profissionalismo, para aproximar os portugueses e o mundo.
Robots.txt Ficheiro não encontrado
Sitemap.xml Ficheiro não encontrado
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Atualizado em: 1970-01-01 / 51 anos
Criado em: 1970-01-01 / 51 anos
Expira em: 2024-06-06 / 41 meses 7 dias

DMNS - DOMINIOS, S.A.
Admin Email: dns@dominios.pt,mailmanager@dominios.pt

Nameservers
dns.ctt.pt
|
IPv4:
194.65.57.130
and
IPv6:
dns2.ctt.pt
|
IPv4:
62.28.143.223
and
IPv6:
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~88.33 KB
Tamanho do Código: ~35.4 KB
Tamanho do Texto: ~52.93 KB Ratio: 59.92%

Redes Sociais

Delicious Total: 0
Facebook Total: 12,294
Google Total: 0
Linkedin Total: 0
Pinterest Total: 30
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
Avoid enormous network payloads Total size was 6,078 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images Potential savings of 3,533 KiB
Optimized images load faster and consume less cellular data
Properly size images Potential savings of 2,187 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Preload key requests Potential savings of 590 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize third-party usage Third-party code blocked the main thread for 0 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
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 83 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
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/).
Cumulative Layout Shift 0.405
Cumulative Layout Shift measures the movement of visible elements within the viewport
Uses efficient cache policy on static assets 2 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoid an excessive DOM size 847 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)
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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 66 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
Minify JavaScript Potential savings of 29 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
JavaScript execution time 0.1 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
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
Largest Contentful Paint 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 320 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve images in next-gen formats Potential savings of 4,576 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
Avoid chaining critical requests 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
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
Keep request counts low and transfer sizes small 58 requests • 6,078 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Defer offscreen images Potential savings of 546 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minimizes main-thread work 0.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 1.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

Móvel

Screenshot Móvel
Total Blocking Time 200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve images in next-gen formats Potential savings of 4,567 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 third-party usage Third-party code blocked the main thread for 30 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
Estimated Input Latency 20 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
Remove unused CSS Potential savings of 68 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
Keep request counts low and transfer sizes small 55 requests • 6,026 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript Potential savings of 84 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid an excessive DOM size 847 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)
Avoid enormous network payloads Total size was 6,026 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Eliminate render-blocking resources Potential savings of 1,120 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 3.1 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Time to Interactive 6.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint (3G) 4383.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Cumulative Layout Shift 0.208
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
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
First Contentful Paint 2.2 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 6.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify JavaScript Potential savings of 29 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Preload key requests Potential savings of 3,480 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 5.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Tap targets are not sized appropriately 69% 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
Reduce initial server response time Root document took 800 ms
Keep the server response time for the main document short because all other requests depend on it
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
Efficiently encode images Potential savings of 3,533 KiB
Optimized images load faster and consume less cellular data
Properly size images Potential savings of 217 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Uses efficient cache policy on static assets 2 resources found
A long cache lifetime can speed up repeat visits to your page
First CPU Idle 4.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/).
Avoid chaining critical requests 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

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: Thu, 31 Dec 2020 01:31:54 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
Set-Cookie: JSESSIONID=6u3l7McffmB5HXndd84M4xF-gQrupABEbeDQWiE7.frontend-server-one-41; path=/
Set-Cookie: dmid=0ba93cc0-1a7d-48bb-ab96-285dda716376; path=/; Max-Age=153792000; Expires=Sat, 15-Nov-2025 01:31:54 GMT
Set-Cookie: opvc=0b189136-2536-4b18-8391-1ccfaf71e315; path=/
Set-Cookie: sitevisitscookie=1; path=/; Max-Age=153792000; Expires=Sat, 15-Nov-2025 01:31:54 GMT
Content-Type: text/html;charset=UTF-8
Cache-Control: max-age=0
Expires: Thu, 31 Dec 2020 01:37:54 GMT
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Secure-Policy: default-src 'self';
Connection: close
Registos DNS Registros de recursos DNS associados a um nome de host
Clique aqui para listar os Registos DNS

Comentários