5.8 sec in total
456 ms
4.6 sec
779 ms
Visit eupago.pt now to see the best up-to-date Eupago content for Portugal and also check out these interesting facts you probably never knew about eupago.pt
Cartão de crédito, TPAs, referências Multibanco, MB Way e pagamentos internacionais no seu negócio. Autorizado pelo Banco de Portugal e pela PSD2.
Visit eupago.ptWe analyzed Eupago.pt page load time and found that the first response time was 456 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eupago.pt performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.7 s
32/100
25%
Value6.2 s
43/100
10%
Value1,330 ms
17/100
30%
Value0.001
100/100
15%
Value10.1 s
26/100
10%
456 ms
71 ms
205 ms
710 ms
306 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 86% of them (83 requests) were addressed to the original Eupago.pt, 6% (6 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Eupago.pt.
Page size can be reduced by 872.6 kB (33%)
2.7 MB
1.8 MB
In fact, the total size of Eupago.pt main page is 2.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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 68.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. This page needs HTML code to be minified as it can gain 23.3 kB, which is 29% 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 68.0 kB or 84% of the original size.
Potential reduce by 305.8 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. Obviously, Eupago needs image optimization as it can save up to 305.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 311.3 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 311.3 kB or 76% of the original size.
Potential reduce by 187.5 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. Eupago.pt needs all CSS files to be minified and compressed as it can save up to 187.5 kB or 89% of the original size.
Number of requests can be reduced by 15 (17%)
90
75
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eupago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eupago.pt
456 ms
css
71 ms
fontello.css
205 ms
foundation.css
710 ms
euPago.css
306 ms
slick.css
30 ms
modernizr.js
205 ms
jquery.js
509 ms
foundation.min.js
746 ms
foundation.topbar.js
211 ms
foundation.equalizer.js
237 ms
foundation.magellan.js
310 ms
foundation.slider.js
413 ms
foundation.reveal.js
440 ms
jquery.stellar.js
623 ms
slick.min.js
4 ms
scripts.js
591 ms
analytics.js
83 ms
eupago_mail.png
480 ms
head_mbps_logos.png
491 ms
head_mainBg.jpg
357 ms
logo.png
357 ms
head_mbps_logos.png
354 ms
bg_c.jpg
677 ms
head_icon_banco.png
355 ms
head_extrato.png
487 ms
logo_subnav.png
412 ms
bi_a01.png
488 ms
bi_a02.png
509 ms
bi_a03.png
515 ms
bi_a04.png
619 ms
bi_b04_bg.png
690 ms
bi_bLbracket.png
692 ms
bi_bRbracket.png
712 ms
bi_b01.png
718 ms
bi_b02_bg.png
818 ms
bi_b02.png
879 ms
bi_b03_bg.png
894 ms
bi_b03.png
896 ms
bi_b01_bg.png
915 ms
bi_b04.png
920 ms
bg_negocio_loja.jpg
1326 ms
bg_negocio_freelance.jpg
1387 ms
bg_negocio_donativos.jpg
1398 ms
bg_negocio_particulares.jpg
1402 ms
bi_c03.png
1118 ms
jump_seller.png
1124 ms
s4y.png
1321 ms
bg_d01.png
1327 ms
bi_blockArrow.png
1525 ms
bg_d02.png
1530 ms
bg_d03.png
1532 ms
bi_e01.png
1530 ms
bi_e02.png
1543 ms
UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf
58 ms
CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf
68 ms
-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf
93 ms
RJMlAoFXXQEzZoMSUteGWCZ2oysoEQEeKwjgmXLRnTc.ttf
120 ms
JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf
277 ms
PKCRbVvRfd5n7BTjtGiFZMDdSZkkecOE1hvV7ZHvhyU.ttf
120 ms
fontello.woff
1535 ms
collect
25 ms
bi_e03.png
1540 ms
ajax-loader.gif
125 ms
bi_e04.png
1385 ms
bi_e05.png
1386 ms
bi_e06.png
1444 ms
bg_l.jpg
1837 ms
sim_dwnArrow.png
1402 ms
sim_icoAquae.png
1451 ms
sim_icoTerra.png
1456 ms
arg_icon01.png
1435 ms
arg_icon02.png
1486 ms
arg_icon04.png
1398 ms
arg_icon05.png
1466 ms
cover_h.jpg
1557 ms
backoffice_icon01.png
1457 ms
backoffice_icon02.png
1493 ms
backoffice_icon03.png
1503 ms
backoffice_icon04.png
1528 ms
bg_b.jpg
1877 ms
dekas_home.png
1617 ms
modalbg_extrato.jpg
1729 ms
1.png
1713 ms
2.png
1631 ms
3.png
1938 ms
4.png
2096 ms
5.png
1635 ms
planos_ico-mini_ps.png
1503 ms
planos_ico-mini_mb.png
1504 ms
planos_ico-mini_mbway.png
1573 ms
desc_seg_icon01.png
1635 ms
desc_seg_icon02.png
1632 ms
desc_seg_icon03.png
1638 ms
desc_fluxograma.png
2039 ms
icon_top.png
1705 ms
logo_footer.png
1647 ms
eupago.pt 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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 IDs 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
eupago.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eupago.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
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eupago.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Eupago.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.
eupago.pt
Open Graph description is not detected on the main page of Eupago. 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: