Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

roosen.nl

Placeholder – Antagonist

Page Load Speed

1.5 sec in total

First Response

296 ms

Resources Loaded

1.1 sec

Page Rendered

154 ms

roosen.nl screenshot

About Website

Visit roosen.nl now to see the best up-to-date Roosen content and also check out these interesting facts you probably never knew about roosen.nl

Visit roosen.nl

Key Findings

We analyzed Roosen.nl page load time and found that the first response time was 296 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

roosen.nl performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

roosen.nl

296 ms

bgnh.jpg

182 ms

logo.png

266 ms

white_rounded_corners_top.png

343 ms

white_rounded_corners_bottom.png

349 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original Roosen.nl, 89% (8 requests) were made to Antagonist.nl. The less responsive or slowest element that took the longest time to load (495 ms) relates to the external source Antagonist.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.1 kB (37%)

Content Size

62.2 kB

After Optimization

39.1 kB

In fact, the total size of Roosen.nl main page is 62.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 58.7 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 2.3 kB

  • Original 3.5 kB
  • After minification 3.2 kB
  • After compression 1.2 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 2.3 kB or 66% of the original size.

Image Optimization

-35%

Potential reduce by 20.8 kB

  • Original 58.7 kB
  • After minification 38.0 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, Roosen needs image optimization as it can save up to 20.8 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roosen. According to our analytics all requests are already optimized.

Accessibility Review

roosen.nl accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA IDs are not unique

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

roosen.nl best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roosen.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Roosen.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 Roosen. 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: