5.1 sec in total
151 ms
3 sec
1.9 sec
Welcome to uatt.com.br homepage info - get ready to check Uatt best content for Brazil right away, or after learning these important things about uatt.com.br
Uatt?
Visit uatt.com.brWe analyzed Uatt.com.br page load time and found that the first response time was 151 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
uatt.com.br performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value8.6 s
1/100
25%
Value10.4 s
8/100
10%
Value6,720 ms
0/100
30%
Value0.366
29/100
15%
Value23.1 s
1/100
10%
151 ms
63 ms
116 ms
47 ms
54 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 29% of them (26 requests) were addressed to the original Uatt.com.br, 43% (38 requests) were made to S3.uatt.com.br and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source S3.uatt.com.br.
Page size can be reduced by 747.3 kB (58%)
1.3 MB
548.8 kB
In fact, the total size of Uatt.com.br main page is 1.3 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. HTML takes 862.0 kB which makes up the majority of the site volume.
Potential reduce by 714.7 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 714.7 kB or 83% of the original size.
Potential reduce by 510 B
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. Obviously, Uatt needs image optimization as it can save up to 510 B or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.1 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 19 (37%)
51
32
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uatt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
uatt.com.br
151 ms
uatt.com.br
63 ms
www.uatt.com.br
116 ms
css
47 ms
materialdesignicons.min.css
54 ms
6542917a100c89.32954882.webp
306 ms
state.js
285 ms
db162e5.js
405 ms
10e78f9.js
406 ms
943e33d.js
405 ms
f081cd9.js
408 ms
f1e37e3.js
751 ms
9bcb472.js
423 ms
gtm.js
706 ms
relogio-desktop.0bcbbda.svg
546 ms
mastercard.ffcfb42.svg
563 ms
visa.6f9bbf1.svg
547 ms
amex.607c2e8.svg
568 ms
elo.c0b0589.svg
569 ms
hipercard.a0129cb.svg
816 ms
boleto.b016cdd.svg
601 ms
pix-bc.7d90b85.svg
874 ms
icone-site-seguro.d5c5f4a.png
877 ms
miniature_6144fe2883ab11a2e74766d0be9bf0ee.webp
562 ms
miniature_bf5a5340782a83eaa7df2c6623c37003.webp
599 ms
miniature_8a9d3bd46378fa41d6c45429135a74c9.webp
814 ms
miniature_dc5022638b2c0ea95d8a8de62f7ff69a.webp
876 ms
miniature_27b9e520ac23bdb0af087dcec5c1d0a6.webp
817 ms
miniature_fae5c067f3e14b6046b86502f8c9cb64.webp
648 ms
miniature_a952cf3ef14c0383e5c12c011cd6f9ac.webp
874 ms
miniature_74c6b810c16402b5c24d076849daa83c.webp
816 ms
miniature_e153c84d2479fba008b554ad06834d6e.webp
813 ms
miniature_71c0c355a6f1fb73421af38886dfb86e.webp
1015 ms
664b602eac2630.06512083.webp
1226 ms
664b600a0117b1.09337928.webp
1226 ms
664b601e409910.04585505.webp
1014 ms
miniature_c953ac8cb08ff83f2762034da1ebf6dc.webp
1225 ms
miniature_ae4f0782e41a4ecf07c46872d632edb2.webp
1226 ms
6418b2d20b9501.00924203.webp
1537 ms
6418b25d40c488.78775397.webp
1528 ms
6418b295ca6443.53886196.webp
1565 ms
6418b327552d90.97733810.webp
1566 ms
miniature_68fd41976c30f4f688dca19d2a1a9093.webp
1536 ms
miniature_b777e1ea8c75d329dba67ecca65bd14f.webp
1536 ms
miniature_416ef2bd8a6ef759efd5eabca1fa28fc.webp
1654 ms
miniature_f9209af65bb1ba81399418f0af349da1.webp
1594 ms
miniature_1f21edd3b35f8e3e4800512daf44ec34.webp
1608 ms
miniature_6010b21eef504c1ecc016267a0c61018.webp
1664 ms
miniature_bb3cd47e902d9b0b96be04ed430c2508.webp
1636 ms
miniature_ee44fa0e845a5346b7cd2dd501615441.webp
1626 ms
miniature_d8fd11fecee14040ea2d070e9ced512b.webp
1630 ms
miniature_bc74c010376d19431a82f46a11f45363.webp
1663 ms
63fcbba643a470.93136112.webp
1676 ms
63fcbac4eb61a6.00118336.webp
1664 ms
63fcbc0e060824.15343864.webp
1694 ms
63fcba8f05b307.19508203.webp
1708 ms
Roboto-Medium.f2e8ef1.woff
659 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
428 ms
Roboto-Regular.047f5a3.woff
659 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
428 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
593 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
655 ms
Roboto-Bold.4c2a279.woff
658 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
657 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
792 ms
Roboto-Italic.d2afd38.woff
1001 ms
Roboto-MediumItalic.1b93d69.woff
1131 ms
Roboto-BoldItalic.0d2d228.woff
1130 ms
icomoon.4f8ee29.woff
745 ms
js
388 ms
sdk.js
910 ms
analytics.js
935 ms
destination
718 ms
hotjar-2749489.js
904 ms
core.js
713 ms
injector.js
1645 ms
6cdccb4e-99a7-4c92-b005-60612055b05c-loader.js
1359 ms
F449D8BA7FCA48AC92BACFB1DF89A33A.js
1285 ms
load.js
931 ms
loader.js
929 ms
current
116 ms
modules.7b6d7646601d8cd7fb5f.js
48 ms
collect
15 ms
collect
12 ms
ga-audiences
29 ms
6538234e400416.32944144.webp
42 ms
65d7aaa102d591.88979947.webp
67 ms
6647993edc71f1.92757034.webp
37 ms
66476b1f9ac737.44120300.webp
47 ms
uatt.com.br accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
uatt.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
uatt.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
PT
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uatt.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Uatt.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.
uatt.com.br
Open Graph data is detected on the main page of Uatt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: