1.4 sec in total
24 ms
933 ms
455 ms
Visit santandercards.com now to see the best up-to-date Santander Cards content and also check out these interesting facts you probably never knew about santandercards.com
Welcome to Santander. We offer current accounts, savings, mortgages, loans, credit cards and much more. Here to help you prosper
Visit santandercards.comWe analyzed Santandercards.com page load time and found that the first response time was 24 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
santandercards.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.9 s
3/100
25%
Value5.7 s
51/100
10%
Value1,070 ms
24/100
30%
Value0.013
100/100
15%
Value13.6 s
11/100
10%
24 ms
22 ms
16 ms
18 ms
18 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Santandercards.com, 3% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (456 ms) relates to the external source Santander.co.uk.
Page size can be reduced by 1.2 MB (47%)
2.7 MB
1.4 MB
In fact, the total size of Santandercards.com 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 72.4 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 72.4 kB or 82% of the original size.
Potential reduce by 111.5 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 Cards images are well optimized though.
Potential reduce by 649.1 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 649.1 kB or 73% of the original size.
Potential reduce by 412.8 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. Santandercards.com needs all CSS files to be minified and compressed as it can save up to 412.8 kB or 88% of the original size.
Number of requests can be reduced by 7 (23%)
31
24
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Santander Cards. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.santander.co.uk
24 ms
launch-ENed26431217ec4f129cc3055077309c86.min.js
22 ms
css_Ub3uIIbUqZiEuvJcKngiEhJxhQg7PpHZHNQY7QLVipc.css
16 ms
css_nbeMcQ8FRlZUHOmjr1JNfLaCFayzXzq2GCBkMLXZiUI.css
18 ms
image_masthead-099943300f80c4cd3f41c653f4b408c2.css
18 ms
strapline-b1b4b58634c5e85af1feac87870ba8a0.css
19 ms
js_ZtIPhmo8jyAs2xtsYaxCZaj69TmnFZ2CVVkUS510Uyo.js
49 ms
js_yVHIDZqbUjAIU4FA-QIjKtLuZykBK0JeBRzr802tf6s.js
84 ms
responsive_table-8de928067145d9cd6ae7bd897dbd505a.js
166 ms
js_EbZ2oCAKPdJOHJ_L9BeFgbVCC4t2wLxD3L1HBn433F4.js
48 ms
logo.svg
117 ms
home_page_hero_option_1.jpg
422 ms
switch-guarantee-white-logo.png
117 ms
gettyimages-764783223.jpg
456 ms
gettyimages-1456996763_0.jpg
455 ms
overall_service_quality_gb_pca_mc0597_3.jpg
118 ms
overall_service_quality_ni_pca_mc0597_4.jpg
117 ms
app_fraud_losses_that_were_reimbursed.png
119 ms
app_fraud_received_per_million_pounds_of_transactions.png
120 ms
app_fraud_sent_per_million_pounds_of_transactions.png
120 ms
app_fraud_received_per_million_pounds_of_transactions_major_banks.png
120 ms
mark-of-trust-kitemark-inclusive-service-financial-services-logo-en-gb-0222.jpg
120 ms
fscs-red.svg
124 ms
take-five.svg
121 ms
home_page_hero_option_1.jpg
18 ms
gettyimages-764783223.jpg
16 ms
gettyimages-1456996763_0.jpg
16 ms
gettyimages-1496166602.jpg
18 ms
overall_service_quality_gb_pca_mc0597_3.jpg
123 ms
overall_service_quality_ni_pca_mc0597_4.jpg
109 ms
app_fraud_losses_that_were_reimbursed.png
22 ms
app_fraud_received_per_million_pounds_of_transactions.png
25 ms
app_fraud_sent_per_million_pounds_of_transactions.png
30 ms
app_fraud_received_per_million_pounds_of_transactions_major_banks.png
37 ms
mark-of-trust-kitemark-inclusive-service-financial-services-logo-en-gb-0222.jpg
44 ms
SantanderText-Regular.woff
61 ms
web18.ttf
70 ms
SantanderHeadline-Rg.woff
83 ms
santandercards.com 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
santandercards.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
santandercards.com SEO score
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 Santandercards.com 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 Santandercards.com 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.
santandercards.com
Open Graph description is not detected on the main page of Santander Cards. 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: