Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 85

    SEO

    Google-friendlier than
    62% of websites

Page Load Speed

12.6 sec in total

First Response

409 ms

Resources Loaded

11.3 sec

Page Rendered

888 ms

uol.com.br screenshot

About Website

Click here to check amazing UOL content for Brazil. Otherwise, check out these important facts you probably never knew about uol.com.br

Visit uol.com.br

Key Findings

We analyzed Uol.com.br page load time and found that the first response time was 409 ms and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

uol.com.br performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value6,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

uol.com.br

409 ms

www.uol.com.br

681 ms

beacon.js

5 ms

home.js

660 ms

uoltm.js

789 ms

Our browser made a total of 216 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Uol.com.br, 24% (51 requests) were made to Akhtm.nspmotion.com and 14% (31 requests) were made to Imguol.com. The less responsive or slowest element that took the longest time to load (7.4 sec) relates to the external source T.dynad.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (47%)

Content Size

3.5 MB

After Optimization

1.8 MB

In fact, the total size of Uol.com.br main page is 3.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 366.3 kB

  • Original 470.3 kB
  • After minification 466.6 kB
  • After compression 103.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 366.3 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 54.9 kB

  • Original 1.3 MB
  • After minification 1.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. UOL images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.2 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 518.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.2 MB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 74.9 kB

  • Original 90.0 kB
  • After minification 80.8 kB
  • After compression 15.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Uol.com.br needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (48%)

Requests Now

203

After Optimization

106

The browser has sent 203 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UOL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 68 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

uol.com.br accessibility score

61

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

uol.com.br best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

uol.com.br SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uol.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Uol.com.br main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of UOL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: