Tools & Wizards About Us
pflanzenkunde.net screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pflanzenkunde.net

Panglima79: Menemani Waktu yang Anda Sisihkan untuk Diri Sendiri

Page Load Speed

3.2 sec in total

First Response

500 ms

Resources Loaded

2.4 sec

Page Rendered

299 ms

pflanzenkunde.net screenshot

About Website

Welcome to pflanzenkunde.net homepage info - get ready to check Pflanzenkunde best content for Germany right away, or after learning these important things about pflanzenkunde.net

Di antara banyaknya hal yang harus diurus, kadang kita perlu waktu kecil yang benar-benar milik sendiri. Panglima79 hadir untuk menemani jeda itu, tanpa tuntutan dan tanpa target. Cukup duduk, tarik n...

Visit pflanzenkunde.net

Key Findings

We analyzed Pflanzenkunde.net page load time and found that the first response time was 500 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pflanzenkunde.net performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,070 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

www.pflanzenkunde.net

500 ms

template.css

231 ms

jstyle.css

215 ms

jquery.min.js

334 ms

jquery-noconflict.js

217 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 56% of them (33 requests) were addressed to the original Pflanzenkunde.net, 7% (4 requests) were made to Pagead2.googlesyndication.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (984 ms) belongs to the original domain Pflanzenkunde.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 812.3 kB (46%)

Content Size

1.8 MB

After Optimization

942.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pflanzenkunde.net main page is 1.8 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. 70% of websites need less resources to load. Images take 812.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.7 kB

  • Original 35.1 kB
  • After minification 29.8 kB
  • After compression 8.4 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 5.3 kB, which is 15% 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 26.7 kB or 76% of the original size.

Image Optimization

-14%

Potential reduce by 116.7 kB

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

JavaScript Optimization

-64%

Potential reduce by 301.0 kB

  • Original 470.5 kB
  • After minification 464.6 kB
  • After compression 169.5 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 301.0 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 367.9 kB

  • Original 436.8 kB
  • After minification 400.8 kB
  • After compression 68.9 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. Pflanzenkunde.net needs all CSS files to be minified and compressed as it can save up to 367.9 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pflanzenkunde.net

www.pflanzenkunde.net

500 ms

template.css

template.css

231 ms

jstyle.css

jstyle.css

215 ms

jquery.min.js

jquery.min.js

334 ms

jquery-noconflict.js

jquery-noconflict.js

217 ms

jquery-migrate.min.js

jquery-migrate.min.js

217 ms

tabs-state.js

tabs-state.js

218 ms

mootools-core.js

mootools-core.js

431 ms

core.js

core.js

323 ms

caption.js

caption.js

320 ms

bootstrap.min.js

bootstrap.min.js

325 ms

jscript.js

jscript.js

349 ms

icomoon2.css

icomoon2.css

427 ms

brand

brand

16 ms

show_ads.js

show_ads.js

5 ms

brand

brand

29 ms

pixel.gif

pixel.gif

208 ms

650x300-blumen-bedeutung.jpg

650x300-blumen-bedeutung.jpg

556 ms

650x300-schneegloeckchen.jpg

650x300-schneegloeckchen.jpg

465 ms

650x300-rhabarber-ernte.jpg

650x300-rhabarber-ernte.jpg

673 ms

650x300-frauenmanteltee.jpg

650x300-frauenmanteltee.jpg

470 ms

650x300-hochbeet-aus-holz.jpg

650x300-hochbeet-aus-holz.jpg

465 ms

60x60-blumen-bedeutung.jpg

60x60-blumen-bedeutung.jpg

175 ms

60x60-schneegloeckchen.jpg

60x60-schneegloeckchen.jpg

294 ms

60x60-rhabarber-ernte.jpg

60x60-rhabarber-ernte.jpg

429 ms

60x60-frauenmanteltee.jpg

60x60-frauenmanteltee.jpg

515 ms

60x60-hochbeet-aus-holz.jpg

60x60-hochbeet-aus-holz.jpg

553 ms

hochbeete-bauen-angebot.jpg

hochbeete-bauen-angebot.jpg

660 ms

all.js

all.js

12 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

89 ms

ca-pub-6616549157839879.js

ca-pub-6616549157839879.js

155 ms

zrt_lookup.html

zrt_lookup.html

157 ms

show_ads_impl.js

show_ads_impl.js

70 ms

load-indicator.gif

load-indicator.gif

508 ms

transparent_bg.png

transparent_bg.png

552 ms

previous.png

previous.png

595 ms

next.png

next.png

592 ms

icomoon.svg

icomoon.svg

724 ms

ryz37L7kYTE

ryz37L7kYTE

154 ms

undefined

undefined

984 ms

pause.png

pause.png

665 ms

arrow-bg.png

arrow-bg.png

668 ms

grad-bg.gif

grad-bg.gif

669 ms

ads

ads

302 ms

lwa.js

lwa.js

267 ms

osd.js

osd.js

20 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

24 ms

www-embed-player.js

www-embed-player.js

42 ms

base.js

base.js

67 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

42 ms

ad_status.js

ad_status.js

92 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

88 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

94 ms

trackPage.php

trackPage.php

160 ms

s_0RUAwCXZ4b_1554121247.html

s_0RUAwCXZ4b_1554121247.html

82 ms

a.js;p=11177200956835;a=11177200932861;cache=7829876484744513

a.js;p=11177200956835;a=11177200932861;cache=7829876484744513

114 ms

creative_add_on.js

creative_add_on.js

125 ms

PAPlus_OliviaMunn_FSH_300x600.jpg

PAPlus_OliviaMunn_FSH_300x600.jpg

125 ms

adchoices.png

adchoices.png

141 ms

Accessibility Review

pflanzenkunde.net accessibility score

88

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

pflanzenkunde.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pflanzenkunde.net SEO score

79

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 Pflanzenkunde.net 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 Pflanzenkunde.net 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

pflanzenkunde.net

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