A Pontuação deste Site é

Com Ranking Similar

2
CASA DA BOA FONTE
casadaboafonte.com
2
IOL - Notícias, empresas e webmail
iol.pt
2
GEOCOMPASS
geocompass.pt
2
Sul Informação | O Sul mostra-se aqui
sulinformacao.pt
2
CTT
ctt.pt
2
Android Passo a Passo Tudo Sobre Sistema Android
androidpassoapasso.com.br
2
L-Queen Personalizados
lqueenpersonalizados.com.br

Últimos Sites Analisados

29
KIMIPLAN LDA
kimiplan.pt
33
WISHIRT T-SHIRTS PERSONALIZADAS
wishirt.com
37
IMOTOR - CARROS USADOS, AUTOMÓVEIS USADOS
imotor.pt
14
JORGE DANIEL MENDES FERREIRA
jorgedanielmendesferreira.com
19
ESCOLA DE CÃES
escoladecaes.com
2
GEOCOMPASS
geocompass.pt
3
ELECTRICISTA-PORTO-ELETRICISTAS-GAIA-FEIRA-AVEIRO-ESPINHO-MATOSINHOS-MAIA-VALONGO
24heletricistaaveiroporto.ml

Top das Tecnologias

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

2 geocompass.pt Última Análise: 3 horas

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 92%
Best Practices Desktop Score 77%
SEO Desktop Score 90%
Progressive Web App Desktop Score 54%
Performance Mobile Score 93%
Best Practices Mobile Score 77%
SEO Mobile Score 90%
Progressive Web App Mobile Score 52%
Autoridade da Página Autoridade 1%
Autoridade do Domínio Autoridade do Domínio 11%
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 10 Carateres
GEOCOMPASS
Descrição Meta 10 Carateres
GeoCompass
URL Efetivo 21 Carateres
https://geocompass.pt
Excerto Conteúdo da página
GEOCOMPASS ...
Núvem de Keywords Densidade
accessories18 radios15 garmin14 more12 know10 atex10 communications9 equipments8 satellite7 thuraya6
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
accessories 18
radios 15
garmin 14
more 12
know 10
atex 10
communications 9
equipments 8
satellite 7
thuraya 6
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
GEOCOMPASS
https://geocompass.pt
GeoCompass
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 / 50 anos
Criado em: 1970-01-01 / 50 anos
Expira em: 1970-01-01 / 606 meses 7 dias

Data Source - Web Solutions Lda
Admin Email: fccn@datasource.pt

Nameservers
rufus11.hocnet.pt
|
IPv4:
and
IPv6:
rufus12.hocnet.pt
|
IPv4:
and
IPv6:
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~74.73 KB
Tamanho do Código: ~27.76 KB
Tamanho do Texto: ~46.98 KB Ratio: 62.86%

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
Serve images in next-gen formats Potential savings of 1,365 KB
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
Server response times are low (TTFB) Root document took 450 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 994 KB
Optimized images load faster and consume less cellular data
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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
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 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input
Avoids enormous network payloads Total size was 2,123 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.4 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.6 s
First Contentful Paint marks the time at which the first 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
Minimize Critical Requests Depth 13 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
Avoids an excessive DOM size 708 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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 14 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 33 requests • 2,123 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 1 resource found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
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 9 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 25 KB
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

Móvel

Screenshot Móvel
Server response times are low (TTFB) Root document took 250 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 994 KB
Optimized images load faster and consume less cellular data
Third-Party Usage Third-party code blocked the main thread for 80 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 330 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 58 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input
Avoids enormous network payloads Total size was 2,123 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first 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
Minimize Critical Requests Depth 13 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
Avoids an excessive DOM size 712 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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 14 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.8 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 33 requests • 2,123 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 1 resource found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 230 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 4.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
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
First Contentful Paint (3G) 3420 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minify CSS Potential savings of 9 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 89% 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
Document uses legible font sizes 98.61% 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
Remove unused CSS Potential savings of 25 KB
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 images in next-gen formats Potential savings of 1,365 KB
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

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
Server: nginx
Date: Fri, 18 Oct 2019 00:00:03 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/5.4.45
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: kcHouseParty_site=8uqgj0maurjsdrs724i0n80uc6; path=/
X-UA-Compatible: IE=Edge,chrome=1
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Pragma: no-cache
Alternate-Protocol: 443:npn-spdy/2
Strict-Transport-Security: max-age=31536000; includeSubdomains
Content-Encoding: gzip
Registos DNS Registros de recursos DNS associados a um nome de host
Clique aqui para listar os Registos DNS

Comentários