Access vredenburg.nl. Welkom bij TivoliVredenburg in Utrecht

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value16,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value34.0 s

0/100

10%

vredenburg.nl

269 ms

www.tivolivredenburg.nl

466 ms

130 ms

1615 ms

main.scss

230 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vredenburg.nl, 27% (21 requests) were made to Tivolivredenburg.nl and 20% (16 requests) were made to Cdns-files.dzcdn.net. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Tivolivredenburg.nl.

Content Size

3.0 MB

After Optimization

1.3 MB

In fact, the total size of Vredenburg.nl main page is 3.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 115.1 kB

Original 127.7 kB
After minification 86.6 kB
After compression 12.6 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. This page needs HTML code to be minified as it can gain 41.1 kB, which is 32% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 115.1 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 7.4 kB

Original 216.6 kB
After minification 209.2 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. Vredenburg images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 1.3 MB

Original 2.3 MB
After minification 2.3 MB
After compression 1.0 MB

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 1.3 MB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 324.3 kB

Original 385.9 kB
After minification 363.2 kB
After compression 61.6 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. Vredenburg.nl needs all CSS files to be minified and compressed as it can save up to 324.3 kB or 84% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

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 Vredenburg.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 Vredenburg.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 Vredenburg. 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: