Tools & Wizards About Us
hallo.saxo screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

hallo.saxo

Voormalig Binck-klant – Saxo Bank België Support

Page Load Speed

3.3 sec in total

First Response

696 ms

Resources Loaded

2.2 sec

Page Rendered

334 ms

hallo.saxo screenshot

About Website

Click here to check amazing Hallo content. Otherwise, check out these important facts you probably never knew about hallo.saxo

Visit hallo.saxo

Key Findings

We analyzed Hallo.saxo page load time and found that the first response time was 696 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

hallo.saxo performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

360010928132-Voormalig-Binck-klant

696 ms

application-1a1175db35230dfa282e711364a74c60.css

77 ms

theming_v1_support-e05586b61178dcde2a13a3d323525a18.css

111 ms

style.css

331 ms

jquery-09d07e20ce042ef10e301661ad1f316c.js

157 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 Hallo.saxo, 18% (7 requests) were made to Theme.zdassets.com and 13% (5 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Theme.zdassets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 618.2 kB (77%)

Content Size

807.0 kB

After Optimization

188.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hallo.saxo main page is 807.0 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. 55% of websites need less resources to load. HTML takes 415.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 372.0 kB

  • Original 415.7 kB
  • After minification 398.2 kB
  • After compression 43.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 372.0 kB or 89% of the original size.

JavaScript Optimization

-65%

Potential reduce by 246.1 kB

  • Original 380.7 kB
  • After minification 380.6 kB
  • After compression 134.6 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 246.1 kB or 65% of the original size.

CSS Optimization

-0%

Potential reduce by 34 B

  • Original 10.6 kB
  • After minification 10.6 kB
  • After compression 10.5 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. Hallo.saxo has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (53%)

Requests Now

30

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hallo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

360010928132-Voormalig-Binck-klant

360010928132-Voormalig-Binck-klant

696 ms

application-1a1175db35230dfa282e711364a74c60.css

application-1a1175db35230dfa282e711364a74c60.css

77 ms

theming_v1_support-e05586b61178dcde2a13a3d323525a18.css

theming_v1_support-e05586b61178dcde2a13a3d323525a18.css

111 ms

style.css

style.css

331 ms

jquery-09d07e20ce042ef10e301661ad1f316c.js

jquery-09d07e20ce042ef10e301661ad1f316c.js

157 ms

uc.js

uc.js

191 ms

launch-EN6d8e04357a1a42939abae23550df0d58.min.js

launch-EN6d8e04357a1a42939abae23550df0d58.min.js

248 ms

script.js

script.js

279 ms

cd.js

cd.js

282 ms

nl-be.3b1672c8f4aa43cb729d.js

nl-be.3b1672c8f4aa43cb729d.js

145 ms

host.js

host.js

206 ms

moment-4ef0d82f9fc65c8a28f659aa3430955f.js

moment-4ef0d82f9fc65c8a28f659aa3430955f.js

150 ms

hc_enduser-fa9d5f0230d7f7607be4864945d52382.js

hc_enduser-fa9d5f0230d7f7607be4864945d52382.js

188 ms

host.js

host.js

13 ms

analytics.js

analytics.js

358 ms

cc.js

cc.js

449 ms

AppMeasurement.min.js

AppMeasurement.min.js

241 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

298 ms

AppMeasurement_Module_AudienceManagement.min.js

AppMeasurement_Module_AudienceManagement.min.js

316 ms

6bb51478ddc0ceccaae1cc8bfbc92ca815fe4af5.svg

6bb51478ddc0ceccaae1cc8bfbc92ca815fe4af5.svg

304 ms

47da91f42cbac2aa7ce60687a11fd676aad33070.svg

47da91f42cbac2aa7ce60687a11fd676aad33070.svg

711 ms

2be6bd7c4f7756e53a5e21e5cec010856e6ef7c7.png

2be6bd7c4f7756e53a5e21e5cec010856e6ef7c7.png

536 ms

sections.json

sections.json

578 ms

invisible.js

invisible.js

209 ms

bc-v4.min.html

bc-v4.min.html

173 ms

465ebf1db6462930b7f4441e0cc06b733becc10b.woff

465ebf1db6462930b7f4441e0cc06b733becc10b.woff

588 ms

c0d0478dc16d58a02f169198d862e684a2b591eb.woff

c0d0478dc16d58a02f169198d862e684a2b591eb.woff

408 ms

f6808e7c0e47ba8767912f4ae8846c1b7b4777b5.woff

f6808e7c0e47ba8767912f4ae8846c1b7b4777b5.woff

587 ms

991c74f36c41082dc72ca21d1ca5e108406102c3.woff

991c74f36c41082dc72ca21d1ca5e108406102c3.woff

589 ms

entypo-7d43a0426efc4765aa933c6fc586ee58..svg

entypo-7d43a0426efc4765aa933c6fc586ee58..svg

79 ms

entypo-cd0cc640c9711149dc484d7c26584704..woff

entypo-cd0cc640c9711149dc484d7c26584704..woff

77 ms

copenhagen-icons-268fb7c014de8a06d7d40310b5000daa..woff

copenhagen-icons-268fb7c014de8a06d7d40310b5000daa..woff

78 ms

cdreport.js

cdreport.js

386 ms

collect

collect

87 ms

json

json

113 ms

collect

collect

78 ms

75b0ff55687b6faa

75b0ff55687b6faa

231 ms

RCa1dfbd0fb4e84cecbb332c03c2714513-source.min.js

RCa1dfbd0fb4e84cecbb332c03c2714513-source.min.js

37 ms

Accessibility Review

hallo.saxo accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

hallo.saxo best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hallo.saxo SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hallo.saxo can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Hallo.saxo 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

hallo.saxo

Open Graph description is not detected on the main page of Hallo. 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: