6.4 sec in total
531 ms
5.7 sec
182 ms
Visit pucrs.br now to see the best up-to-date PUCRS content for Brazil and also check out these interesting facts you probably never knew about pucrs.br
Um novo mundo de possibilidades está à sua espera! Vem com a gente. Viva experiências incríveis na melhor universidade do Sul do País. Na PUCRS você é o protagonista da sua formação e pode escolher as...
Visit pucrs.brWe analyzed Pucrs.br page load time and found that the first response time was 531 ms and then it took 5.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.
pucrs.br performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.5 s
18/100
25%
Value6.5 s
38/100
10%
Value850 ms
34/100
30%
Value0.134
80/100
15%
Value17.0 s
4/100
10%
531 ms
1116 ms
536 ms
519 ms
519 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 69% of them (54 requests) were addressed to the original Pucrs.br, 6% (5 requests) were made to Googleapis.com and 5% (4 requests) were made to Farm2.staticflickr.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pucrs.br.
Page size can be reduced by 657.1 kB (37%)
1.8 MB
1.1 MB
In fact, the total size of Pucrs.br main page is 1.8 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 14.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 14.7 kB or 73% of the original size.
Potential reduce by 95.7 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. PUCRS images are well optimized though.
Potential reduce by 265.5 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 265.5 kB or 73% of the original size.
Potential reduce by 281.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. Pucrs.br needs all CSS files to be minified and compressed as it can save up to 281.1 kB or 81% of the original size.
Number of requests can be reduced by 24 (35%)
69
45
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PUCRS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pucrs.br
531 ms
portal
1116 ms
536 ms
reset.css
519 ms
fonts.css
519 ms
jquery.fancybox.css
525 ms
style.css
523 ms
pages.css
701 ms
menu.css
510 ms
mediaqueries.css
682 ms
home.css
861 ms
jquery.js
2080 ms
functions.js
696 ms
modernizr.js
910 ms
conversion.js
30 ms
jquery-latest.js
11 ms
jquery-migrate-1.0.0.js
14 ms
scripts.js
692 ms
jquery-latest.min.js
14 ms
swfobject.js
38 ms
video_yt.js
534 ms
jquery.slides.min.js
538 ms
date-en-US.js
1042 ms
client.js
64 ms
urchin.js
32 ms
bg_site_cover.png
182 ms
24460569844_79cb225882_o.jpg
169 ms
2016_02_04-revista_pucrs_177-entrevista-marco_bobbio.png
1748 ms
24627200843_b6d0b67033_o.jpg
143 ms
25273985645_fae19887b2_o.jpg
140 ms
24460825653_d96b9c3474_o.jpg
143 ms
2015_02_18-volta_as_aulas.png
879 ms
2015_10_09-famecos.png
705 ms
bg_home_top.jpg
693 ms
i_logo_pucrs.png
520 ms
bg_search_text.png
188 ms
bt_search_sub.png
188 ms
bg_switch_location.png
188 ms
bg_main_menu.png
187 ms
bg_central_alunos_home.jpg
708 ms
bg_mest_dout_home.jpg
356 ms
bg_tecnopuc_home.png
357 ms
bg_publicacoes_home.png
357 ms
btn-agenda-capa.png
528 ms
ttl_slogan.png
531 ms
200anos.svgz
743 ms
i_logo_maristas.png
691 ms
i_social_facebook.png
701 ms
i_social_twitter.png
704 ms
i_social_instagram.png
863 ms
i_social_youtube.png
864 ms
128 ms
bg_footer.png
839 ms
footer_spacer.png
846 ms
opensans-regular.woff
1018 ms
robotocondensed-regular.woff
1226 ms
opensans-semibold.woff
1167 ms
opensans-bold.woff
1172 ms
opensans-italic.woff
1006 ms
cb=gapi.loaded_0
105 ms
__utm.gif
57 ms
channels
142 ms
channels
199 ms
channels
234 ms
mini-carousel_9.jpg
1090 ms
mini-carousel_10.jpg
1272 ms
mini-carousel_11.jpg
1420 ms
mini-carousel_12.jpg
1422 ms
mini-carousel_13.jpg
1264 ms
bt_slides_prev.png
1308 ms
bt_slides_next.png
1436 ms
56 ms
postmessageRelay
37 ms
api.js
41 ms
core:rpc:shindig.random:shindig.sha1.js
96 ms
2536007149-postmessagerelay.js
17 ms
playlistItems
308 ms
playlistItems
1247 ms
pucrs.br accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
pucrs.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
pucrs.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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pucrs.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 Pucrs.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.
pucrs.br
Open Graph description is not detected on the main page of PUCRS. 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: