Your Website Score is

Similar Ranking

41
INÍCIO - PRODUTOS DE OCASIÃO
produtosocasiao.pt
41
WEBTUGA - ALOJAMENTO WEB - ALOJAMENTO DE WEBSITES PARA CRIAR SITE OU LOJA ONLINE
webtuga.pt
41
O SEU DOMÍNIO – NOVO SITE PARA O SEU DOMÍNIO!
oseudominio.pt
41
BYDAS, DIGITAL COMMUNICATION AGENCY / SHOPIFY PARTNER AND EXPERTS
bydas.com
39
GB - WHATSAPP GB, PRO, PLUS, AERO, FM, WEBWHATS
biva.digital
38
ERN - REMODELAÇÃO IMÓVEIS ESPAÇOS COMERCIAIS
ern.com.pt
35
MARISA PASSOS - GRAPHIC DESIGNER | FREELANCER | PORTFOLIO
marisapassos.com

Latest Sites

31
ORTHOPETCARE
orthopetcare.pt
19
MYIEVOLUTION - TERAPIA ONLINE - TERAPIA ONLINE %
myievolution.com
35
TECHENET - NOTÍCIAS E INFORMAÇÃO DE TECNOLOGIA
techenet.com
19
RAG TAILORS - FARDAS E UNIFORMES À IMAGEM DO SEU NEGÓCIO
ragtailors.com
14
11
KID TO KID ONLINE
kidtokidonline.pt

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
Apache
Web Servers
Font Awesome
Font Scripts
Nginx
Web Servers
Yoast SEO
SEO
WooCommerce
Ecommerce
Google Tag Manager
Tag Managers

41 webtuga.pt Last Updated: 8 months

Success 62% of passed verification steps
Warning 23% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 43%
Best Practices Desktop Score 77%
SEO Desktop Score 91%
Progressive Web App Desktop Score 26%
Performance Mobile Score 14%
Best Practices Mobile Score 77%
SEO Mobile Score 88%
Progressive Web App Mobile Score 29%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Only Registered Users

Sign up for see all features and reviews about this site

Login

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

WebTuga WebTuga

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
WebTuga
Param short_name
WebTuga
Param start_url
/
Param display
standalone
Param gcm_sender_id
482941778795
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest

Desktop

Desktop Screenshot
Avoid chaining critical requests 51 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
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid an excessive DOM size 926 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)
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 17.5 s
A fast page load over a cellular network ensures a good mobile user experience
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 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 4.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 510 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Preload key requests Potential savings of 840 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
First CPU Idle 3.1 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 long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoids enormous network payloads Total size was 2,172 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Potential savings of 13 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve images in next-gen formats Potential savings of 576 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
Serve static assets with an efficient cache policy 11 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work 4.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 460 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
Speed Index 3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 2.6 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time 410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Estimated Input Latency 40 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
Cumulative Layout Shift 0.109
Cumulative Layout Shift measures the movement of visible elements within the viewport
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Reduce JavaScript execution time 3.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused JavaScript Potential savings of 345 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused CSS Potential savings of 98 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
Minify JavaScript Potential savings of 9 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Keep request counts low and transfer sizes small 86 requests • 2,172 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
First Meaningful Paint 6.9 s
First Meaningful Paint measures when the primary content of a page is visible
Speed Index 9.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 19 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
Total Blocking Time 1,700 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Document uses legible font sizes 94.81% 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
Initial server response time was short Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint 4.4 s
First Contentful Paint marks the time at which the first text or image is painted
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint (3G) 9450 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Page load is not fast enough on mobile networks Interactive at 14.5 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce JavaScript execution time 3.4 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
Minimize main-thread work 7.1 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 51 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
Serve static assets with an efficient cache policy 9 resources found
A long cache lifetime can speed up repeat visits to your page
Minify JavaScript Potential savings of 9 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Remove unused CSS Potential savings of 99 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
Estimated Input Latency 230 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
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
Keep request counts low and transfer sizes small 78 requests • 1,365 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
Tap targets are not sized appropriately 43% 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
Cumulative Layout Shift 0.212
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids an excessive DOM size 816 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)
Eliminate render-blocking resources Potential savings of 2,250 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 8.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First CPU Idle 11.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/).
Reduce the impact of third-party code Third-party code blocked the main thread for 1,220 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
Max Potential First Input Delay 770 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads Total size was 1,365 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Time to Interactive 14.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused JavaScript Potential savings of 380 KiB
Remove unused JavaScript to reduce bytes consumed by network activity

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login