5.7 sec in total
1.9 sec
3.4 sec
377 ms
Click here to check amazing Uprc content for Puerto Rico. Otherwise, check out these important facts you probably never knew about uprc.edu
Visit uprc.eduWe analyzed Uprc.edu page load time and found that the first response time was 1.9 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
uprc.edu performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value11.7 s
0/100
25%
Value10.4 s
8/100
10%
Value960 ms
29/100
30%
Value0.117
85/100
15%
Value11.1 s
20/100
10%
1875 ms
120 ms
119 ms
117 ms
290 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 96% of them (78 requests) were addressed to the original Uprc.edu, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Uprc.edu.
Page size can be reduced by 713.0 kB (50%)
1.4 MB
714.9 kB
In fact, the total size of Uprc.edu main page is 1.4 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. 40% of websites need less resources to load. Javascripts take 740.0 kB which makes up the majority of the site volume.
Potential reduce by 96.5 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 96.5 kB or 86% of the original size.
Potential reduce by 14.4 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. Uprc images are well optimized though.
Potential reduce by 522.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 522.9 kB or 71% of the original size.
Potential reduce by 79.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. Uprc.edu needs all CSS files to be minified and compressed as it can save up to 79.1 kB or 83% of the original size.
Number of requests can be reduced by 45 (58%)
78
33
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uprc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
uprc.edu
1875 ms
prettyPhoto.css
120 ms
galleryview.css
119 ms
mod_accordeonck_css.php
117 ms
mootools-core.js
290 ms
core.js
117 ms
caption.js
163 ms
jquery-1.8.2.min.js
348 ms
jquery.prettyPhoto.js
229 ms
mootools-more.js
412 ms
mod_accordeonck.js
171 ms
css
25 ms
general.css
217 ms
main.css
229 ms
nav.css
273 ms
template.css
284 ms
moomenuh.css
284 ms
moomenuh_right.css
329 ms
supersized.shutter.css
339 ms
ContentFlowAddOn_white.css
340 ms
contentflow.css
342 ms
dynamic_css.php
384 ms
jquery-162.js
515 ms
jquery.easing.min.js
396 ms
supersized.3.2.1.js
398 ms
supersized.shutter.js
397 ms
contentflow.js
456 ms
UvumiDropdown.js
456 ms
tooltips.js
457 ms
jquery.galleryview.js
414 ms
mycontentflow.css
57 ms
ContentFlowAddOn_white.js
93 ms
openbox.png
64 ms
centerBarBg2.jpg
63 ms
shadow-top-site-top.png
65 ms
shadow-top-site-down.png
64 ms
centerBarMid2.jpg
389 ms
black-03.png
65 ms
printButton.png
387 ms
universia.png
388 ms
white-93.png
369 ms
social-links.png
372 ms
li_bg.png
369 ms
plus.png
369 ms
uprc.edu
976 ms
underline.png
338 ms
UPRC-Derechos-Reservado.png
338 ms
back.png
339 ms
forward.png
339 ms
bg-black.png
340 ms
thumb-back.png
341 ms
thumb-forward.png
341 ms
progress-back.png
340 ms
progress-bar.png
340 ms
nav-bg.png
342 ms
bg-hover.png
342 ms
pause.png
340 ms
button-tray-up.png
342 ms
up-controls-white.png
342 ms
white-80.png
342 ms
bg-bottom-left.png
343 ms
bg-bottom-right.png
343 ms
analytics.js
310 ms
nav-dot.png
58 ms
5.jpg
342 ms
1.jpg
341 ms
3.jpg
323 ms
progress.gif
63 ms
1458052290_bomba2tiempos_web.jpg
167 ms
1456773126_cultura_web.jpg
185 ms
1458248196_estu_web.jpg
314 ms
1455128689_estudiante_web.jpg
283 ms
1427743112_jagurjingle_web.png
506 ms
loader.gif
377 ms
control.png
376 ms
collect
12 ms
next.png
214 ms
prev.png
214 ms
pause.png
242 ms
overlay_border_left.png
249 ms
control_active.png
60 ms
uprc.edu 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
uprc.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uprc.edu can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Uprc.edu 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.
uprc.edu
Open Graph description is not detected on the main page of Uprc. 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: