A Pontuação deste Site é

Com Ranking Similar

37
502 BAD GATEWAY
alagoasnumclick.com.br
37
PORTAL CURSOS HOLÍSTICOS
portalgaia.com.
37
Caricatura em Eventos, Aniversários e Casamentos. Caricaturistas!
abelcosta.com
37
HOMEPAGE | ESEL - ESCOLA SUPERIOR DE ENFERMAGEM DE LISBOA
esel.pt
37
Lisboa E-Nova – Agência de Energia-Ambiente de Lisboa – Lisboa E-Nova – Agência de Energia-Ambiente de Lisboa
lisboaenova.org
37
WILDER - TRAZEMOS-LHE AS NOTÍCIAS, AS HISTÓRIAS E O QUE HÁ DE MELHOR PARA VER NA NATUREZA. SAIBA COMO SER UM NATURALISTA.
wilder.pt

Ú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
29
UNIVERSO DO CONHECIMENTO - EVOLUÇÃO PESSOAL E ESPIRITUAL
universodoconhecimento.com

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

37 esel.pt Última Análise: 2 meses

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

Desktop

Móvel

Performance Desktop Score 44%
Best Practices Desktop Score 93%
SEO Desktop Score 82%
Progressive Web App Desktop Score 26%
Performance Mobile Score 35%
Best Practices Mobile Score 86%
SEO Mobile Score 83%
Progressive Web App Mobile Score 29%
Autoridade da Página Autoridade 1%
Autoridade do Domínio Autoridade do Domínio 39%
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 57 Carateres
HOMEPAGE | ESEL - ESCOLA SUPERIOR DE ENFERMAGEM DE LISBOA
Descrição Meta 0 Carateres
SEM DADOS
URL Efetivo 19 Carateres
https://www.esel.pt
Excerto Conteúdo da página
Homepage | ESEL - Escola Superior de Enfermagem de Lisboa Passar para o conteúdo principal ...
Núvem de Keywords Densidade
enfermagem37 apresentação36 acesso18 saúde16 candidatura14 mobilidade12 informações12 documentação12 apoio12 esel12
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
enfermagem 37
apresentação 36
acesso 18
saúde 16
candidatura 14
mobilidade 12
informações 12
documentação 12
apoio 12
esel 12
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
HOMEPAGE | ESEL - ESCOLA SUPERIOR DE ENFERMAGEM DE LISBOA
https://www.esel.pt
Homepage | ESEL - Escola Superior de Enfermagem de Lisboa Passar para o conteúdo principal ...
Robots.txt Ficheiro detetado
Sitemap.xml Ficheiro não encontrado
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~129.23 KB
Tamanho do Código: ~84.5 KB
Tamanho do Texto: ~44.73 KB Ratio: 34.61%

Redes Sociais

Delicious Total: 0
Facebook Total: 0
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
Minimizes main-thread work 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve images in next-gen formats Potential savings of 5,467 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
Largest Contentful Paint 6.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Keep request counts low and transfer sizes small 106 requests • 7,024 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Remove unused CSS Potential savings of 258 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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
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
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Properly size images Potential savings of 169 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid enormous network payloads Total size was 7,024 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Minify CSS Potential savings of 208 KiB
Minifying CSS files can reduce network payload sizes
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Eliminate render-blocking resources Potential savings of 2,460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 10.7 s
A fast page load over a cellular network ensures a good mobile user experience
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 65 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.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 210 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 5.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 2.5 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/).
Serve static assets with an efficient cache policy 97 resources found
A long cache lifetime can speed up repeat visits to your page
Remove unused JavaScript Potential savings of 41 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Time to Interactive 3.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid an excessive DOM size 1,977 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)

Móvel

Screenshot Móvel
Initial server response time was short Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minify CSS Potential savings of 208 KiB
Minifying CSS files can reduce network payload sizes
First Contentful Paint 8.1 s
First Contentful Paint marks the time at which the first text or image is painted
First Contentful Paint (3G) 16125 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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 1,974 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)
Total Blocking Time 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 96 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 8.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused CSS Potential savings of 259 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
Page load is not fast enough on mobile networks Interactive at 12.4 s
A fast page load over a cellular network ensures a good mobile user experience
Time to Interactive 12.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Tap targets are not sized appropriately 94% 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
Largest Contentful Paint 14.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 7,020 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid enormous network payloads Total size was 7,023 KiB
Large network payloads cost users real money and are highly correlated with long load times
Keep request counts low and transfer sizes small 105 requests • 7,023 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle 8.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/).
Remove unused JavaScript Potential savings of 41 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
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
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
Minimize main-thread work 2.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 8.1 s
First Meaningful Paint measures when the primary content of a page is visible
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
Avoid chaining critical requests 65 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
Serve images in next-gen formats Potential savings of 5,467 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
Properly size images Potential savings of 370 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Minimize third-party usage Third-party code blocked the main thread for 90 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

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: Sat, 02 Jan 2021 00:11:33 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-Powered-By: PHP/7.1.23
Cache-Control: must-revalidate, no-cache, private
X-Drupal-Dynamic-Cache: MISS
X-UA-Compatible: IE=edge
Content-language: pt-pt
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Expires: Sun, 19 Nov 1978 05:00:00 GMT
X-Generator: Drupal 8 (https://www.drupal.org)
X-Drupal-Cache: HIT
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