Tools & Wizards About Us

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

treasury.nl

Treasury.nl - Home

Page Load Speed

8.1 sec in total

First Response

1.2 sec

Resources Loaded

6.5 sec

Page Rendered

381 ms

About Website

Click here to check amazing Treasury content for India. Otherwise, check out these important facts you probably never knew about treasury.nl

Treasury specialist (semi) publieke- en zorgsector

Visit treasury.nl

Key Findings

We analyzed Treasury.nl page load time and found that the first response time was 1.2 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

treasury.nl performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.456

20/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.treasury.nl

1214 ms

cm8adam_1_call.js

44 ms

reset.css

176 ms

technology.css

176 ms

style.css

179 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 51% of them (58 requests) were addressed to the original Treasury.nl, 22% (25 requests) were made to Beursplaza.nl and 6% (7 requests) were made to Tools.investing.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Beursplaza.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 867.4 kB (52%)

Content Size

1.7 MB

After Optimization

795.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Treasury.nl main page is 1.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. 70% of websites need less resources to load. Javascripts take 706.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 37.6 kB

  • Original 47.9 kB
  • After minification 45.5 kB
  • After compression 10.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 37.6 kB or 78% of the original size.

Image Optimization

-17%

Potential reduce by 103.0 kB

  • Original 589.5 kB
  • After minification 486.6 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. Obviously, Treasury needs image optimization as it can save up to 103.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 466.5 kB

  • Original 706.5 kB
  • After minification 670.7 kB
  • After compression 240.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 466.5 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 260.4 kB

  • Original 318.7 kB
  • After minification 303.0 kB
  • After compression 58.3 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. Treasury.nl needs all CSS files to be minified and compressed as it can save up to 260.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (69%)

Requests Now

108

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

treasury.nl accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

treasury.nl 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

High

Page has valid source maps

SEO Factors

treasury.nl SEO score

89

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 Treasury.nl 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 Treasury.nl 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 Treasury. 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: