Tools & Wizards About Us
peepl.be screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

peepl.be

Peepl - membership management and communication in one online tool

Page Load Speed

3.6 sec in total

First Response

416 ms

Resources Loaded

2.5 sec

Page Rendered

692 ms

peepl.be screenshot

About Website

Visit peepl.be now to see the best up-to-date Peepl content for Belgium and also check out these interesting facts you probably never knew about peepl.be

With Peepl you can manage your members directory, calendar, communication, finances and much more with an easy-to-use online tool.

Visit peepl.be

Key Findings

We analyzed Peepl.be page load time and found that the first response time was 416 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

peepl.be performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

peepl.be

416 ms

224 ms

bootstrap.min.css

89 ms

swiper.min.css

177 ms

font-awesome.min.css

264 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Peepl.be, 70% (48 requests) were made to Peepl.io and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (998 ms) relates to the external source Peepl.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 715.9 kB (29%)

Content Size

2.4 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peepl.be main page is 2.4 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 91.7 kB

  • Original 113.9 kB
  • After minification 101.0 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 11% 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 91.7 kB or 80% of the original size.

Image Optimization

-24%

Potential reduce by 448.6 kB

  • Original 1.9 MB
  • After minification 1.5 MB

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, Peepl needs image optimization as it can save up to 448.6 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 71 B

  • Original 187.7 kB
  • After minification 187.7 kB
  • After compression 187.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-76%

Potential reduce by 175.5 kB

  • Original 229.5 kB
  • After minification 195.1 kB
  • After compression 54.0 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. Peepl.be needs all CSS files to be minified and compressed as it can save up to 175.5 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (41%)

Requests Now

61

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peepl.be

peepl.be

416 ms

224 ms

bootstrap.min.css

bootstrap.min.css

89 ms

swiper.min.css

swiper.min.css

177 ms

font-awesome.min.css

font-awesome.min.css

264 ms

magnific-popup.min.css

magnific-popup.min.css

262 ms

base.min.css

base.min.css

266 ms

css

css

45 ms

css

css

64 ms

jquery.min.js

jquery.min.js

32 ms

jquery.min.js

jquery.min.js

424 ms

bootstrap.js

bootstrap.js

434 ms

html5shiv.js

html5shiv.js

408 ms

jquery.carouFredSel.js

jquery.carouFredSel.js

491 ms

jquery.cloud9carousel.js

jquery.cloud9carousel.js

432 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

431 ms

jquery.waterwheelCarousel.js

jquery.waterwheelCarousel.js

437 ms

svg4everybody.min.js

svg4everybody.min.js

543 ms

swiper.min.js

swiper.min.js

620 ms

app.new.min.js

app.new.min.js

542 ms

ca78c4636f75440f90a3bbd8645cd008.js.ubembed.com

ca78c4636f75440f90a3bbd8645cd008.js.ubembed.com

201 ms

9e170d867f0d9ed6a49bda9899163d69aabd00f4.js

9e170d867f0d9ed6a49bda9899163d69aabd00f4.js

93 ms

analytics.js

analytics.js

166 ms

fbevents.js

fbevents.js

164 ms

email_confirm.png

email_confirm.png

281 ms

btn-arrow-icon.svg

btn-arrow-icon.svg

215 ms

thankyou.png

thankyou.png

353 ms

peepl_logo.svg

peepl_logo.svg

294 ms

international_flag_icon.svg

international_flag_icon.svg

325 ms

belgium_flag_icon.svg

belgium_flag_icon.svg

327 ms

netherlands_flag_icon.svg

netherlands_flag_icon.svg

373 ms

header.jpg

header.jpg

823 ms

bg_ovals.svg

bg_ovals.svg

387 ms

studio100.png

studio100.png

382 ms

tejo.png

tejo.png

386 ms

biv.png

biv.png

425 ms

febelsafe.png

febelsafe.png

463 ms

teleonthaal.png

teleonthaal.png

471 ms

netwerkondernemen.png

netwerkondernemen.png

477 ms

rti.png

rti.png

477 ms

lions.png

lions.png

509 ms

jci.png

jci.png

553 ms

kfcmoerkerke.png

kfcmoerkerke.png

564 ms

tejo.png

tejo.png

745 ms

rtknokke.png

rtknokke.png

748 ms

rtknokke.png

rtknokke.png

679 ms

biv.png

biv.png

823 ms

teleonthaal.png

teleonthaal.png

998 ms

kfcmarke.png

kfcmarke.png

849 ms

kfcmarke.png

kfcmarke.png

844 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd5a7dvg.ttf

80 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvg.ttf

110 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvg.ttf

125 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvg.ttf

125 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvg.ttf

126 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvg.ttf

126 ms

big_arrow_right.svg

big_arrow_right.svg

747 ms

big_arrow_left.svg

big_arrow_left.svg

806 ms

big_arrow_up.svg

big_arrow_up.svg

811 ms

big_arrow_4.svg

big_arrow_4.svg

820 ms

big_arrow_5.svg

big_arrow_5.svg

826 ms

guided_demo.jpg

guided_demo.jpg

885 ms

collect

collect

53 ms

js

js

112 ms

insight.min.js

insight.min.js

50 ms

bundle.js

bundle.js

37 ms

modules-v2.js

modules-v2.js

53 ms

insight_tag_errors.gif

insight_tag_errors.gif

63 ms

i8ewlxrg

i8ewlxrg

59 ms

Accessibility Review

peepl.be accessibility score

82

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

High

Links do not have a discernible name

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

peepl.be 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

High

Page has valid source maps

SEO Factors

peepl.be SEO score

81

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

peepl.be

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