Your Website Score is

Similar Ranking

93
GOOGLE
google.com
93
UOL - O MELHOR CONTEÚDO
uol.com.br
91
A PIPOCA MAIS DOCE
apipocamaisdoce.sapo.pt
91
HOTMART: APRENDA O QUE QUISER, ENSINE O QUE SOUBER
go.hotmart.com
91
SAPO
sapo.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
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

93 uol.com.br Last Updated: 9 months

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

Desktop

Mobile

Performance Mobile Score 19%
Best Practices Mobile Score 69%
SEO Mobile Score 99%
Progressive Web App Mobile Score 50%
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

Mobile

Mobile Screenshot
Serve images in next-gen formats Potential savings of 129 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
Tap targets are not 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
Avoids enormous network payloads Total size was 1,786 KB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 720 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 4,620 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid an excessive DOM size 2,801 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 310 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
Serve static assets with an efficient cache policy 20 resources found
A long cache lifetime can speed up repeat visits to your page
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
Time to Interactive 19.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First CPU Idle 16.7 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 Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Minify JavaScript Potential savings of 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time
Initial server response time was short Root document took 340 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint 4.8 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce the impact of third-party code Third-party code blocked the main thread for 1,780 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
Efficiently encode images Potential savings of 100 KB
Optimized images load faster and consume less cellular data
Reduce JavaScript execution time 10.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize main-thread work 25.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.478
Cumulative Layout Shift measures the movement of visible elements within the viewport
Document uses legible font sizes 83.52% 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 83 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
Avoid chaining critical requests 4 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 67 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to 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
First Contentful Paint (3G) 1954 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Speed Index 9.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused JavaScript Potential savings of 439 KB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint 10.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Page load is not fast enough on mobile networks Interactive at 19.1 s
A fast page load over a cellular network ensures a good mobile user experience
Keep request counts low and transfer sizes small 166 requests • 1,787 KB
To set budgets for the quantity and size of page resources, add a budget.json file

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