Tools & Wizards About Us
wecanhelp.de screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

wecanhelp.de

WeCanHelp.de - Mach aus Deinem Einkauf eine gute Tat

Page Load Speed

6.1 sec in total

First Response

332 ms

Resources Loaded

5.6 sec

Page Rendered

164 ms

wecanhelp.de screenshot

About Website

Click here to check amazing We Can Help content for Germany. Otherwise, check out these important facts you probably never knew about wecanhelp.de

Auf WeCanHelp.de kannst Du 13.812 Einrichtungen und Projektgruppen mit Deinen Einkäufen bei 33.316 Shops ohne Mehrkosten unterstützen. Insgesamt wurden schon über 13,51 Mio. € gesammelt.

Visit wecanhelp.de

Key Findings

We analyzed Wecanhelp.de page load time and found that the first response time was 332 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wecanhelp.de performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

wecanhelp.de

332 ms

www.wecanhelp.de

1743 ms

bootstrap.css

240 ms

style.css

415 ms

jquery-ui.css

332 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 47% of them (48 requests) were addressed to the original Wecanhelp.de, 18% (19 requests) were made to B.tile.openstreetmap.de and 17% (18 requests) were made to C.tile.openstreetmap.de. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Wecanhelp.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.0 kB (6%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wecanhelp.de main page is 1.5 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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 55.5 kB

  • Original 71.1 kB
  • After minification 69.1 kB
  • After compression 15.6 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 55.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 2.7 kB

  • Original 1.0 MB
  • After minification 1.0 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. We Can Help images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 28.6 kB

  • Original 369.2 kB
  • After minification 369.2 kB
  • After compression 340.6 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

-13%

Potential reduce by 10.2 kB

  • Original 79.5 kB
  • After minification 79.5 kB
  • After compression 69.3 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. Wecanhelp.de needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (56%)

Requests Now

70

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Can Help. 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 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wecanhelp.de

wecanhelp.de

332 ms

www.wecanhelp.de

www.wecanhelp.de

1743 ms

bootstrap.css

bootstrap.css

240 ms

style.css

style.css

415 ms

jquery-ui.css

jquery-ui.css

332 ms

footer_menu.css

footer_menu.css

466 ms

jquery.2.0.3.min.js

jquery.2.0.3.min.js

585 ms

jquery-ui-1.10.4.custom.min.js

jquery-ui-1.10.4.custom.min.js

377 ms

jquery.cookie.js

jquery.cookie.js

432 ms

jquery.clearable.js

jquery.clearable.js

464 ms

jquery.clearable.css

jquery.clearable.css

511 ms

selectboxit.min.js

selectboxit.min.js

544 ms

selectboxit.css

selectboxit.css

553 ms

jquery.placeholder.js

jquery.placeholder.js

601 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

605 ms

magnific-popup.css

magnific-popup.css

642 ms

byme.css

byme.css

688 ms

tipuedrop.css

tipuedrop.css

681 ms

tipuedrop.js

tipuedrop.js

707 ms

jquery_jtruncate.js

jquery_jtruncate.js

703 ms

util_bs3.js

util_bs3.js

741 ms

bootstrap.min.js

bootstrap.min.js

790 ms

yamm.css

yamm.css

797 ms

all.css

all.css

839 ms

v4-shims.css

v4-shims.css

874 ms

cookieconsent.min.js

cookieconsent.min.js

853 ms

cookieconsent.min.css

cookieconsent.min.css

879 ms

zozo.accordion.min.css

zozo.accordion.min.css

945 ms

zozo.accordion.min.js

zozo.accordion.min.js

925 ms

navigation.css

navigation.css

970 ms

navigation.js

navigation.js

988 ms

jquery.jscroll.js

jquery.jscroll.js

1086 ms

leaflet.css

leaflet.css

1085 ms

leaflet.js

leaflet.js

1086 ms

screen.css

screen.css

1092 ms

MarkerCluster.css

MarkerCluster.css

1127 ms

MarkerCluster.Default.css

MarkerCluster.Default.css

1107 ms

easy-button.css

easy-button.css

1106 ms

leaflet-tag-filter-button.css

leaflet-tag-filter-button.css

888 ms

leaflet.markercluster-src.js

leaflet.markercluster-src.js

868 ms

easy-button.js

easy-button.js

845 ms

leaflet-tag-filter-button.js

leaflet-tag-filter-button.js

829 ms

osm.js

osm.js

1495 ms

preloader_400.gif

preloader_400.gif

298 ms

OpenSans-SemiBold.ttf

OpenSans-SemiBold.ttf

395 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

350 ms

fa-regular-400.woff

fa-regular-400.woff

288 ms

fa-solid-900.woff

fa-solid-900.woff

386 ms

20.png

20.png

791 ms

21.png

21.png

826 ms

20.png

20.png

900 ms

21.png

21.png

459 ms

22.png

22.png

499 ms

20.png

20.png

554 ms

21.png

21.png

577 ms

19.png

19.png

581 ms

19.png

19.png

582 ms

22.png

22.png

581 ms

22.png

22.png

594 ms

21.png

21.png

289 ms

19.png

19.png

361 ms

22.png

22.png

457 ms

21.png

21.png

485 ms

19.png

19.png

482 ms

22.png

22.png

483 ms

20.png

20.png

486 ms

20.png

20.png

492 ms

20.png

20.png

458 ms

19.png

19.png

485 ms

22.png

22.png

495 ms

20.png

20.png

495 ms

19.png

19.png

496 ms

22.png

22.png

550 ms

21.png

21.png

553 ms

21.png

21.png

581 ms

20.png

20.png

396 ms

21.png

21.png

494 ms

21.png

21.png

478 ms

19.png

19.png

409 ms

20.png

20.png

286 ms

22.png

22.png

315 ms

21.png

21.png

403 ms

20.png

20.png

227 ms

19.png

19.png

192 ms

22.png

22.png

200 ms

19.png

19.png

287 ms

21.png

21.png

353 ms

19.png

19.png

107 ms

20.png

20.png

284 ms

20.png

20.png

381 ms

22.png

22.png

341 ms

20.png

20.png

248 ms

19.png

19.png

274 ms

22.png

22.png

369 ms

22.png

22.png

327 ms

20.png

20.png

219 ms

21.png

21.png

228 ms

21.png

21.png

207 ms

19.png

19.png

164 ms

19.png

19.png

354 ms

22.png

22.png

285 ms

21.png

21.png

352 ms

22.png

22.png

274 ms

Accessibility Review

wecanhelp.de accessibility score

89

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

Links do not have a discernible name

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

wecanhelp.de best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

wecanhelp.de SEO score

87

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

wecanhelp.de

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