A Pontuação deste Site é

Com Ranking Similar

1
OLX - O Maior Site de Compra e Venda do Brasil
olx.com.br
1
TRAVELWINGS
travelwings.pt

Últimos Sites Analisados

56
CODISTEC
codistec.com
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
WordPress
CMS
Nginx
Web Servers
Google Analytics
Analytics
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks

1 travelwings.pt Última Análise: 2 semanas

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

Desktop

Móvel

Performance Desktop Score 16%
Best Practices Desktop Score 79%
SEO Desktop Score 91%
Progressive Web App Desktop Score 30%
Performance Mobile Score 1%
Best Practices Mobile Score 71%
SEO Mobile Score 99%
Progressive Web App Mobile Score 32%
Autoridade da Página Autoridade 32%
Autoridade do Domínio Autoridade do Domínio 22%
Moz Rank 4.6/10
Taxas de Rejeição Taxa 0%
Charset Encoding
Excelente, a codificação de idioma / carateres é especificada: UTF-8
Tag Título 11 Carateres
TRAVELWINGS
Descrição Meta 0 Carateres
SEM DADOS
URL Efetivo 26 Carateres
https://www.travelwings.pt
Excerto Conteúdo da página
Travelwings ...
Núvem de Keywords Densidade
$root65 localize56 generic42 webcontent40 footer29 name18 engines14 content14 client12 header11
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
$root 65
localize 56
generic 42
webcontent 40
footer 29
name 18
engines 14
content 14
client 12
header 11
Pré-visualização do Google O seu site aparece assim no resultado de pesquisa do Google
TRAVELWINGS
https://www.travelwings.pt
Travelwings ...
Robots.txt Ficheiro detetado
Sitemap.xml Ficheiro detetado
Tamanho da Página Código & Ratio do Texto
Tamanho do Documento: ~49.49 KB
Tamanho do Código: ~32.02 KB
Tamanho do Texto: ~17.47 KB Ratio: 35.30%

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 static assets with an efficient cache policy 129 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 5.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Max Potential First Input Delay 720 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
First CPU Idle 4.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/).
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 23.0 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid chaining critical requests 56 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
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Total Blocking Time 1,650 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift 1.124
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 5.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 2.1 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Enable text compression Potential savings of 331 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Estimated Input Latency 350 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
Reduce JavaScript execution time 2.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 3,391 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
Remove unused CSS Potential savings of 107 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
Defer offscreen images Potential savings of 1,781 KiB
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
Remove unused JavaScript Potential savings of 321 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Efficiently encode images Potential savings of 2,145 KiB
Optimized images load faster and consume less cellular data
Eliminate render-blocking resources Potential savings of 1,760 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid enormous network payloads Total size was 7,380 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated
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 179 requests • 7,380 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid an excessive DOM size 2,065 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)
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint 2.1 s
First Contentful Paint marks the time at which the first 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

Móvel

Screenshot Móvel
First Contentful Paint (3G) 23610 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Contentful Paint 8.6 s
First Contentful Paint marks the time at which the first text or image is painted
Document uses legible font sizes 75.27% 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
Reduce JavaScript execution time 10.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 1.506
Cumulative Layout Shift measures the movement of visible elements within the viewport
Max Potential First Input Delay 3,180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Time to Interactive 24.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Potential savings of 7,550 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 27.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid chaining critical requests 56 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 12.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimize main-thread work 15.5 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 2,832 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Enable text compression Potential savings of 331 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 2,145 KiB
Optimized images load faster and consume less cellular data
First CPU Idle 12.2 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/).
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
Remove unused CSS Potential savings of 107 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
Tap targets are not sized appropriately 91% 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
Initial server response time was short Root document took 80 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid enormous network payloads Total size was 7,372 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Meaningful Paint 12.2 s
First Meaningful Paint measures when the primary content of a page is visible
Estimated Input Latency 2,280 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
Keep request counts low and transfer sizes small 177 requests • 7,372 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Remove unused JavaScript Potential savings of 324 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time 7,650 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Page load is not fast enough on mobile networks Interactive at 24.4 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce the impact of third-party code Third-party code blocked the main thread for 260 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
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
Avoid an excessive DOM size 1,868 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 static assets with an efficient cache policy 127 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Potential savings of 3,391 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
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.

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/2 200 
date: Fri, 01 Jan 2021 01:12:53 GMT
server: Apache
x-powered-by: PHP/7.3.23
vary: User-Agent
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