8.1 sec in total
1.6 sec
6 sec
445 ms
Click here to check amazing Uem content for Brazil. Otherwise, check out these important facts you probably never knew about uem.br
Visit uem.brWe analyzed Uem.br page load time and found that the first response time was 1.6 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
uem.br performance score
name
value
score
weighting
Value10.9 s
0/100
10%
Value20.2 s
0/100
25%
Value14.8 s
1/100
10%
Value190 ms
90/100
30%
Value0.653
8/100
15%
Value13.8 s
10/100
10%
1643 ms
1722 ms
1464 ms
1379 ms
1661 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 85% of them (58 requests) were addressed to the original Uem.br, 12% (8 requests) were made to Sepang.uem.br and 1% (1 request) were made to Cidadao.pr.gov.br. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Uem.br.
Page size can be reduced by 438.5 kB (19%)
2.3 MB
1.8 MB
In fact, the total size of Uem.br main page is 2.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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 87.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 87.9 kB or 88% of the original size.
Potential reduce by 195.3 kB
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. Uem images are well optimized though.
Potential reduce by 108.9 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 108.9 kB or 73% of the original size.
Potential reduce by 46.4 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. Uem.br needs all CSS files to be minified and compressed as it can save up to 46.4 kB or 84% of the original size.
Number of requests can be reduced by 21 (31%)
67
46
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
uem.br
1643 ms
template_css.css
1722 ms
blue.css
1464 ms
ja-news.css
1379 ms
ja.script.js
1661 ms
ja-transmenuh.css
1668 ms
ja-transmenu.js
2120 ms
ja.header.js
1197 ms
governo-pr.gif
617 ms
1427380599banner_corrupcao_quadrado.jpg
885 ms
logo_FINEP.jpg
1464 ms
seti.gif
644 ms
fund-araucaria.gif
658 ms
cnpq.gif
718 ms
capes.gif
712 ms
capes-periodicos.gif
747 ms
colegiados-superiores.gif
798 ms
univ-aberta-brasil.gif
1025 ms
simbolo-uem-fundo-70.png
182 ms
shadowleft-bg.gif
182 ms
shadownright-bg.gif
184 ms
mainnav-active-bg.gif
186 ms
mainnav-sep.gif
189 ms
logo-blue1.png
731 ms
banner-02.jpg
1297 ms
banner-05.jpg
1631 ms
banner-03.jpg
1825 ms
banner-00.jpg
1881 ms
banner-01.jpg
1114 ms
banner-04.jpg
1642 ms
forint-site-500px.jpg
1484 ms
pibid_placa.jpg
1656 ms
Saude_Mental-site-7120.jpg
1857 ms
prointe-logo.jpg
1994 ms
site-uem-radio.png
1826 ms
site-uem-tv.png
1837 ms
consulta_publica.png
2008 ms
nit.png
2010 ms
logoNationalArchives.jpg
2196 ms
bom-negocio-parana.png
2049 ms
180px-usa-flag.png
2063 ms
sub-logo.gif
2175 ms
gescomp.png
2370 ms
UEM_IRRF.jpg
2192 ms
lista_telefonica_uem.jpg
2233 ms
wifi.jpeg
2246 ms
x.gif
2327 ms
arrowchild-off.gif
2345 ms
header-bg.gif
2345 ms
headerright-bg.gif
2390 ms
topnav-left-bg.gif
2399 ms
stripe1.gif
2510 ms
mainnav-bg.gif
2523 ms
pathway-bg.gif
2527 ms
mainnav-shadow.gif
2378 ms
leftcol-bg.gif
2427 ms
bullet-title.gif
2436 ms
seperator.gif
2540 ms
stripe2.gif
2553 ms
bullet-list.gif
2010 ms
box-br.gif
1631 ms
box-bl.gif
1498 ms
box-tr.gif
1317 ms
box-tl.gif
1277 ms
a-mainlevel-bg.gif
1280 ms
h3-bg.gif
1264 ms
footer-bg.gif
1115 ms
v-seperator.gif
1155 ms
uem.br accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
uem.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
uem.br SEO score
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uem.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 Uem.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
uem.br
Open Graph description is not detected on the main page of Uem. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: