Tools & Wizards About Us
app.rekentuin.nl screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

app.rekentuin.nl

Inloggen - rekentuin

Page Load Speed

3.2 sec in total

First Response

770 ms

Resources Loaded

2.2 sec

Page Rendered

156 ms

app.rekentuin.nl screenshot

About Website

Welcome to app.rekentuin.nl homepage info - get ready to check App Rekentuin best content for Netherlands right away, or after learning these important things about app.rekentuin.nl

Visit app.rekentuin.nl

Key Findings

We analyzed App.rekentuin.nl page load time and found that the first response time was 770 ms and then it took 2.4 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

app.rekentuin.nl performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

app.rekentuin.nl

770 ms

app.rekentuin.nl

436 ms

style.css

288 ms

mootools-yui-compressed.js

100 ms

mootools-more.js

65 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 50% of them (13 requests) were addressed to the original App.rekentuin.nl, 19% (5 requests) were made to Fonts.gstatic.com and 15% (4 requests) were made to D4huk2v4vqhib.cloudfront.net. The less responsive or slowest element that took the longest time to load (770 ms) belongs to the original domain App.rekentuin.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 747.1 kB (76%)

Content Size

987.8 kB

After Optimization

240.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of App.rekentuin.nl main page is 987.8 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. 20% of websites need less resources to load. CSS take 688.8 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 4.6 kB

  • Original 7.3 kB
  • After minification 7.2 kB
  • After compression 2.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 4.6 kB or 63% of the original size.

Image Optimization

-5%

Potential reduce by 6.1 kB

  • Original 122.7 kB
  • After minification 116.7 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. App Rekentuin images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 106.1 kB

  • Original 169.0 kB
  • After minification 166.3 kB
  • After compression 62.9 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 106.1 kB or 63% of the original size.

CSS Optimization

-92%

Potential reduce by 630.3 kB

  • Original 688.8 kB
  • After minification 584.0 kB
  • After compression 58.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. App.rekentuin.nl needs all CSS files to be minified and compressed as it can save up to 630.3 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (44%)

Requests Now

16

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

app.rekentuin.nl

app.rekentuin.nl

770 ms

app.rekentuin.nl

app.rekentuin.nl

436 ms

style.css

style.css

288 ms

mootools-yui-compressed.js

mootools-yui-compressed.js

100 ms

mootools-more.js

mootools-more.js

65 ms

Class.BindAll.js

Class.BindAll.js

68 ms

prevent_double_submit.js

prevent_double_submit.js

72 ms

font.css

font.css

91 ms

font.css

font.css

183 ms

css

css

67 ms

logo.png

logo.png

48 ms

logo.png

logo.png

106 ms

logo.png

logo.png

132 ms

logo.png

logo.png

181 ms

login_bg.jpg

login_bg.jpg

486 ms

login_icons_sprite.png

login_icons_sprite.png

251 ms

analytics.js

analytics.js

59 ms

signika-regular-webfont.woff

signika-regular-webfont.woff

281 ms

signika-bold-webfont.woff

signika-bold-webfont.woff

214 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

77 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

87 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

100 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

117 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

119 ms

entypo.woff

entypo.woff

398 ms

collect

collect

27 ms

Accessibility Review

app.rekentuin.nl accessibility score

63

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

app.rekentuin.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

SEO Factors

app.rekentuin.nl SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 App.rekentuin.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 App.rekentuin.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

app.rekentuin.nl

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