Review
Your Website Score is
Update
Similar Ranking
2
JOÃO TERRA - FOTÓGRAFO CASAMENTO | WEDDING PHOTOGRAPHER | AVEIRO, PORTO
joaoterra.com
2
TIAGO BASÍLIO LEITE / FREELANCER / MARKETING E COMUNICAÇÃO
tiagobasilioleite.pt
2
ERROR 404 (NOT FOUND)!!1
voltaaomundoaviajar.com
2
PIMAD
pimad.pt
1
plano-de-saude-sp-sp.com.br
1
wecareon.pt
1
ergobrilho.pt
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
24
WELCOME
portugalvineyards.com
14
LOVEME
lojaloveme.com.br
11
KID TO KID ONLINE
kidtokidonline.pt
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
2
pimad.pt
Last Updated: 3 months
Success
32% of passed verification steps
Warning
38% of total warning
Errors
30% of total errors, require fast action
Share
Download PDF
Desktop
Mobile
Performance
Desktop Score 78%
Best Practices
Desktop Score 79%
SEO
Desktop Score 82%
Progressive Web App
Desktop Score 26%
Performance
Mobile Score 38%
Best Practices
Mobile Score 71%
SEO
Mobile Score 83%
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
Speed Index
1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle
1.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/).
Remove unused JavaScript
Potential savings of 176 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoid chaining critical requests
13 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
279 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)
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Contentful Paint
1.4 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Cumulative Layout Shift
0.071
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Meaningful Paint
1.5 s
First Meaningful Paint measures when the primary content of a page is visible
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
Preload key requests
Potential savings of 1,150 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Serve static assets with an efficient cache policy
24 resources found
A long cache lifetime can speed up repeat visits to your page
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
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 10.3 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid serving legacy JavaScript to modern browsers
Potential savings of 27 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
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
Largest Contentful Paint
2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Avoids enormous network payloads
Total size was 1,467 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay
40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short
Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources
Potential savings of 1,090 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid long main-thread tasks
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Remove unused CSS
Potential savings of 299 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 multiple page redirects
Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
Time to Interactive
1.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Properly size images
Potential savings of 76 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Serve images in next-gen formats
Potential savings of 249 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
Enable text compression
Potential savings of 565 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Keep request counts low and transfer sizes small
34 requests • 1,467 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Mobile
Document uses legible font sizes
98.29% 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
Avoid multiple page redirects
Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
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 chaining critical requests
13 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
Serve images in next-gen formats
Potential savings of 280 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
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Eliminate render-blocking resources
Potential savings of 4,660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Max Potential First Input Delay
210 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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. [Learn more](https://web.dev/first-cpu-idle/).
First Meaningful Paint
6.5 s
First Meaningful Paint measures when the primary content of a page is visible
Page load is not fast enough on mobile networks
Interactive at 10.6 s
A fast page load over a cellular network ensures a good mobile user experience
Cumulative Layout Shift
0.03
Cumulative Layout Shift measures the movement of visible elements within the viewport
Total Blocking Time
280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize main-thread work
3.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small
46 requests • 1,755 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Time to Interactive
10.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index
7.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid serving legacy JavaScript to modern browsers
Potential savings of 34 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
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
Tap targets are not sized appropriately
93% 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
Initial server response time was short
Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Preload key requests
Potential savings of 7,680 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Remove unused CSS
Potential savings of 302 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
Defer offscreen images
Potential savings of 82 KiB
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 53 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve static assets with an efficient cache policy
28 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint (3G)
12630.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Remove unused JavaScript
Potential savings of 277 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression
Potential savings of 565 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid large layout shifts
4 elements found
These DOM elements contribute most to the CLS of the page.
Avoids an excessive DOM size
279 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)
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
Largest Contentful Paint
10.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids enormous network payloads
Total size was 1,755 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Reduce JavaScript execution time
1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
5.9 s
First Contentful Paint marks the time at which the first text or image is painted
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
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
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...