Review
Your Website Score is
Update
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
27
RELÓGIOS, JOIAS E ÓCULOS. LUXO AOS MELHORES PREÇOS NA ZAGARI
zagari.pt
Latest Sites
12
BRIGHTON EAGLE CHAUFFEUR & TAXI - CHAUFFEUR DRIVEN EXECUTIVE CAR HIRE
brightoneaglechauffeur.com
56
U.PORTO - UNIVERSIDADE DO PORTO
sigarra.up.pt
19
DIRECT ENGLISH | O PROGRAMA DE INGLÊS MAIS EFICAZ DO MUNDO
directenglish.pt
24
THE REIGATE MARBLE SHOP | GRANITE WORKTOPS & MARBLE WORKTOPS IN SURREY AND ALL AROUND SUS---
marble-shop.co.uk
19
BLIMEY SOLUTIONS LTD - CIS ACCOUNTING & RECRUITMENT SERVICES IN LONDON
blimeysolutions.com
19
TROPOJA CONSTRUCTION LTD | TRUSTED CONSTRUCTION COMPANY IN LONDON
tropojaconstructionltd.co.uk
31
ELSONY WASTE REMOVAL | AFFORDABLE WASTE & RUBBISH COLLECTION & REMOVAL IN N11, N12 & SURROUNDING AREAS
elsonywaste.co.uk
Top Technologies
PHP
Programming Languages
Google Font API
Font Scripts
WordPress
CMS
Apache
Web Servers
Font Awesome
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
Yoast SEO
SEO
WooCommerce
Ecommerce
Google Tag Manager
Tag Managers
27
marcogouveia.pt
Last Updated: 3 years
Success
78% of passed verification steps
Warning
7% of total warning
Errors
15% of total errors, require fast action
Share
Download PDF
Desktop
Mobile
Performance
Desktop Score 79%
Best Practices
Desktop Score 69%
SEO
Desktop Score 100%
Progressive Web App
Desktop Score 31%
Performance
Mobile Score 26%
Best Practices
Mobile Score 69%
SEO
Mobile Score 100%
Progressive Web App
Mobile Score 33%
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
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
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 12.0 s
A fast page load over a cellular network ensures a good mobile user experience
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
Remove unused CSS
Potential savings of 155 KB
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
Serve images in next-gen formats
Potential savings of 25 KB
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
Server response times are low (TTFB)
Root document took 180 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources
Potential savings of 440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images
Potential savings of 11 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage
Third-party code blocked the main thread for 80 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
Total Blocking Time
200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time
1.0 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
Defer offscreen images
Potential savings of 2 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images
Potential savings of 15 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index
2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle
2.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).
Avoids enormous network payloads
Total size was 1,349 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities
3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests
12 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
777 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)
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
84 requests • 1,349 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy
8 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive
2.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Mobile
First Meaningful Paint
3.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
82 requests • 1,320 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy
8 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
920 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive
13.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks
Interactive at 13.1 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency
410 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)
7197 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
Document uses legible font sizes
96.02% 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
Remove unused CSS
Potential savings of 153 KB
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
Serve images in next-gen formats
Potential savings of 25 KB
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
Server response times are low (TTFB)
Root document took 190 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources
Potential savings of 1,820 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images
Potential savings of 11 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,680 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
Total Blocking Time
3,290 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time
7.2 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
Properly size images
Potential savings of 6 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index
9.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle
12.8 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).
Avoids enormous network payloads
Total size was 1,320 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work
13.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities
3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests
12 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
777 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 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
Domain (TDL) and Typo
Status
marcogouveia.co
Available
Buy Now!
marcogouveia.us
Available
Buy Now!
marcogouveia.com
Already Registered
marcogouveia.org
Already Registered
marcogouveia.net
Already Registered
mrcogouveia.pt
Available
Buy Now!
jarcogouveia.pt
Available
Buy Now!
iarcogouveia.pt
Available
Buy Now!
Information Server
Only Registered Users
Sign up for see all features and reviews about this site
Login
Login/Register
Shortcuts
Shortcut traffic
Shortcut tips
Shortcut alexa
Shortcut server
Shortcut meta
Shortcut authority
Shortcut technologies
Shortcut pagespeed
Shortcut pagespeed_stats
Shortcut social
Shortcut domain_available
Pages
Politica de Privacidade
Contact
Latest Updated Sites
Top Sites
Languages
English
Espanhol
French
Português
...
Please wait
Starting process...