Tools & Wizards About Us
pleio.nl screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

pleio.nl

Laagdrempelig samenwerken - met Pleio kan het

Page Load Speed

4.8 sec in total

First Response

476 ms

Resources Loaded

4 sec

Page Rendered

319 ms

pleio.nl screenshot

About Website

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

Online samenwerken binnen en over de grenzen van je organisatie. Pleio maakt het mogelijk. Binnen acht uur staat je platform live

Visit pleio.nl

Key Findings

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

Performance Metrics

pleio.nl performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value20.0 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.209

59/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

pleio.nl

476 ms

www.pleio.nl

1330 ms

lightbox.1458311169.css

251 ms

elgg.1458311169.css

631 ms

jquery-1.6.4.min.js

507 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 63% of them (22 requests) were addressed to the original Pleio.nl, 11% (4 requests) were made to F.vimeocdn.com and 9% (3 requests) were made to Integralevroeghulp.pleio.nl. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Pleio.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 731.8 kB (68%)

Content Size

1.1 MB

After Optimization

346.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 18.4 kB

  • Original 23.7 kB
  • After minification 23.3 kB
  • After compression 5.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 18.4 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 14.3 kB

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

JavaScript Optimization

-69%

Potential reduce by 481.3 kB

  • Original 693.7 kB
  • After minification 693.2 kB
  • After compression 212.4 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 481.3 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 217.8 kB

  • Original 250.6 kB
  • After minification 223.6 kB
  • After compression 32.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. Pleio.nl needs all CSS files to be minified and compressed as it can save up to 217.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (48%)

Requests Now

33

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pleio.nl

pleio.nl

476 ms

www.pleio.nl

www.pleio.nl

1330 ms

lightbox.1458311169.css

lightbox.1458311169.css

251 ms

elgg.1458311169.css

elgg.1458311169.css

631 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

507 ms

jquery-ui-1.8.16.min.js

jquery-ui-1.8.16.min.js

683 ms

elgg.1458311169.js

elgg.1458311169.js

699 ms

lightbox.1458311169.js

lightbox.1458311169.js

463 ms

languages

languages

586 ms

piwik.js

piwik.js

962 ms

login.png

login.png

1060 ms

login.png

login.png

1141 ms

login.png

login.png

1226 ms

background.png

background.png

111 ms

logo_normal.png

logo_normal.png

106 ms

en.gif

en.gif

105 ms

nl.gif

nl.gif

107 ms

login.png

login.png

109 ms

login.png

login.png

225 ms

login.png

login.png

224 ms

11098762

11098762

480 ms

thumbnail.php

thumbnail.php

499 ms

thumbnail.php

thumbnail.php

667 ms

7135762

7135762

711 ms

121168476

121168476

73 ms

elgg_sprites.png

elgg_sprites.png

383 ms

ajax_loader_bw.gif

ajax_loader_bw.gif

570 ms

player.js

player.js

187 ms

player.css

player.css

157 ms

ga.js

ga.js

62 ms

vuid.min.js

vuid.min.js

184 ms

__utm.gif

__utm.gif

50 ms

proxy.html

proxy.html

65 ms

509263465.jpg

509263465.jpg

165 ms

9442265_60x60.jpg

9442265_60x60.jpg

109 ms

Accessibility Review

pleio.nl accessibility score

98

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

[aria-hidden="true"] elements contain focusable descendents

Best Practices

pleio.nl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pleio.nl SEO score

98

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pleio.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Pleio.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

pleio.nl

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