5.4 sec in total
613 ms
4.6 sec
175 ms
Welcome to epm.br homepage info - get ready to check EPM best content for Brazil right away, or after learning these important things about epm.br
Escola Paulista de Medicina da Universidade Federal de São Paulo - UNIFESP
Visit epm.brWe analyzed Epm.br page load time and found that the first response time was 613 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
epm.br performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value17.0 s
0/100
25%
Value14.5 s
1/100
10%
Value530 ms
55/100
30%
Value0.031
100/100
15%
Value14.9 s
8/100
10%
613 ms
2185 ms
59 ms
200 ms
586 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Epm.br, 69% (27 requests) were made to Unifesp.br and 8% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Unifesp.br.
Page size can be reduced by 489.3 kB (72%)
676.4 kB
187.1 kB
In fact, the total size of Epm.br main page is 676.4 kB. 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. Javascripts take 290.1 kB which makes up the majority of the site volume.
Potential reduce by 46.3 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 46.3 kB or 81% of the original size.
Potential reduce by 16.1 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. Obviously, EPM needs image optimization as it can save up to 16.1 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 187.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 187.1 kB or 64% of the original size.
Potential reduce by 239.7 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. Epm.br needs all CSS files to be minified and compressed as it can save up to 239.7 kB or 84% of the original size.
Number of requests can be reduced by 25 (76%)
33
8
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EPM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
epm.br
613 ms
2185 ms
css
59 ms
k2.css
200 ms
bootstrap.min.css
586 ms
bootstrap-responsive.min.css
558 ms
font-awesome.css
595 ms
css
66 ms
mobile-menu.css
578 ms
template.css
580 ms
preset1.css
597 ms
phocadownload.css
750 ms
phocadownload.css
780 ms
finder.css
777 ms
template.css
773 ms
mootools-core.js
965 ms
core.js
774 ms
jquery.min.js
1303 ms
jquery-noconflict.js
989 ms
jquery-migrate.min.js
988 ms
k2.js
987 ms
jquery-noconflict.js
987 ms
bootstrap.min.js
1159 ms
modernizr-2.6.2.min.js
1162 ms
helix.core.js
1160 ms
menu.js
1164 ms
autocompleter.js
1166 ms
ga.js
63 ms
Unifesp-marca.png
226 ms
epmlogo.png
377 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
135 ms
Hm1qjDlZpOdVXoa-QGE7_w.ttf
178 ms
fontawesome-webfont.woff
375 ms
sdk.js
74 ms
__utm.gif
93 ms
__utm.gif
80 ms
85 ms
collect
78 ms
xd_arbiter.php
64 ms
epm.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
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
epm.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
Browser errors were logged to the console
epm.br SEO score
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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epm.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Epm.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.
epm.br
Open Graph description is not detected on the main page of EPM. 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: