2.7 sec in total
358 ms
1.9 sec
417 ms
Click here to check amazing Vestibular UPF content for Brazil. Otherwise, check out these important facts you probably never knew about vestibular.upf.br
A UPF, fundada em 1968, tem suas ações norteadas e sustentadas por quatro pilares: ensino, pesquisa, extensão e inovação tecnológica.
Visit vestibular.upf.brWe analyzed Vestibular.upf.br page load time and found that the first response time was 358 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster. This domain responded with an error, which can significantly jeopardize Vestibular.upf.br rating and web reputation
vestibular.upf.br performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value11.1 s
0/100
25%
Value13.3 s
2/100
10%
Value1,010 ms
27/100
30%
Value0.008
100/100
15%
Value14.0 s
10/100
10%
358 ms
395 ms
142 ms
37 ms
37 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 51% of them (42 requests) were addressed to the original Vestibular.upf.br, 9% (7 requests) were made to Apis.google.com and 9% (7 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (921 ms) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 642.0 kB (8%)
7.7 MB
7.1 MB
In fact, the total size of Vestibular.upf.br main page is 7.7 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. 55% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 40.4 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. This page needs HTML code to be minified as it can gain 6.9 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 40.4 kB or 80% of the original size.
Potential reduce by 105.2 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. Vestibular UPF images are well optimized though.
Potential reduce by 289.2 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 289.2 kB or 66% of the original size.
Potential reduce by 207.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. Vestibular.upf.br needs all CSS files to be minified and compressed as it can save up to 207.1 kB or 86% of the original size.
Number of requests can be reduced by 47 (64%)
74
27
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vestibular UPF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
vestibular.upf.br
358 ms
Home
395 ms
bootstrap-3.3.4.css
142 ms
grid-custom.css
37 ms
cor.css
37 ms
main.css
107 ms
fonts.css
35 ms
platform.js
101 ms
jquery-1.11.2.min.js
127 ms
bootstrap-3.3.4.min.js
114 ms
jquery.mobile.custom-1.4.5.min.js
116 ms
global.js
58 ms
globalize.js
118 ms
globalize.culture.pt-BR.js
113 ms
globalize.culture.en-US.js
118 ms
jquery.validate.min.js
222 ms
additional-methods.min.js
133 ms
jquery.toastmessage.js
126 ms
jquery.blockui.min.js
219 ms
analytics.js
63 ms
app.js
232 ms
messages.js
233 ms
extends.js
217 ms
main.js
216 ms
slider.js
232 ms
Shared.js
233 ms
analytics.js
86 ms
sdk.js
255 ms
1661714_1687855541501909_279165976_n.jpg
562 ms
widgets.js
114 ms
ir-conteudo.png
63 ms
0dff5707-2e19-4742-83fa-45f525e2defb.jpg
90 ms
ba5b9f03-64c2-4856-bc12-de5f6601fb6c.jpg
442 ms
b8e4ecb1-08c4-47ec-8a4d-9c53409d8fa9.png
856 ms
bkg.png
116 ms
43a8da62-f43d-4090-8a88-8cdd983fdc5d.png
918 ms
acd2e19a-6c84-4178-8d5d-34015aa8fc13.jpg
572 ms
4f5edfd8-c468-4af6-9e77-2234708db096.jpg
485 ms
instagram-ico.png
190 ms
instagram-btn.png
279 ms
logo-footer.png
460 ms
axys.png
511 ms
10665305_239009233108716_742605806_n.jpg
784 ms
12826153_848398901952212_313083708_n.jpg
785 ms
10724126_1679355799005218_160463844_n.jpg
921 ms
12826291_230401540640014_2042049154_n.jpg
920 ms
Montserrat-Bold-webfont.woff
542 ms
glyphicons-halflings-regular.woff
552 ms
glyphicons-halflings-regular.woff
571 ms
Lato-Regular-webfont.woff
629 ms
linkid.js
77 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
93 ms
subscribe_embed
189 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
33 ms
collect
38 ms
collect
137 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
47 ms
postmessageRelay
105 ms
98 ms
www-subscribe-embed-vflWJjAep.css
61 ms
www-subscribe-embed.js
81 ms
xd_arbiter.php
136 ms
xd_arbiter.php
249 ms
3193398744-postmessagerelay.js
42 ms
rpc:shindig_random.js
35 ms
www-hitchhiker-vfluKv9vH.png
41 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_0
18 ms
jot
112 ms
cb=gapi.loaded_2
12 ms
border_3.gif
13 ms
subscribe_embed
67 ms
spacer.gif
16 ms
border_3.gif
24 ms
bubbleSprite_3.png
31 ms
bubbleDropR_3.png
36 ms
bubbleDropB_3.png
37 ms
www-subscribe-embed-card-vflqARhQ4.css
17 ms
www-subscribe-embed-card.js
17 ms
glyphicons-halflings-regular.ttf
72 ms
glyphicons-halflings-regular.svg
51 ms
vestibular.upf.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
<frame> or <iframe> elements do not have a title
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
vestibular.upf.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
Page has valid source maps
vestibular.upf.br 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vestibular.upf.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 Vestibular.upf.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.
vestibular.upf.br
Open Graph description is not detected on the main page of Vestibular UPF. 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: