5.1 sec in total
1.3 sec
3.7 sec
114 ms
Welcome to cam.es homepage info - get ready to check Cam best content right away, or after learning these important things about cam.es
Accedeix a serveis i productes financers: comptes, targetes, hipoteques, préstecs, fons d'inversió, plans de pensions i assegurances. Banc Sabadell.
Visit cam.esWe analyzed Cam.es page load time and found that the first response time was 1.3 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
cam.es performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value20.3 s
0/100
25%
Value21.6 s
0/100
10%
Value19,690 ms
0/100
30%
Value0.167
71/100
15%
Value29.7 s
0/100
10%
1319 ms
237 ms
537 ms
600 ms
345 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Cam.es, 8% (5 requests) were made to Emstatics.bancsabadell.com and 5% (3 requests) were made to Datalog.bancsabadell.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Bancsabadell.com.
Page size can be reduced by 903.8 kB (74%)
1.2 MB
318.3 kB
In fact, the total size of Cam.es main page is 1.2 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. 30% of websites need less resources to load. Javascripts take 873.7 kB which makes up the majority of the site volume.
Potential reduce by 114.1 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 114.1 kB or 80% of the original size.
Potential reduce by 2.6 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, Cam needs image optimization as it can save up to 2.6 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 628.5 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 628.5 kB or 72% of the original size.
Potential reduce by 158.7 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. Cam.es needs all CSS files to be minified and compressed as it can save up to 158.7 kB or 82% of the original size.
Number of requests can be reduced by 40 (65%)
62
22
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
1319 ms
styles.css
237 ms
site-styles.css
537 ms
commons.js
600 ms
sloth_inc.js
345 ms
checkHref.js
347 ms
comun_presentacion.js
357 ms
jquery-latest.js
727 ms
utils_mktg_SA.js
467 ms
new-header-styles.css
459 ms
acceso_bsol_part_detalle.js
372 ms
AC_OETags.js
467 ms
fp_AA.js
585 ms
styler.js
464 ms
htmlvalidater.js
559 ms
LwC.js
533 ms
informacion.png
118 ms
flechitaObs.png
112 ms
x-negra.png
122 ms
icon-alert.gif
119 ms
overlay.png
120 ms
utag.js
67 ms
dc.js
102 ms
down.png
140 ms
lupa_t.png
195 ms
lupa.png
196 ms
logoBancSabadell.png
207 ms
lock_blue.png
204 ms
salir.png
206 ms
botonCambio.gif
242 ms
alert.png
294 ms
close2.gif
288 ms
1p.gif
304 ms
bkgBSOnline.gif
305 ms
candado.gif
311 ms
ayuda.gif
338 ms
li-triangulo-gris.gif
383 ms
botonRedondo.gif
388 ms
padlock-sec.gif
395 ms
bca-dist-ico.png
398 ms
Hagasecliente_en.gif
407 ms
Fons_Modul.gif
427 ms
li-triangulo-azul.gif
473 ms
moreInfo.gif
488 ms
CR_XarxesSocials_Blog_12092.gif
499 ms
FACE.gif
500 ms
CR_XarxesSocials_Twitter_120925.gif
517 ms
googleplussmall.gif
539 ms
CR_XarxesSocials_Linkedin_120925.gif
580 ms
yt.gif
606 ms
Norma07.gif
611 ms
ExcelenciaEuropea.gif
612 ms
FinanzasParaTodos.gif
637 ms
escribeaci.js
638 ms
zBkvZ
93 ms
zBkvZ
90 ms
new-header-print.css
119 ms
sloth1.3.8.f788d9e.js
361 ms
3MH0.html
98 ms
194 ms
PfiE.html
83 ms
startseitep=plloydsbank
143 ms
160 ms
cam.es 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Links do not have a discernible name
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>).
cam.es 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
Missing source maps for large first-party JavaScript
cam.es 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cam.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cam.es 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.
cam.es
Open Graph description is not detected on the main page of Cam. 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: