4.7 sec in total
328 ms
4.2 sec
194 ms
Welcome to crs.hsbc.com homepage info - get ready to check CRS HSBC best content for United States right away, or after learning these important things about crs.hsbc.com
HSBC will be one of the fully CRS compliant banks in the world – learn more about CRS and how this will affect your personal or business account with HSBC
Visit crs.hsbc.comWe analyzed Crs.hsbc.com page load time and found that the first response time was 328 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
crs.hsbc.com performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value3.7 s
58/100
25%
Value7.6 s
25/100
10%
Value100 ms
98/100
30%
Value0.031
100/100
15%
Value10.8 s
22/100
10%
328 ms
1401 ms
399 ms
190 ms
396 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 95% of them (36 requests) were addressed to the original Crs.hsbc.com, 5% (2 requests) were made to Www1.member-hsbc-group.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Crs.hsbc.com.
Page size can be reduced by 403.4 kB (46%)
876.4 kB
473.0 kB
In fact, the total size of Crs.hsbc.com main page is 876.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 372.1 kB which makes up the majority of the site volume.
Potential reduce by 201.3 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 201.3 kB or 89% of the original size.
Potential reduce by 87 B
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. CRS HSBC images are well optimized though.
Potential reduce by 202.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 202.1 kB or 72% of the original size.
Number of requests can be reduced by 28 (78%)
36
8
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CRS HSBC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
crs.hsbc.com
328 ms
www.crs.hsbc.com
1401 ms
common
399 ms
desktop
190 ms
wt_top_section.js
396 ms
wt_bottom_section.js
439 ms
dojo.js
732 ms
bg_arrow.png
309 ms
hsbc-logo.png
191 ms
section_divider.png
173 ms
shadow.png
173 ms
heading-05.jpg
480 ms
icons.png
410 ms
selected.png
411 ms
arrow.png
412 ms
divider.png
475 ms
cookie_icon.png
513 ms
cookie_close.png
518 ms
back.png
561 ms
icons_dark.png
650 ms
pdf.png
899 ms
red_chevron.png
644 ms
red_external_site.png
691 ms
red_new_window.png
696 ms
webtrends.js
1004 ms
DoormatController.js
444 ms
navigation.png
416 ms
selected_device.png
493 ms
arrow_device.png
494 ms
red_pdf_download_device.png
586 ms
red_chevron_device.png
609 ms
red_external_site_device.png
632 ms
red_new_window_device.png
890 ms
wtid.js
339 ms
tablet
187 ms
mobile
403 ms
dcs.gif
137 ms
182 ms
crs.hsbc.com accessibility score
crs.hsbc.com 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
Browser errors were logged to the console
crs.hsbc.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Crs.hsbc.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 Crs.hsbc.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.
crs.hsbc.com
Open Graph description is not detected on the main page of CRS HSBC. 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: