A Pontuação deste Site é

Com Ranking Similar

2
IOL - NOTÍCIAS, EMPRESAS E BLOGS.
iol.pt
2
GEOCOMPASS
geocompass.pt
2
EMPRESA DE TRANSPORTES-INDISLOG TRANSPORTES LDA
indislog.com
2
L-Queen Personalizados
lqueenpersonalizados.com.br
2
WINSIG | SOLUçõES DE GESTãO INTEGRADA
winsig.pt
2
HOMEPAGE - IDEALBIZ
idealbiz.pt
2
ALFALOC - ENVÍO INTERNACIONAL EXPRESO
alfaloc.eus

Ú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
29
UNIVERSO DO CONHECIMENTO - EVOLUÇÃO PESSOAL E ESPIRITUAL
universodoconhecimento.com

Top das Tecnologias

jQuery
Javascript Frameworks
Google Font API
Font Scripts
PHP
Programming Languages
Gzip
Compress
Apache
Web Servers
WordPress
CMS
Nginx
Web Servers
Google Analytics
Analytics
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks

2 geocompass.pt Última Análise: 7 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 72%
Best Practices Desktop Score 87%
SEO Desktop Score 73%
Progressive Web App Desktop Score 36%
Performance Mobile Score 52%
Best Practices Mobile Score 80%
SEO Mobile Score 75%
Progressive Web App Mobile Score 33%
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
accessories20 atex18 more18 know16 radios14 gpsmap11 garmin10 communications9 zone9 equipments8
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 20
atex 18
more 18
know 16
radios 14
gpsmap 11
garmin 10
communications 9
zone 9
equipments 8
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 / 51 anos
Criado em: 1970-01-01 / 51 anos
Expira em: 1970-01-01 / 623 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: ~97.53 KB
Tamanho do Código: ~35.81 KB
Tamanho do Texto: ~61.72 KB Ratio: 63.28%

Redes Sociais

Delicious Total: 0
Facebook Total: 5,961
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
Remove unused JavaScript Potential savings of 391 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
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
Initial server response time was short Root document took 490 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
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Enable text compression Potential savings of 685 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
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
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
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/).
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Minify JavaScript Potential savings of 63 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minify CSS Potential savings of 49 KiB
Minifying CSS files can reduce network payload sizes
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid an excessive DOM size 893 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)
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
Cumulative Layout Shift 1
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Potential savings of 480 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 4,011 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
Largest Contentful Paint 3.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Keep request counts low and transfer sizes small 42 requests • 5,991 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid enormous network payloads Total size was 5,991 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Use HTTP/2 40 requests not served via HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing
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
Efficiently encode images Potential savings of 3,174 KiB
Optimized images load faster and consume less cellular data

Móvel

Screenshot Móvel
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
First Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
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
Document uses legible font sizes 96.46% 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 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
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Estimated Input Latency 20 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
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 4.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images Potential savings of 3,174 KiB
Optimized images load faster and consume less cellular data
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize third-party usage Third-party code blocked the main thread for 50 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
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
Minify JavaScript Potential savings of 63 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint 8.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid enormous network payloads Total size was 5,991 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 1.07
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
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
Time to Interactive 7.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small 42 requests • 5,991 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle 7.6 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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Enable text compression Potential savings of 685 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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
First Contentful Paint (3G) 7020 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Eliminate render-blocking resources Potential savings of 1,790 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 3.3 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused JavaScript Potential savings of 386 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Serve images in next-gen formats Potential savings of 4,011 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 an excessive DOM size 897 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)
Use HTTP/2 40 requests not served via HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minify CSS Potential savings of 49 KiB
Minifying CSS files can reduce network payload sizes
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
Initial server response time was short Root document took 520 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 210 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

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: Fri, 05 Mar 2021 00:00:02 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=tsoha3chmk6tc5tffkiehuss70; 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 297
NS geocompass.pt ns2.kriacao.pt IN 86400
NS geocompass.pt ns1.kriacao.pt IN 86400
MX geocompass.pt geocompass.pt IN 300
TXT geocompass.pt v=spf1 ip4:176.61.147.180 +a +mx +ip4:195.8.59.90 ~all IN 300

Comentários

O que é SEO? (Search Engine Optimization)

SEO é o conjunto de estratégias com o objetivo de potencializar e melhorar o posicionamento de um site nas páginas de resultados naturais (orgânicos) nos sites de busca.

Informação de Contato

info@rankpt.com

Siga-nos

Copyright 2017 / 2021 - paulonobrega.com
Idioma | English