Review
Your Website Score is
Update
Similar Ranking
14
VISTOREPRO – A SUA LOJA ONLINE
vistorepro.com
14
GRANDE CAMPO – LOJA ONLINE – COMPRAR FLORES ONLINE
grandecampo.pt
14
EXCLUSIVE VILLA CASCAIS – THE BEST HOUSES TO SELL OR BUY IN CASCAIS
exclusivevillacascais.com
14
GOLDEN SKY JETS | EXECUTIVE AVIATION
goldenskyjets.com
14
ACCUEIL
eurotranslogistiques.com
14
ADVOGADO | BALCÃO DO SOLICITADOR - VILA NOVA DE MIL FONTES | BEJA
tc-juridico.pt
14
HOME | BRANDQUEEN GROUP
brandqc.com
Latest Sites
14
FÁBRICA DE SACADA
fabricadesacada.com.br
27
ONLINE EDUCATION FOR TEENS - BRAVE GENERATION ACADEMY
bravegenerationacademy.com
14
WEED MOOD – WEED MOOD
weedmood.net
86
BUY/SELL BITCOIN, ETHER AND ALTCOINS | CRYPTOCURRENCY EXCHANGE | BINANCE
binance.com
41
YOUTUBE
youtube.com.br
32
RÁDIO SPAÇO FM 100.9 - FARROUPILHA (RS)
spacofm.com.br
14
CONSONAR
consonar.com.br
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
14
grandecampo.pt
Last Updated: 3 years
Success
47% of passed verification steps
Warning
15% of total warning
Errors
38% of total errors, require fast action
Share
Download PDF
Desktop
Mobile
Performance
Desktop Score 53%
Best Practices
Desktop Score 77%
SEO
Desktop Score 91%
Progressive Web App
Desktop Score 27%
Performance
Mobile Score 11%
Best Practices
Mobile Score 77%
SEO
Mobile Score 90%
Progressive Web App
Mobile Score 30%
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
Server response times are low (TTFB)
Root document took 420 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources
Potential savings of 1,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression
Potential savings of 1,122 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images
Potential savings of 100 KB
Optimized images load faster and consume less cellular data
Third-Party Usage
1 Third-Party Found
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
50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time
0.4 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 1,438 KB
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
Properly size images
Potential savings of 1,094 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index
2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle
2.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input
Avoid enormous network payloads
Total size was 3,635 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint
1.5 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
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize Critical Requests Depth
44 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
636 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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)
Minify JavaScript
Potential savings of 4 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint
1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
71 requests • 3,635 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
62 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
150 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive
5.0 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 on simulated mobile network at 21.6 s
A fast page load over a cellular network ensures a good mobile user experience
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
Remove unused CSS
Potential savings of 440 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 809 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
Mobile
Third-Party Usage
1 Third-Party Found
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
650 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time
1.9 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 1,576 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 204 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index
9.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle
8.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input
Avoid enormous network payloads
Total size was 3,650 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work
3.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint
6.1 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
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize Critical Requests Depth
44 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
636 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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)
Minify JavaScript
Potential savings of 4 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint
6.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small
72 requests • 3,650 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
63 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay
660 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive
21.9 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 21.9 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency
140 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)
12450 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 not sized appropriately
82% 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
98.6% 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 447 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 809 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 540 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources
Potential savings of 5,090 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression
Potential savings of 1,122 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images
Potential savings of 100 KB
Optimized images load faster and consume less cellular data
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
grandecampo.co
Available
Buy Now!
grandecampo.us
Available
Buy Now!
grandecampo.com
Available
Buy Now!
grandecampo.org
Available
Buy Now!
grandecampo.net
Available
Buy Now!
gandecampo.pt
Available
Buy Now!
trandecampo.pt
Available
Buy Now!
brandecampo.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...