7.7 sec in total
312 ms
6.7 sec
693 ms
Welcome to unibanco.pt homepage info - get ready to check Unibanco best content for Portugal right away, or after learning these important things about unibanco.pt
Conheça o cartão de crédito UNIBANCO e pague em 3 vezes as suas compras, com oferta de cashback e crédito até 50 dias sem juros. Adira já!
Visit unibanco.ptWe analyzed Unibanco.pt page load time and found that the first response time was 312 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
unibanco.pt performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value14.1 s
0/100
25%
Value9.3 s
13/100
10%
Value1,750 ms
10/100
30%
Value0.557
13/100
15%
Value14.1 s
9/100
10%
312 ms
718 ms
81 ms
38 ms
2413 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 87% of them (60 requests) were addressed to the original Unibanco.pt, 4% (3 requests) were made to Cdn.cookielaw.org and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Unibanco.pt.
Page size can be reduced by 159.6 kB (3%)
5.3 MB
5.2 MB
In fact, the total size of Unibanco.pt 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. 55% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 118.0 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 118.0 kB or 84% of the original size.
Potential reduce by 41.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. Unibanco images are well optimized though.
Potential reduce by 224 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 7 (11%)
61
54
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unibanco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
unibanco.pt
312 ms
www.unibanco.pt
718 ms
gtm.js
81 ms
otSDKStub.js
38 ms
827f1.css
2413 ms
ae565.css
2653 ms
byside_webcare.js
593 ms
8e0632c0-73f8-41ff-a995-c9b6100bd2d0.json
29 ms
location
98 ms
6567a.js
3199 ms
9e7c6.js
2153 ms
otBannerSdk.js
20 ms
474 ms
uni-sprite.png
135 ms
Banner-HP_desktop_MUDA_2024-scaled.jpg
541 ms
Banner-HP_tablet_MUDA_2024.jpg
871 ms
Banner-HP_Mobile.jpg
672 ms
Unibanco-trividir-verao-hp-desk-scaled.jpg
761 ms
Unibanco-trividir-verao-hp-tablet-scaled.jpg
881 ms
Unibanco-trividir-verao-hp-mobile.jpg
978 ms
Unibanco-campanha-debito-direto-hp-desk-scaled.jpg
1071 ms
Unibanco-campanha-debito-direto-hp-tablet.jpg
763 ms
Unibanco-campanha-debito-direto-hp-mobile.jpg
979 ms
MGM-cartao-unibanco-desk-hp-scaled.jpg
989 ms
MGM-cartao-unibanco-tablet-hp-scaled.jpg
1307 ms
MGM-cartao-unibanco-mobile-hp.jpg
995 ms
Unibanco-credito-pessoal-2T24-desk.png
1841 ms
Unibanco-credito-pessoal-2T24-tablet.png
1195 ms
Unibanco-credito-pessoal-2T24-mobile.png
1099 ms
Unibanco-credito-consolidado-2T24-desk.png
1108 ms
Unibanco-credito-consolidado-2T24-tablet.png
1290 ms
Unibanco-credito-consolidado-2T24-mobile.png
1207 ms
Conta-UNIBANCO-Desktop.jpg
1220 ms
Conta-UNIBANCO-Tablet.jpg
1306 ms
Conta-UNIBANCO-Mobile.jpg
1317 ms
Website_Desktop_1920x620.png
1335 ms
Website_Tablet_768x620.png
1613 ms
Banner_Fraturas_Mobile.jpg
1524 ms
fbevents.js
48 ms
ModernEra-Light.woff
1352 ms
ModernEra-Regular.woff
1367 ms
ModernEra-Medium.woff
1390 ms
ModernEra-Bold.woff
1460 ms
wARDj0u
13 ms
ModernEra-Black.woff
1475 ms
logo-uni-50-years.svg
1475 ms
logo-uni.svg
1553 ms
icon-3x-sem-juros.png
1556 ms
icon-oferta-cashback.png
1563 ms
UNIBANCO_Icones_CMYK_192px-24.png
1581 ms
UNIBANCO_Icones_CMYK_192px-25.png
1591 ms
Unibanco-trividir-verao-cartao.png
1206 ms
gerir-conta-unibanco-1.png
1078 ms
credito-pessoal-unibanco.png
1203 ms
Group-15.png
1012 ms
Group-18.png
1069 ms
Group-14-1.png
988 ms
Group-22-3.png
979 ms
UNIBANCO_Icones_CMYK_192px-101.png
903 ms
UNIBANCO_Icones_CMYK_192px-91.png
964 ms
apps-846x1024.png
1499 ms
footer-facebook.svg
971 ms
footer-instagram.svg
898 ms
footer-youtube.svg
885 ms
homebanking_google_play.png
880 ms
homebanking_app_store.png
855 ms
logo-unibanco.png
866 ms
logo-reduniq.svg
855 ms
logo-unicre-blue.svg
802 ms
unibanco.pt 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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
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>).
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.
unibanco.pt 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
unibanco.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unibanco.pt 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 Unibanco.pt 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.
unibanco.pt
Open Graph data is detected on the main page of Unibanco. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: