Your Website Score is

Similar Ranking

19
BE LAGOOM - DE MUJERES PARA MUJERES - MODA ONLINE
belagoom.com
19
AGALPORTOTEC,LDA
agalportotec.com
19
JOSÉ M. SILVA
josemsilva.pt
19
CÁTIA GUEDES - WEB DESIGN E MARKETING DIGITAL
catiaguedes.com
19
GRISP RESEARCH SOLUTIONS
grisp.pt
19
JOTI MENUISERIE ALU
joti.fr
19
TAXI4YOU MADEIRA
taxi4youmadeira.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

19 greenoeste.pt Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 64%
Best Practices Desktop Score 86%
SEO Desktop Score 100%
Progressive Web App Desktop Score 30%
Performance Mobile Score 33%
Best Practices Mobile Score 93%
SEO Mobile Score 100%
Progressive Web App Mobile Score 32%
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
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First Meaningful Paint 1.6 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 390 KiB
Remove unused JavaScript to reduce 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
Largest Contentful Paint 3.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids enormous network payloads Total size was 2,531 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources Potential savings of 1,460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify JavaScript Potential savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Minify CSS Potential savings of 60 KiB
Minifying CSS files can reduce network payload sizes
Efficiently encode images Potential savings of 294 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.
Keep request counts low and transfer sizes small 78 requests • 2,531 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Properly size images Potential savings of 424 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Total Blocking Time 0 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 on simulated mobile network at 13.1 s
A fast page load over a cellular network ensures a good mobile user experience
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
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 58 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 406 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)
Time to Interactive 1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Enable text compression Potential savings of 734 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 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
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
Avoid chaining critical requests 36 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
Reduce initial server response time Root document took 1,050 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 0.263
Cumulative Layout Shift measures the movement of visible elements within the viewport
First CPU Idle 1.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/).
Serve images in next-gen formats Potential savings of 615 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 335 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

Mobile

Mobile Screenshot
Avoid chaining critical requests 36 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 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
Largest Contentful Paint 9.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minify CSS Potential savings of 60 KiB
Minifying CSS files can reduce network payload sizes
Remove unused JavaScript Potential savings of 390 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids an excessive DOM size 406 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 51 resources found
A long cache lifetime can speed up repeat visits to your page
Page load is not fast enough on mobile networks Interactive at 12.6 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce initial server response time Root document took 1,640 ms
Keep the server response time for the main document short because all other requests depend on it
Remove unused CSS Potential savings of 343 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 5 elements found
These DOM elements contribute most to the CLS of the page.
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Total Blocking Time 330 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids enormous network payloads Total size was 2,199 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Potential savings of 92 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Enable text compression Potential savings of 734 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Eliminate render-blocking resources Potential savings of 5,490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First CPU Idle 10.5 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/).
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Serve images in next-gen formats Potential savings of 470 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
Minify JavaScript Potential savings of 4 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Estimated Input Latency 30 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 Contentful Paint (3G) 14147 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Efficiently encode images Potential savings of 294 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 12.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 6.2 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
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
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce JavaScript execution time 1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 6.4 s
First Meaningful Paint measures when the primary content of a page is visible
Document uses legible font sizes 100% 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
Keep request counts low and transfer sizes small 71 requests • 2,199 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minimize third-party usage Third-party code blocked the main thread for 150 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
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
Speed Index 9.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimize main-thread work 2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 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
Defer offscreen images Potential savings of 160 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

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