8.3 sec in total
332 ms
7.8 sec
170 ms
Welcome to ufpb.br homepage info - get ready to check UFPB best content for Brazil right away, or after learning these important things about ufpb.br
Visit ufpb.brWe analyzed Ufpb.br page load time and found that the first response time was 332 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ufpb.br performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value11.7 s
0/100
25%
Value15.4 s
1/100
10%
Value14,450 ms
0/100
30%
Value0.075
95/100
15%
Value36.7 s
0/100
10%
332 ms
4522 ms
426 ms
543 ms
659 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 85% of them (63 requests) were addressed to the original Ufpb.br, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Ufpb.br.
Page size can be reduced by 1.3 MB (63%)
2.0 MB
729.4 kB
In fact, the total size of Ufpb.br main page is 2.0 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. 45% of websites need less resources to load. CSS take 856.3 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.3 kB or 80% of the original size.
Potential reduce by 17.9 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. UFPB images are well optimized though.
Potential reduce by 486.8 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 486.8 kB or 67% of the original size.
Potential reduce by 714.3 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. Ufpb.br needs all CSS files to be minified and compressed as it can save up to 714.3 kB or 83% of the original size.
Number of requests can be reduced by 46 (66%)
70
24
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UFPB. 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 31 to 1 for CSS and as a result speed up the page load time.
ufpb.br
332 ms
www.ufpb.br
4522 ms
system.base.css
426 ms
aggregator.css
543 ms
date.css
659 ms
field.css
777 ms
node.css
896 ms
search.css
1010 ms
user.css
1130 ms
extlink.css
1236 ms
views.css
1232 ms
ckeditor.css
1233 ms
ctools.css
1234 ms
lightbox.css
1235 ms
font-awesome.min.css
46 ms
bootstrap.css
1261 ms
base.css
1356 ms
default.css
1360 ms
compatibility.css
1359 ms
styles.css
1373 ms
mains.css
1364 ms
jquery.min.js
1497 ms
jquery.once.js
1480 ms
drupal.js
1479 ms
extlink.js
1482 ms
pt-br_g22Bk8wwpyhfYYqhnnnWA_2ANt8ehymlBF2peDhGZ7g.js
1807 ms
lightbox.js
1498 ms
tb-megamenu-frontend.js
1605 ms
tb-megamenu-touch.js
1610 ms
googleanalytics.js
1603 ms
script.js
1622 ms
jquery.cookie.js
1620 ms
acessibilidade.js
1726 ms
barra.js
998 ms
r800-1024.css
381 ms
r640-800.css
378 ms
r320.css
383 ms
r568.css
382 ms
r960.css
493 ms
lower-320-fix.css
521 ms
normalize.css
510 ms
responsive.css
501 ms
misc.css
507 ms
print.css
557 ms
contraste.css
607 ms
analytics.js
81 ms
EozfWEt5NYY
112 ms
body-bg-repeat.jpg
133 ms
reticula_repeat-x.png
135 ms
logo.png
239 ms
facebook.png
144 ms
twitter.png
128 ms
youtube.png
129 ms
srch-btn.png
273 ms
manuten%C3%A7%C3%A3o_rede%20el%C3%A9trica%20-%202_2.jpg
274 ms
ufpb_1.jpg
276 ms
LOGO%20UFPB.png
360 ms
banner-periodicos-capes.jpg
276 ms
ufpb-revista.jpg
359 ms
banner-periodicos-ufpb.jpg
364 ms
Selo_Acesso.jpg
366 ms
banner-tvufpb.jpg
397 ms
banner-ufpb-virtual.jpg
398 ms
banner-progep.jpg
476 ms
banner-editora.jpg
481 ms
banner-inova.jpg
909 ms
extlink_s.png
425 ms
collect
24 ms
www-embed-player-vflZsBgOl.css
67 ms
www-embed-player.js
91 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
25 ms
ad_status.js
63 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
83 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
87 ms
ufpb.br accessibility score
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
ufpb.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ufpb.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 Ufpb.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.
ufpb.br
Open Graph description is not detected on the main page of UFPB. 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: