Geocompass.pt - SEO - Revisão do site

A Pontuação deste Site é

Com Ranking Similar

CASA DA BOA FONTE

casadaboafonte.com

IOL - Notícias, empresas e webmail

iol.pt

GEOCOMPASS

geocompass.pt

Sul Informação | O Sul mostra-se aqui

sulinformacao.pt

CTT

ctt.pt

Android Passo a Passo Tudo Sobre Sistema Android

androidpassoapasso.com.br

tnhnnmutzjmssq.html

Últimos Sites Analisados

SOLUÇÕES DE DETERGENTES PARA EMPRESAS EM PORTUGAL.

kimiplan.pt

IMOTOR - CARROS USADOS, AUTOMÓVEIS USADOS

imotor.pt

WISHIRT T-SHIRTS PERSONALIZADAS

wishirt.com

JORGE DANIEL MENDES FERREIRA

jorgedanielmendesferreira.com

ESCOLA DE CÃES

escoladecaes.com

GEOCOMPASS

geocompass.pt

hxsmnghm.html

Top das Tecnologias

jQuery

Javascript Frameworks

Google Font API

Font Scripts

Gzip

Compress

PHP

Programming Languages

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: 18 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

Partilhar esta Análise

Desktop

Móvel

Performance Desktop Score 83%

Best Practices Desktop Score 77%

SEO Desktop Score 90%

Progressive Web App Desktop Score 54%

Performance Mobile Score 54%

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

accessories19 more15 radios14 garmin14 know13 atex11 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	19
more	15
radios	14
garmin	14
know	13
atex	11
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

http://geocompass.pt/robots.txt

Sitemap.xml Ficheiro detetado

http://geocompass.pt/sitemap.xml

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 / 611 meses 20 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: ~80.07 KB

Tamanho do Código: ~29.97 KB

Tamanho do Texto: ~50.1 KB Ratio: 62.57%

Redes Sociais

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

Serve static assets with an efficient cache policy 35 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 70 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 1.7 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 49 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 223 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,560 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 430 ms

Time To First Byte identifies the time at which your server sends a response

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

Enable text compression Potential savings of 669 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 1,124 KB

Optimized images load faster and consume less cellular data

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 10 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

Defer offscreen images Potential savings of 47 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 1.5 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 1.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).

Avoid enormous network payloads Total size was 3,097 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 0.3 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.5 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

Avoid chaining critical requests 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 754 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 63 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 1.5 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 37 requests • 3,097 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Móvel

Total Blocking Time 130 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.5 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

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

Speed Index 4.8 s

Speed Index shows how quickly the contents of a page are visibly populated

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).

Avoid enormous network payloads Total size was 3,097 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.2 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 3.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

Avoid chaining critical requests 13 chains found

Avoids an excessive DOM size 758 elements

Minify JavaScript Potential savings of 63 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 3.8 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 37 requests • 3,097 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 35 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 190 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 7.7 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

First Contentful Paint (3G) 7968.5 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 49 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.65% 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 223 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,560 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 370 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,950 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 669 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 1,124 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 20 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: Sun, 29 Mar 2020 00:00:03 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=jha8143ve2m1dgpmas2lkjvjg2; 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

Tipo	Nome	Valor	Class	TTL
A	geocompass.pt	176.61.147.180	IN	299
NS	geocompass.pt	ns1.kriacao.pt	IN	21599
NS	geocompass.pt	ns2.kriacao.pt	IN	21599
MX	geocompass.pt	geocompass.pt	IN	299
TXT	geocompass.pt	v=spf1 ip4:176.61.147.180 +a +mx +ip4:195.8.59.90 ~all	IN	299

A Pontuação deste Site é

Com Ranking Similar

Últimos Sites Analisados

Top das Tecnologias

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

Desktop

Móvel

Redes Sociais

Tecnologias Aplicadas

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

PWA - Manifest

Desktop

Móvel

Dicas de Otimização e Velocidade

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

Ranking Alexa

99,999,999

99,999,999

Domínio Disponível

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

Informações do Servidor

Comentários

O que é SEO? (Search Engine Optimization)

Informação de Contato

Siga-nos