A Pontuação deste Site é

Com Ranking Similar

71
TUA SAÚDE - TUA SAÚDE
tuasaude.com
71
VAMOS FICAR LIGADOS - NOS
nos.pt
71
Eletricidade - Electrónica - Esquemas - Eletronica PT
electronica-pt.com
71
zerozero.pt :: Porque todos os jogos começam assim...
zerozero.pt
71
Câmara Municipal de Viana do Castelo
cm-viana-castelo.pt
71
Loja do Vigour - Prazer4u
vigour.name
71
Chaminés - Limpeza |Desobstrução | Técnico©
limpeza-chamines.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
23
CLUBE NAVAL DA HORTA
cnhorta.org

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

71 nos.pt Última Análise: 3 semanas

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

Desktop

Móvel

Performance Desktop Score 76%
Best Practices Desktop Score 64%
SEO Desktop Score 67%
Progressive Web App Desktop Score 30%
Performance Mobile Score 18%
Best Practices Mobile Score 57%
SEO Mobile Score 70%
Progressive Web App Mobile Score 32%
Autoridade da Página Autoridade 50%
Autoridade do Domínio Autoridade do Domínio 63%
Moz Rank 5.9/10
Taxas de Rejeição Taxa 0%
Tag Título 38 Carateres
VAMOS FICAR LIGADOS - NOS
Descrição Meta 122 Carateres
Liga-te à nova rede móvel da NOS, pronta para o 5G, à melhor experiência de TV e ao melhor da tecnologia e entretenimento.
URL Efetivo 18 Carateres
https://www.nos.pt
Excerto Conteúdo da página
Vamos ficar ligados - NOS ...
Núvem de Keywords Densidade
serviços15 mais15 todos14 para14 pacotes14 internet13 telemóvel12 telefone12 equipamentos10 ajuda10
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
serviços 15
mais 15
todos 14
para 14
pacotes 14
internet 13
telemóvel 12
telefone 12
equipamentos 10
ajuda 10
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
VAMOS FICAR LIGADOS - NOS
https://www.nos.pt
Liga-te à nova rede móvel da NOS, pronta para o 5G, à melhor experiência de TV e ao melhor da tecnologia e entretenimento.
Robots.txt Ficheiro detetado
Sitemap.xml Ficheiro detetado
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: 2009-12-03 / 11 anos
Expira em: 2020-01-07 / 12 meses 19 dias

NOS, SGPS, S.A.
Admin Email: dns-admin@nos.pt;

Nameservers
ns2.novis.pt
|
IPv4:
and
IPv6:
ns1.novis.pt
|
IPv4:
and
IPv6:
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~437.21 KB
Tamanho do Código: ~398.72 KB
Tamanho do Texto: ~38.49 KB Ratio: 8.80%

Redes Sociais

Delicious Total: 0
Facebook Total: 25,352
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
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 151 requests • 3,555 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle 1.9 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/).
Eliminate render-blocking resources Potential savings of 400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.064
Cumulative Layout Shift measures the movement of visible elements within the viewport
Enable text compression Potential savings of 2 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
Max Potential First Input Delay 240 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 11.2 s
A fast page load over a cellular network ensures a good mobile user experience
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid serving legacy JavaScript to modern browsers Potential savings of 29 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 chaining critical requests 31 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
Initial server response time was short Root document took 200 ms
Keep the server response time for the main document short because all other requests depend on it
Serve images in next-gen formats Potential savings of 1,903 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
robots.txt is not valid 3 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 39 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid an excessive DOM size 2,530 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
Preload key requests Potential savings of 900 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 11 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Remove unused JavaScript Potential savings of 227 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Remove unused CSS Potential savings of 88 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 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
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 2.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Properly size images Potential savings of 1,322 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Efficiently encode images Potential savings of 39 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid enormous network payloads Total size was 3,555 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
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

Móvel

Screenshot Móvel
Page load is not fast enough on mobile networks Interactive at 11.6 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce the impact of third-party code Third-party code blocked the main thread for 750 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
Time to Interactive 11.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve images in next-gen formats Potential savings of 1,903 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
Minify JavaScript Potential savings of 11 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Contentful Paint (3G) 7927 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Speed Index 6.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time 3.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests 31 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
Properly size images Potential savings of 434 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Preload key requests Potential savings of 3,720 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
Efficiently encode images Potential savings of 39 KiB
Optimized images load faster and consume less cellular data
Avoid serving legacy JavaScript to modern browsers Potential savings of 29 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
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Defer offscreen images Potential savings of 183 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Contentful Paint 3.7 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle 9.7 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/).
Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability 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.
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Remove unused CSS Potential savings of 89 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
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 an excessive DOM size 2,508 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 149 requests • 3,576 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 1,860 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Eliminate render-blocking resources Potential savings of 1,930 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
robots.txt is not valid 3 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Tap targets are not sized appropriately 91% 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
Enable text compression Potential savings of 2 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Estimated Input Latency 390 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
Avoid enormous network payloads Total size was 3,576 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 980 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Meaningful Paint 5.5 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy 37 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.431
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work 7.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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 JavaScript Potential savings of 228 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Document uses legible font sizes 83.29% 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
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 11.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted

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/2 200 
date: Thu, 31 Dec 2020 01:41:45 GMT
content-type: text/html; charset=utf-8
content-length: 65462
cache-control: private, max-age=0
content-encoding: gzip
expires: Tue, 15 Dec 2020 23:01:24 GMT
last-modified: Wed, 30 Dec 2020 23:01:24 GMT
vary: Accept-Encoding
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
x-ms-invokeapp: 1; RequireReadOnly
access-control-allow-origin: *
access-control-allow-methods: GET
access-control-allow-headers: Content-Type
x-frame-options: SAMEORIGIN
server: Microsoft-IIS
x-varnish: 58118183 45861505
age: 9620
via: 1.1 varnish (Varnish/5.2)
accept-ranges: bytes
Registos DNS Registros de recursos DNS associados a um nome de host
Clique aqui para listar os Registos DNS

Comentários