A Pontuação deste Site é

Com Ranking Similar

68
OBSERVADOR – NOTÍCIAS, OPINIÃO, ESPECIAIS, EXPLICADORES E NEWSLETTERS
observador.pt
68
EXAME INFORMÁTICA
exameinformatica.sapo.pt
68
VODAFONE PORTUGAL - TELEMÓVEIS, INTERNET, TELEVISÃO
vodafone.pt
68
【ビタブリッドCフェイス(Vitabrid C)の口コミ】悪評&良い評判は本当?購入して徹底調査してみた
lojatextil.com
68
Samsys - Soluções que ajudam a crescer
samsys.pt
68
Gerenciando Blog - Blogs, SEO e Monetização
gerenciandoblog.com.br
68
OSPRECOS.PT
osprecos.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

68 vodafone.pt Última Análise: 3 semanas

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

Desktop

Móvel

Performance Desktop Score 56%
Best Practices Desktop Score 57%
SEO Desktop Score 100%
Progressive Web App Desktop Score 33%
Performance Mobile Score 15%
Best Practices Mobile Score 57%
SEO Mobile Score 99%
Progressive Web App Mobile Score 36%
Autoridade da Página Autoridade 47%
Autoridade do Domínio Autoridade do Domínio 54%
Moz Rank 4.4/10
Taxas de Rejeição Taxa 0%
Tag Título 51 Carateres
VODAFONE PORTUGAL - TELEMÓVEIS, INTERNET, TELEVISÃO
Descrição Meta 120 Carateres
O seu operador de comunicações – loja online com os últimos telemóveis e Smartphones, pacotes de TV+Net+Voz, banda larga
URL Efetivo 23 Carateres
https://www.vodafone.pt
Excerto Conteúdo da página
Vodafone Portugal - Telemóveis, Internet, Televisão Please click here if you are not redirected within a few seconds. Skip to content Particular Business A Vodafone Estado da Rede ...
Núvem de Keywords Densidade
stroke81 round52 false45 delete45 login38 currencynumber30 offerslot30 ischild30 previouspricerelation30 minimumfractiondigits27
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
stroke 81
round 52
false 45
delete 45
login 38
currencynumber 30
offerslot 30
ischild 30
previouspricerelatio... 30
minimumfractiondigit... 27
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
VODAFONE PORTUGAL - TELEMÓVEIS, INTERNET, TELEVISÃO
https://www.vodafone.pt
O seu operador de comunicações – loja online com os últimos telemóveis e Smartphones, pacotes de TV+Net+Voz, banda larga
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: 1970-01-01 / 51 anos
Expira em: 1970-01-01 / 621 meses 18 dias

CSC Corporate Domains Inc.
Admin Email: admin@internationaladmin.com,cctld-billing@cscinfo.com,dns-admin@cscglobal.com

Nameservers
ns-b2.vodafone.pt
|
IPv4:
87.103.113.185
and
IPv6:
ns-b1.vodafone.pt
|
IPv4:
87.103.113.184
and
IPv6:
ns-a2.vodafone.pt
|
IPv4:
87.103.113.153
and
IPv6:
ns-a1.vodafone.pt
|
IPv4:
87.103.113.152
and
IPv6:
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~293.97 KB
Tamanho do Código: ~254.63 KB
Tamanho do Texto: ~39.34 KB Ratio: 13.38%

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
Keep request counts low and transfer sizes small 183 requests • 2,358 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint 3.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Remove unused JavaScript Potential savings of 627 KiB
Remove unused JavaScript to reduce 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
Eliminate render-blocking resources Potential savings of 180 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 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused CSS Potential savings of 152 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
Time to Interactive 3.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 290 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Properly size images Potential savings of 40 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids enormous network payloads Total size was 2,358 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Cumulative Layout Shift 0.416
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid an excessive DOM size 3,535 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)
Minify JavaScript Potential savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Preload key requests Potential savings of 1,110 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Total Blocking Time 340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize main-thread work 3.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.0 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/).
Initial server response time was short Root document took 330 ms
Keep the server response time for the main document short because all other requests depend on it
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
Reduce JavaScript execution time 1.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.8 s
First Contentful Paint marks the time at which the first text or image is painted
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 211 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 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 20.9 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid serving legacy JavaScript to modern browsers Potential savings of 52 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
Serve static assets with an efficient cache policy 95 resources found
A long cache lifetime can speed up repeat visits to your page

Móvel

Screenshot Móvel
Preload key requests Potential savings of 6,600 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Max Potential First Input Delay 1,260 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index 8.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 3.3 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 1,160 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Estimated Input Latency 620 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 151 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
Serve static assets with an efficient cache policy 95 resources found
A long cache lifetime can speed up repeat visits to your 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
Time to Interactive 21.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Defer offscreen images Potential savings of 92 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve images in next-gen formats Potential savings of 187 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
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 serving legacy JavaScript to modern browsers Potential savings of 52 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
First CPU Idle 18.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/).
Tap targets are not sized appropriately 93% 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 JavaScript execution time 8.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
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
Initial server response time was short Root document took 290 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 2,287 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 13.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Minify JavaScript Potential savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint 12.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 3,577 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)
Reduce the impact of third-party code Third-party code blocked the main thread for 290 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.507
Cumulative Layout Shift measures the movement of visible elements within the viewport
Page load is not fast enough on mobile networks Interactive at 21.6 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 6624 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
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 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
Keep request counts low and transfer sizes small 201 requests • 2,287 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 3,650 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 607 KiB
Remove unused JavaScript to reduce bytes consumed by network activity

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:14:15 GMT
server: vodafone.pt
set-cookie: ObSSOCookie=1OTr5quThaGR0eo1LrpK63j5w314KEBlZ%2F86gWF6oq8AOd7vMZ0%2FApcwzeCn9J8XvDMHzcJa2MKuUZcCW7fW9lRMu613eO44NKGMEmGjjxIY5ppR73phly1KK5DjEjAcGyer2uTIb0LRatMNkz63ucdlJgTdN287z27uKNNvTQVcy%2B36f2RB%2BYwrq50A1Jf14K8uPzJi6zYZqhlnaag1lygThJD%2FPqJ76s0GeZ6z55EKaqBHkbDY30fbgmraKAyyOoMIjzNo2eARIGu3zxnBo1vJOHOiq8rfwxl1GM3kgtVxJUHq0VRpMv8FCv0gwsKT; httponly; path=/; domain=.vodafone.pt
cache-control: public
pragma: public
accept-ranges: bytes
x-mod-pagespeed: 1.13.35.2-0
x-frame-options: SAMEORIGIN
referrer-policy: no-referrer
x-permitted-cross-domain-policies: none
x-xss-protection: 1;mode=block
x-content-type-options: nosniff
vary: Accept-Encoding
content-encoding: gzip
cache-control: max-age=0, no-cache
content-length: 43161
content-type: text/html; charset=UTF-8
strict-transport-security: max-age=157680000
set-cookie: NSC_mc_xxx.htmc.wpebgpof.qu=ffffffff50a6112b45525d5f4f58455e445a4a420000;expires=Thu, 31-Dec-2020 12:14:15 GMT;path=/;domain=www.vodafone.pt;secure;httponly
set-cookie: visid_incap_2439306=+A4g2niIR1uncHiFi1kv0+Yl7V8AAAAAQUIPAAAAAAC/Miv7Wt0ifbylqQnv+5k4; expires=Thu, 30 Dec 2021 09:00:22 GMT; HttpOnly; path=/; Domain=.vodafone.pt; Secure; SameSite=None
set-cookie: nlbi_2439306=NfioaxvahF/jQbZAlm+sCAAAAAD4ARyglBRgeU/7E5g2f9rW; path=/; Domain=.vodafone.pt; Secure; SameSite=None
set-cookie: incap_ses_505_2439306=5fGUSRWUAiT1rkVKGx8CB+cl7V8AAAAAB+1lcExE2jpVmikFHIZzQA==; path=/; Domain=.vodafone.pt; Secure; SameSite=None
x-cdn: Incapsula
x-iinfo: 5-167589966-167588316 PNNy RT(1609377255606 0) q(0 0 0 0) r(2 2) U5
Registos DNS Registros de recursos DNS associados a um nome de host
Clique aqui para listar os Registos DNS

Comentários