7.9 sec in total
211 ms
5.4 sec
2.3 sec
Click here to check amazing Santander content. Otherwise, check out these important facts you probably never knew about santander.us
Apply for a bank account online with Santander Bank. Enjoy convenient online bank account options from one of the best personal banks.
Visit santander.usWe analyzed Santander.us page load time and found that the first response time was 211 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
santander.us performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value47.5 s
0/100
25%
Value44.0 s
0/100
10%
Value52,630 ms
0/100
30%
Value0.935
3/100
15%
Value77.6 s
0/100
10%
211 ms
590 ms
266 ms
294 ms
359 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Santander.us, 79% (57 requests) were made to Santanderbank.com and 7% (5 requests) were made to Fecdn.user1st.info. The less responsive or slowest element that took the longest time to load (590 ms) relates to the external source Santanderbank.com.
Page size can be reduced by 574.3 kB (19%)
2.9 MB
2.4 MB
In fact, the total size of Santander.us main page is 2.9 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. Only a small number of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 217.7 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 217.7 kB or 58% of the original size.
Potential reduce by 230.7 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. Santander images are well optimized though.
Potential reduce by 123.8 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 123.8 kB or 52% of the original size.
Potential reduce by 2.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. Santander.us needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 14% of the original size.
Number of requests can be reduced by 34 (52%)
65
31
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Santander. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
santander.us
211 ms
www.santanderbank.com
590 ms
head
266 ms
utag.sync.js
294 ms
utag.js
359 ms
main.css
106 ms
combo
256 ms
clay.css
253 ms
main.css
217 ms
combo
258 ms
js_loader_config
172 ms
combo
258 ms
combo
344 ms
combo
311 ms
js_bundle_config
284 ms
combo
354 ms
main.css
302 ms
combo
289 ms
9aa9d696-ba1c-00d5-71e1-a36ba5d1a18a
306 ms
3d462475
341 ms
bootstrap-icons.css
282 ms
all.css
353 ms
bootstrap-icons.css
251 ms
main.css
292 ms
main.css
298 ms
main.css
296 ms
main.css
297 ms
main.css
306 ms
staging.js
314 ms
staging_branch.js
316 ms
staging_version.js
310 ms
main.js
310 ms
jquery.mask.min.js
310 ms
P00cXWMB
348 ms
Activation
17 ms
8467205636.js
164 ms
ActivationFrameScripts
31 ms
Loader
21 ms
ca903dab-71ae-9b33-0bab-05c7d754b18f
33 ms
a8467205636.html
149 ms
Circle-Button.svg
210 ms
dee6c307-621d-e651-7fc7-f6ced336e07d
149 ms
c818a34f-9b69-0d88-45dd-f88d22050afe
145 ms
4d1f35d2-f3ff-50b3-fe86-6ff4f4f66e6e
205 ms
cce1b548-7655-91de-1778-6441d6dd7e64
146 ms
744ff8eb-51d7-0fed-e778-91755fa6e06a
142 ms
7901105a-eac7-54d6-f1fd-35506dd4511e
147 ms
362fe2ec-ed94-f817-de0b-aecd81b7fe25
155 ms
abf5268d-03d5-b77d-ea07-f1fe92122388
148 ms
e71f724e-40b9-f7ce-a039-b8d6cb0353f8
151 ms
a83e9e43-8a78-ea8f-9081-9a8b509a74ee
151 ms
d0dd0283-a3b8-d339-35c3-d2a206759ff6
185 ms
948d5515-ae62-4bed-9d80-cecdce9f03b7
188 ms
1eb29031-5e2e-11cc-47d0-75367e8304b2
186 ms
fda3a219-d71c-23ab-204e-53806d0c4c48
192 ms
Scan-QR-code-to-open-app.png
245 ms
6f5cd00c-ceb1-6f70-eada-e97b1b9c0bb2
196 ms
d6465554-467e-ef72-6ada-7f81472a54e5
227 ms
83c351ca-3072-6c0a-715c-1862dc83631b
216 ms
28a89158-2191-3eac-eec3-42f28731cd38
211 ms
b4d47b7b-98fd-1166-2a15-8eff2a1d7927
212 ms
74e0dbb5-9859-7c4c-71df-f8cd100b1322
219 ms
9ee8c3d2-2d0d-355b-7e14-5bcc0af1ffbd
218 ms
bd9cbe6b-0568-09f1-1280-eeb7e47cad6b
219 ms
a383ba71-d53c-04bd-addf-e233278a2664
237 ms
SantanderTextW05-Regular.eot
238 ms
SantanderHeadlineW05-Light.woff
66 ms
SantanderTextW05-Regular.woff
68 ms
0cb05de0-aa5a-811b-8871-ceec8c50613a
41 ms
bootstrap-icons.woff
16 ms
bootstrap-icons.woff
85 ms
Init
225 ms
santander.us 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
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
santander.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
santander.us 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 Santander.us 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 Santander.us 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.
santander.us
Open Graph description is not detected on the main page of Santander. 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: