23.1 sec in total
759 ms
21.6 sec
748 ms
Welcome to unifor.br homepage info - get ready to check Unifor best content for Brazil right away, or after learning these important things about unifor.br
A Universidade de Fortaleza (Unifor) conta com mais de 25 mil alunos, 40 cursos de Graduação, 17 Mestrados e Doutorados, 80 especializações e MBAs, além de 230 laboratórios para pesquisa e prática do ...
Visit unifor.brWe analyzed Unifor.br page load time and found that the first response time was 759 ms and then it took 22.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
unifor.br performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value16.5 s
0/100
25%
Value23.9 s
0/100
10%
Value3,490 ms
1/100
30%
Value0.018
100/100
15%
Value27.2 s
0/100
10%
759 ms
71 ms
271 ms
405 ms
387 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 73% of them (84 requests) were addressed to the original Unifor.br, 5% (6 requests) were made to Googletagmanager.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Latam-unifor.netmng.com.
Page size can be reduced by 688.1 kB (13%)
5.3 MB
4.6 MB
In fact, the total size of Unifor.br main page is 5.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 418.8 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 418.8 kB or 79% of the original size.
Potential reduce by 197.3 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. Unifor images are well optimized though.
Potential reduce by 72.0 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 72.0 kB or 15% of the original size.
Number of requests can be reduced by 54 (50%)
109
55
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unifor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
unifor.br
759 ms
injector.js
71 ms
combo
271 ms
clay.css
405 ms
main.css
387 ms
combo
395 ms
js_loader_config
397 ms
combo
588 ms
combo
477 ms
combo
668 ms
js_bundle_config
486 ms
main.css
691 ms
vendors.js
524 ms
assets.js
568 ms
js
55 ms
main.js
320 ms
aui_deprecated.css
231 ms
analytics.js
139 ms
gtm.js
113 ms
Banner-QR-Code-Unifor.jpg
1140 ms
icon-contrast-white.svg
201 ms
libras.svg
202 ms
unifor-logo-vertical.svg
204 ms
unifor-logo-vertical-negative.svg
203 ms
unifor-logo-horizontal.svg
205 ms
unifor-logo-horizontal-negative.svg
200 ms
facebook.svg
258 ms
twitter.svg
263 ms
linkedin.svg
262 ms
youtube.svg
259 ms
instagram.svg
261 ms
flickr.svg
260 ms
079422f7-f1ae-ac5b-213e-758215ac8b0b
572 ms
9aa6d531-b5cc-8517-eda4-1ade83b358d7
528 ms
642068a3-98f7-dbc6-181e-0df4f645f86a
629 ms
d7d3aad9-3562-ee9e-3963-292304cf09f8
530 ms
a172c752-5df2-1627-fb0c-9163532d0029
572 ms
28464b97-4139-20de-4366-17c569d039f1
529 ms
1737545a-f874-9346-d8fd-236b0f8b7955
934 ms
16d0fe09-f4c6-02c3-87c9-1e2988abde83
747 ms
3b2c36f3-bcfc-4ff7-2e53-5a1c13fb737e
755 ms
977d4f57-de07-7e56-738a-a08ce12526b4
755 ms
416b2029-8cc0-8667-3e63-c7e9822d7a43
754 ms
b508aecf-8262-f552-42aa-57237ae08d74
810 ms
2acf089a-6c31-80eb-dcd1-83ce5b65bb56
944 ms
2508735a-86f4-a0d6-4e42-c1cab6710e94
1029 ms
7ce7708f-eeed-d435-edb5-42a8a2c57814
945 ms
5ab01e13-14fa-59d5-b2f3-afec3aff7a6a
858 ms
decfd2c0-dc62-7a38-9daf-6cee7084edef
906 ms
984caae2-3bd6-cb72-0dd3-48bc9caf2679
953 ms
4f6cc5d3-3c36-77bc-61f0-4291ccc8910f
1001 ms
381aa422-9391-431b-3cb2-0fd53c2cefb5
1027 ms
a574bd41-dead-536a-5d07-efe5251daedf
1040 ms
6483d138-c40a-7b32-557b-d79847c9999e
1041 ms
e9016805-4a44-d846-35c6-9ec701af3d7a
1047 ms
9db67148-d520-f60c-e9b0-2abc42396338
1027 ms
1052 ms
collect
81 ms
js
96 ms
collect
63 ms
insight.min.js
422 ms
uwt.js
387 ms
destination
297 ms
collect
285 ms
collect.js
30 ms
c3facab9-66c3-44f9-bb94-6f20188b0a80-loader.js
845 ms
latam-unifor.netmng.com
19925 ms
fbevents.js
335 ms
2dc41c796cf2578201032d1.js
378 ms
ytc.js
374 ms
Satoshi-Regular.woff
1007 ms
Satoshi-Bold.woff
1006 ms
1bc3c1a5-9f9e-177b-c3e3-4aaa19722abe
936 ms
068306f2-4366-4abd-0dd5-f5b3bffab171
936 ms
22aa7869-ee51-5412-893a-d09bc1a0bf03
1003 ms
27d20647-f968-f51c-8512-94782af80c49
1000 ms
collect
265 ms
js
360 ms
collect
325 ms
a33c719d-e9ae-dcd6-bf24-48c93a1a975e
987 ms
5a01a3b8-e0cd-2fb4-7eee-31f40e1d3c85
988 ms
21b51fda-c033-62f4-8831-abc5f58af882
989 ms
ac44412f-7d48-aa55-d688-f27e99a8e45f
1024 ms
a4d46ba8-31e7-cfa1-c25d-00b05468c209
1026 ms
a46a5fc4-f9f7-8c33-0414-608c96dd3968
1024 ms
ga-audiences
274 ms
collect
130 ms
js
151 ms
4d3caaa8-d082-1b1e-1b85-3d58bda244ca
798 ms
d7e73dd1-c68d-f925-5a09-9a2b3c00d69b
795 ms
c36d2b7f-7943-21f6-fa4e-168bd04cb2e0
773 ms
ga-audiences
186 ms
618c20cb-9c9e-3958-0623-3dc73c15b1d5
809 ms
10090109.json
52 ms
10106203.json
53 ms
730aa92f-e750-3108-9525-bb304c1e4a7d
779 ms
ga-audiences
164 ms
c474482d-9593-98e7-1b43-670e70471e39
752 ms
adsct
111 ms
adsct
188 ms
4d7e197d-49f0-564e-088d-1e499697f730
755 ms
0adac077-083f-f703-c86d-980618190650
667 ms
b99097aa-7053-9ef9-6378-e4ea54ae5b36
672 ms
62dfc428-3d35-b545-cb5d-86ffdce37edb
717 ms
30ffcd6c-bf00-c85b-e717-569151483064
663 ms
860c794c-d169-767f-25a4-b624a49fa9af
615 ms
c1281ded-8abe-a75a-0f6d-eaf87827cde4
609 ms
fad2de11-8770-2c31-8b02-911e72f23ed1
590 ms
arrow.svg
621 ms
lead-tracking.min.js
3 ms
traffic-source-cookie.min.js
5 ms
458 ms
arrow-gray.svg
457 ms
arrow-yellow.svg
460 ms
Satoshi-Black.woff
470 ms
unifor.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
unifor.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
Browser errors were logged to the console
Page has valid source maps
unifor.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
![]()
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unifor.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 Unifor.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.
unifor.br
Open Graph data is detected on the main page of Unifor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: