Your Website Score is

Similar Ranking

27
MODO DE MANUTENÇÃO
portaldepublicidade.pt
27
ALOE VERA SHOP | LOJA ONLINE
aloe-vera.me
27
HOTEL CARVALHO ARAUJO - HOTEL CARVALHO ARAUJO HOTEL CARVALHO ARAUJO - O SEU HOTEL NO GERÊS
hotelcarvalhoaraujo.com
27
REDUCE YOUR FOOTPRINT WHILE TRAVELING THE WORLD - NO FOOTPRINT NOMADS
nofootprintnomads.com
27
CONSULTOR DE MARKETING DIGITAL? MARCO GOUVEIA
marcogouveia.pt
27
CRIAR LOJA ONLINE. VENDA EM TODO LADO COM A WEASY | WEASY.IO
weasy.io
26
MYGZONE | TIENDA ONLINE VIDEO JUEGOS
mygzone.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

27 weasy.io Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 60%
Best Practices Desktop Score 71%
SEO Desktop Score 82%
Progressive Web App Desktop Score 26%
Performance Mobile Score 18%
Best Practices Mobile Score 71%
SEO Mobile Score 85%
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

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
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 Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle 2.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/).
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
Avoid enormous network payloads Total size was 3,172 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 45 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
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
Properly size images Potential savings of 543 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Time to Interactive 3.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Avoid an excessive DOM size 1,812 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 860 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 100 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
Serve static assets with an efficient cache policy 33 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.004
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 18.0 s
A fast page load over a cellular network ensures a good mobile user experience
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Defer offscreen images Potential savings of 691 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minify JavaScript Potential savings of 54 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Keep request counts low and transfer sizes small 136 requests • 3,172 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript Potential savings of 291 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 4.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
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
Remove unused CSS Potential savings of 141 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
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Initial server response time was short Root document took 280 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
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
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images Potential savings of 43 KiB
Optimized images load faster and consume less cellular data
Serve images in next-gen formats Potential savings of 1,302 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

Mobile

Mobile Screenshot
Tap targets are sized appropriately 100% 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.236
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce the impact of third-party code Third-party code blocked the main thread for 550 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
Avoid enormous network payloads Total size was 3,128 KiB
Large network payloads cost users real money and are highly correlated with long load times
First CPU Idle 11.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/).
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.
Minify JavaScript Potential savings of 54 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Contentful Paint 4.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 45 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 910 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay 320 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Document uses legible font sizes 98.78% 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
Page load is not fast enough on mobile networks Interactive at 17.5 s
A fast page load over a cellular network ensures a good mobile user experience
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Estimated Input Latency 110 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
Defer offscreen images Potential savings of 846 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Remove unused CSS Potential savings of 140 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
First Contentful Paint (3G) 8835 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Serve images in next-gen formats Potential savings of 1,302 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
Time to Interactive 17.5 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 3,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Keep request counts low and transfer sizes small 135 requests • 3,128 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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,813 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)
Speed Index 9.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify CSS Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
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 4.3 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 290 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 119 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Efficiently encode images Potential savings of 43 KiB
Optimized images load faster and consume less cellular data
Minimize main-thread work 5.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 19 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Largest Contentful Paint 18.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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 serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

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