Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 92

    SEO

    Google-friendlier than
    79% of websites

santander.be

Santander

Page Load Speed

2.9 sec in total

First Response

321 ms

Resources Loaded

2.5 sec

Page Rendered

152 ms

santander.be screenshot

About Website

Click here to check amazing Santander content for Belgium. Otherwise, check out these important facts you probably never knew about santander.be

Op zoek naar een persoonlijke lening op afbetaling of een permanente geldreserve? Bij Santander leent u steeds verantwoord en aan het beste tarief!

Visit santander.be

Key Findings

We analyzed Santander.be page load time and found that the first response time was 321 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

santander.be performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

santander.be

321 ms

www.santander.be

979 ms

index.css

90 ms

jquery-1.5.2.min.js

429 ms

jquery.cookie.js

340 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 83% of them (15 requests) were addressed to the original Santander.be, 11% (2 requests) were made to Ssl.google-analytics.com and 6% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (979 ms) belongs to the original domain Santander.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.3 kB (10%)

Content Size

714.2 kB

After Optimization

640.0 kB

In fact, the total size of Santander.be main page is 714.2 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. Only 10% of websites need less resources to load. Images take 598.7 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 1.9 kB

  • Original 3.2 kB
  • After minification 3.0 kB
  • After compression 1.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 1.9 kB or 60% of the original size.

Image Optimization

-2%

Potential reduce by 10.1 kB

  • Original 598.7 kB
  • After minification 588.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 images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 59.0 kB

  • Original 108.4 kB
  • After minification 107.1 kB
  • After compression 49.4 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 59.0 kB or 54% of the original size.

CSS Optimization

-82%

Potential reduce by 3.2 kB

  • Original 3.9 kB
  • After minification 3.0 kB
  • After compression 719 B

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.be needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

The browser has sent 15 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 4 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

santander.be accessibility score

65

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

santander.be best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

santander.be SEO score

92

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santander.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Santander.be 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.

Social Sharing Optimization

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: