A Pontuação deste Site é

Com Ranking Similar

2
CASA DA BOA FONTE
casadaboafonte.com
2
IOL - NOTÍCIAS, EMPRESAS E BLOGS.
iol.pt
2
GEOCOMPASS
geocompass.pt
2
Sul Informação | O Sul mostra-se aqui
sulinformacao.pt
2
CTT
ctt.pt
2
L-Queen Personalizados
lqueenpersonalizados.com.br

Ú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

Top das Tecnologias

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

2 geocompass.pt Última Análise: 9 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 83%
Best Practices Desktop Score 86%
SEO Desktop Score 73%
Progressive Web App Desktop Score 52%
Performance Mobile Score 53%
Best Practices Mobile Score 79%
SEO Mobile Score 75%
Progressive Web App Mobile Score 50%
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
accessories21 more16 radios14 know14 garmin14 atex11 communications9 equipments8 satellite7 iridium6
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 21
more 16
radios 14
know 14
garmin 14
atex 11
communications 9
equipments 8
satellite 7
iridium 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 / 51 anos
Criado em: 1970-01-01 / 51 anos
Expira em: 1970-01-01 / 620 meses 1 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: ~88 KB
Tamanho do Código: ~32.77 KB
Tamanho do Texto: ~55.23 KB Ratio: 62.76%

Redes Sociais

Delicious Total: 0
Facebook Total: 5,947
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
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
Eliminate render-blocking resources Potential savings of 430 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Initial server response time was short Root document took 380 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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/).
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
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
Keep request counts low and transfer sizes small 39 requests • 3,096 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve images in next-gen formats Potential savings of 1,539 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
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
Avoid enormous network payloads Total size was 3,096 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused CSS Potential savings of 223 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
Enable text compression Potential savings of 676 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoids an excessive DOM size 817 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)
Remove unused JavaScript Potential savings of 391 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minify CSS Potential savings of 49 KiB
Minifying CSS files can reduce network payload sizes
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 37 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 12 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
Efficiently encode images Potential savings of 1,087 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
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
Largest Contentful Paint 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Cumulative Layout Shift 1
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Minify JavaScript Potential savings of 63 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

Móvel

Screenshot Móvel
Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift 1
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 386 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time 150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Potential savings of 1,780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint (3G) 6720 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First CPU Idle 6.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/).
Minify CSS Potential savings of 49 KiB
Minifying CSS files can reduce network payload sizes
Time to Interactive 7.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests 12 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 10.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 3.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids an excessive DOM size 821 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)
Document uses legible font sizes 96.41% 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
Speed Index 4.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Minimize 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
Minify JavaScript Potential savings of 63 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Enable text compression Potential savings of 676 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Serve images in next-gen formats Potential savings of 1,539 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
Efficiently encode images Potential savings of 1,087 KiB
Optimized images load faster and consume less cellular data
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy 37 resources found
A long cache lifetime can speed up repeat visits to your page
Minimizes main-thread work 1.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
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
Keep request counts low and transfer sizes small 39 requests • 3,096 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
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
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
Avoid enormous network payloads Total size was 3,096 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused CSS Potential savings of 223 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
Initial server response time was short Root document took 410 ms
Keep the server response time for the main document short because all other requests depend on it

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, 05 Dec 2020 00:00:04 GMT
Server: Apache
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=prmjoeb4gf1bp8siir6ic4mf36; path=/
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