Your Website Score is

Latest Sites

14
FORTIS CONSULTING – STP
fortis.st
26
FORTIS CONSULTING |
fortis.pt
24
SP CLINIC: MEDICINA CHINESA, SAÚDE & ESTÉTICA EM LISBOA
spclinic.pt
85
PÚBLICO — PENSE BEM, PENSE PÚBLICO
publico.pt
60
WORTEN ONLINE | TUDO O QUE PRECISA EM WORTEN.PT - 24H
worten.pt
26
AULAS DE MÚSICA | LISBOA | ACADEMIA DE MÚSICA DE TELHEIRAS
academiamusicatelheiras.com
44
ESCOLA DE MÚSICA | AULAS DE PIANO | AULAS DE GUITARRA E GUITARRA PORTUGUESA | LUSOMUSIC
lusomusic.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

85 publico.pt Last Updated: 4 weeks

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

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 73%
SEO Desktop Score 91%
Progressive Web App Desktop Score 73%
Performance Mobile Score 35%
Best Practices Mobile Score 67%
SEO Mobile Score 88%
Progressive Web App Mobile Score 75%
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

Desktop

Desktop Screenshot
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Defer offscreen images Potential savings of 1,099 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 4,510 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
Keep request counts low and transfer sizes small 133 requests • 7,095 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid enormous network payloads Total size was 7,095 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Remove unused CSS Potential savings of 92 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
Efficiently encode images Potential savings of 3,679 KiB
Optimized images load faster and consume less cellular data
Avoid an excessive DOM size 4,414 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 large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First CPU Idle 2.3 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/).
Includes front-end JavaScript libraries with known security vulnerabilities 12 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
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
Cumulative Layout Shift 0.066
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
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
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
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Remove unused JavaScript Potential savings of 287 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Serve static assets with an efficient cache policy 84 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Properly size images Potential savings of 4,808 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid serving legacy JavaScript to modern browsers Potential savings of 15 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 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
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 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

Mobile

Mobile Screenshot
Keep request counts low and transfer sizes small 127 requests • 6,819 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index 4.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 3.5 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 16.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Tap targets are not sized appropriately 44% 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
Includes front-end JavaScript libraries with known security vulnerabilities 12 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Cumulative Layout Shift 0.277
Cumulative Layout Shift measures the movement of visible elements within the viewport
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/).
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
Minimize third-party usage Third-party code blocked the main thread for 230 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
First Contentful Paint (3G) 5160 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Properly size images Potential savings of 3,663 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
User Timing marks and measures 1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Minimize main-thread work 9.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 4,414 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 15 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
Max Potential First Input Delay 670 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 5.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 78 resources found
A long cache lifetime can speed up repeat visits to your page
Document uses legible font sizes 97.49% 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 94 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Efficiently encode images Potential savings of 3,660 KiB
Optimized images load faster and consume less cellular data
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
Defer offscreen images Potential savings of 1,245 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid enormous network payloads Total size was 6,819 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce JavaScript execution time 3.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid an excessive DOM size 4,415 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)
Estimated Input Latency 150 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
Total Blocking Time 1,840 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused JavaScript Potential savings of 253 KiB
Remove unused JavaScript to reduce bytes consumed by network activity

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