A Pontuação deste Site é

Com Ranking Similar

18
NORSAFE
norsafe.pt
18
ROTA DE TAPAS - HOME
rotadetapas.com.pt
18
INÍCIO - CENTRO SOCIAL E PAROQUIAL S.PEDRO E S.JOAO DO ESTORIL
cspspsje.pt
18
TOMAZ DO DOURO - CRUZEIROS NO DOURO
tomazdodouro.pt
18
CAIS DO PICO
caisdopico.pt
18
TRANSFERS E PASSEIOS EM LONDRES COM MOTORISTAS BRASILEIROS.
te-travelbrasil.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
2
EMPRESA DE TRANSPORTES-INDISLOG TRANSPORTES LDA
indislog.com

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

18 tomazdodouro.pt Última Análise: 3 meses

Sucesso 62% passos de análise realizados
Aviso 23% total de avisos
Erros 15% de erros detetados. Estes erros exigem ação rápida

Desktop

Móvel

Performance Desktop Score 82%
Best Practices Desktop Score 79%
SEO Desktop Score 83%
Progressive Web App Desktop Score 41%
Performance Mobile Score 77%
Best Practices Mobile Score 71%
SEO Mobile Score 83%
Progressive Web App Mobile Score 43%
Autoridade da Página Autoridade 30%
Autoridade do Domínio Autoridade do Domínio 22%
Moz Rank 4.3/10
Taxas de Rejeição Taxa 0%
Charset Encoding
Excelente, a codificação de idioma / carateres é especificada: UTF-8
Tag Título 35 Carateres
TOMAZ DO DOURO - CRUZEIROS NO DOURO
Descrição Meta 34 Carateres
Cruzeiros no Douro - Douro Cruises
URL Efetivo 22 Carateres
http://tomazdodouro.pt
Excerto Conteúdo da página
 Tomaz do Douro - Cruzeiros no Douro        Carrinho de Compras ...
Núvem de Keywords Densidade
porto15 régua7 pocinho4 cruzeiros4 douro4 mais4 embarque4 cais4 almoço3 informações3
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
porto 15
régua 7
pocinho 4
cruzeiros 4
douro 4
mais 4
embarque 4
cais 4
almoço 3
informações 3
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
TOMAZ DO DOURO - CRUZEIROS NO DOURO
http://tomazdodouro.pt
Cruzeiros no Douro - Douro Cruises
Robots.txt Ficheiro detetado
Sitemap.xml Ficheiro detetado
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~24.83 KB
Tamanho do Código: ~22.59 KB
Tamanho do Texto: ~2.24 KB Ratio: 9.03%

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
Links do not have descriptive text 3 links found
Descriptive link text helps search engines understand your content
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
Avoid enormous network payloads Total size was 3,709 KiB
Large network payloads cost users real money and are highly correlated with long load times
Does not use HTTPS 11 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small 29 requests • 3,709 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minify CSS Potential savings of 8 KiB
Minifying CSS files can reduce network payload sizes
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 710 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
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
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
Enable text compression Potential savings of 261 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Remove unused JavaScript Potential savings of 49 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First CPU Idle 0.9 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.9 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive 0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Preload key requests Potential savings of 1,150 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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 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
Avoids an excessive DOM size 193 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)
Serve images in next-gen formats Potential savings of 1,982 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 2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Efficiently encode images Potential savings of 1,273 KiB
Optimized images load faster and consume less cellular data
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
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
Reduce initial server response time Root document took 1,090 ms
Keep the server response time for the main document short because all other requests depend on it
Remove unused CSS Potential savings of 199 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
Properly size images Potential savings of 211 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Defer offscreen images Potential savings of 2,413 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 0.03
Cumulative Layout Shift measures the movement of visible elements within the viewport

Móvel

Screenshot Móvel
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
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Reduce initial server response time Root document took 940 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 3.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids enormous network payloads Total size was 1,081 KiB
Large network payloads cost users real money and are highly correlated with long load times
Links do not have descriptive text 3 links found
Descriptive link text helps search engines understand your content
First Meaningful Paint 3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused CSS Potential savings of 201 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
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
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
Keep request counts low and transfer sizes small 22 requests • 1,081 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Properly size images Potential savings of 222 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint (3G) 6940.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Time to Interactive 4.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 16 resources found
A long cache lifetime can speed up repeat visits to your page
Defer offscreen images Potential savings of 68 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.323
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Potential savings of 2,780 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 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
Total Blocking Time 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First CPU Idle 3.4 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 3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Efficiently encode images Potential savings of 100 KiB
Optimized images load faster and consume less cellular data
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Document uses legible font sizes 97.95% 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
Serve images in next-gen formats Potential savings of 264 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
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Does not use HTTPS 11 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Minify CSS Potential savings of 8 KiB
Minifying CSS files can reduce network payload sizes
Minimize third-party usage Third-party code blocked the main thread for 10 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
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size 147 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)
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Tap targets are not sized appropriately 68% 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Remove unused JavaScript Potential savings of 70 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression Potential savings of 260 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Preload key requests Potential savings of 2,880 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

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, 01 Jan 2021 13:27:43 GMT
Server: Apache
X-Powered-By: PHP/7.2.34
Link: ; rel="https://api.w.org/"
Set-Cookie: _icl_current_language=pt-pt; expires=Sat, 02-Jan-2021 13:27:44 GMT; Max-Age=86400; 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