Tools & Wizards About Us
requiem.nl screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

requiem.nl

Welkom op de website van Uitvaart Coöperatie - Uitvaart Coöperatie

Page Load Speed

3.6 sec in total

First Response

867 ms

Resources Loaded

2.6 sec

Page Rendered

163 ms

requiem.nl screenshot

About Website

Welcome to requiem.nl homepage info - get ready to check Requiem best content right away, or after learning these important things about requiem.nl

Uitvaart verzorgen? Bij Uitvaart coöperatie staat een goed team voor u klaar met een landelijk netwerk aan uitvaartondernemers.  ✅ Persoonlijke aandacht

Visit requiem.nl

Key Findings

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

Performance Metrics

requiem.nl performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.459

19/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

www.requiem.nl

867 ms

wp-emoji-release.min.js

104 ms

reset.css

202 ms

font-awesome.css

203 ms

style.css

205 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 27% of them (12 requests) were addressed to the original Requiem.nl, 43% (19 requests) were made to Maps.googleapis.com and 18% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (867 ms) belongs to the original domain Requiem.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 470.7 kB (54%)

Content Size

867.4 kB

After Optimization

396.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 23.8 kB

  • Original 29.7 kB
  • After minification 29.2 kB
  • After compression 5.9 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 23.8 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 8.2 kB

  • Original 119.0 kB
  • After minification 110.8 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. Requiem images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 407.1 kB

  • Original 679.3 kB
  • After minification 663.2 kB
  • After compression 272.3 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 407.1 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 31.7 kB

  • Original 39.4 kB
  • After minification 30.9 kB
  • After compression 7.7 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. Requiem.nl needs all CSS files to be minified and compressed as it can save up to 31.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (46%)

Requests Now

39

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.requiem.nl

www.requiem.nl

867 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

104 ms

reset.css

reset.css

202 ms

font-awesome.css

font-awesome.css

203 ms

style.css

style.css

205 ms

media-queries.css

media-queries.css

206 ms

jquery.js

jquery.js

309 ms

js

js

61 ms

infobox.js

infobox.js

488 ms

common.js

common.js

300 ms

wp-embed.min.js

wp-embed.min.js

300 ms

logo-requiem.jpg

logo-requiem.jpg

117 ms

loader.gif

loader.gif

117 ms

common.js

common.js

7 ms

map.js

map.js

20 ms

util.js

util.js

18 ms

onion.js

onion.js

40 ms

openhand_8_8.cur

openhand_8_8.cur

69 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

99 ms

stats.js

stats.js

18 ms

controls.js

controls.js

12 ms

css

css

97 ms

transparent.png

transparent.png

23 ms

google4.png

google4.png

15 ms

mapcnt6.png

mapcnt6.png

40 ms

sv5.png

sv5.png

40 ms

tmapctrl.png

tmapctrl.png

52 ms

tmapctrl4.png

tmapctrl4.png

55 ms

google_white5.png

google_white5.png

55 ms

vt

vt

43 ms

vt

vt

37 ms

vt

vt

34 ms

vt

vt

65 ms

vt

vt

72 ms

vt

vt

70 ms

vt

vt

49 ms

vt

vt

48 ms

vt

vt

68 ms

vt

vt

80 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

24 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

27 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

35 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

39 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

264 ms

Accessibility Review

requiem.nl accessibility score

90

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

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

requiem.nl best practices score

75

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

SEO Factors

requiem.nl SEO score

92

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 Requiem.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 Requiem.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

requiem.nl

Open Graph data is detected on the main page of Requiem. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: