Tools & Wizards About Us
lindenpark.de screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

lindenpark.de

Lindenpark Potsdam – Vielfalt tut gut

Page Load Speed

8.2 sec in total

First Response

2.1 sec

Resources Loaded

5.8 sec

Page Rendered

267 ms

lindenpark.de screenshot

About Website

Welcome to lindenpark.de homepage info - get ready to check Lindenpark best content for Germany right away, or after learning these important things about lindenpark.de

Visit lindenpark.de

Key Findings

We analyzed Lindenpark.de page load time and found that the first response time was 2.1 sec and then it took 6.1 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

lindenpark.de performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value22.7 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.913

3/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

Network Requests Diagram

lindenpark.de

2113 ms

base.css

338 ms

public.css

425 ms

columns.css

333 ms

authoring.css

275 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 98% of them (101 requests) were addressed to the original Lindenpark.de, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Lindenpark.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.7 kB (32%)

Content Size

824.0 kB

After Optimization

561.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lindenpark.de main page is 824.0 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. 30% of websites need less resources to load. Images take 533.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 209.4 kB

  • Original 273.3 kB
  • After minification 258.8 kB
  • After compression 63.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 209.4 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 53.0 kB

  • Original 533.0 kB
  • After minification 480.1 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. Lindenpark images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 312 B

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

Requests Breakdown

Number of requests can be reduced by 45 (54%)

Requests Now

83

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lindenpark.de

lindenpark.de

2113 ms

base.css

base.css

338 ms

public.css

public.css

425 ms

columns.css

columns.css

333 ms

authoring.css

authoring.css

275 ms

portlets.css

portlets.css

293 ms

controlpanel.css

controlpanel.css

401 ms

print.css

print.css

428 ms

deprecated.css

deprecated.css

474 ms

navtree.css

navtree.css

475 ms

invisibles.css

invisibles.css

494 ms

forms.css

forms.css

518 ms

ploneKss.css

ploneKss.css

556 ms

slimbox2.css

slimbox2.css

555 ms

simulator.css

simulator.css

658 ms

main.css

main.css

629 ms

ploneCustom.css

ploneCustom.css

641 ms

jquery-cachekey9135.js

jquery-cachekey9135.js

1118 ms

slimbox2-cachekey4624.js

slimbox2-cachekey4624.js

755 ms

external_link_confirmation-cachekey2867.js

external_link_confirmation-cachekey2867.js

341 ms

hide_columns.js

hide_columns.js

427 ms

nightmainback.png

nightmainback.png

225 ms

headerback.png

headerback.png

460 ms

logo.gif

logo.gif

226 ms

nightglobalnavstartbuttonselected.png

nightglobalnavstartbuttonselected.png

242 ms

nightglobalnavbutton.png

nightglobalnavbutton.png

272 ms

nightglobalnavendbutton.png

nightglobalnavendbutton.png

265 ms

nightsearchbox2.png

nightsearchbox2.png

386 ms

image_thumb

image_thumb

435 ms

image_thumb

image_thumb

524 ms

image_thumb

image_thumb

481 ms

image_preview

image_preview

465 ms

image_preview

image_preview

508 ms

image_portletsmall

image_portletsmall

672 ms

image_portletsmall

image_portletsmall

644 ms

image_portletsmall

image_portletsmall

619 ms

image_tile

image_tile

682 ms

image_mini

image_mini

697 ms

image_preview

image_preview

680 ms

image_icon

image_icon

758 ms

image_icon

image_icon

898 ms

image_icon

image_icon

875 ms

image_icon

image_icon

836 ms

image_icon

image_icon

868 ms

image_icon

image_icon

888 ms

image_icon

image_icon

893 ms

image_icon

image_icon

952 ms

image_icon

image_icon

1110 ms

image_icon

image_icon

1102 ms

image_icon

image_icon

1049 ms

SPI-NL-BRB_255px.png

SPI-NL-BRB_255px.png

1088 ms

nightdocumentheaderback.png

nightdocumentheaderback.png

1087 ms

startpage-banner.png

startpage-banner.png

1530 ms

light_blue_left.png

light_blue_left.png

1168 ms

blue_left.png

blue_left.png

1243 ms

blue_right.png

blue_right.png

1278 ms

arrow_right.png

arrow_right.png

1274 ms

ga.js

ga.js

59 ms

__utm.gif

__utm.gif

15 ms

arrow_down.png

arrow_down.png

1082 ms

light_blue_right.png

light_blue_right.png

1098 ms

image_portletbig

image_portletbig

1134 ms

light_green_left.png

light_green_left.png

1232 ms

green_left.png

green_left.png

1183 ms

green_right.png

green_right.png

1142 ms

image_thumb

image_thumb

1094 ms

light_green_right.png

light_green_right.png

1066 ms

image_preview

image_preview

1209 ms

image_thumb

image_thumb

1144 ms

image_preview

image_preview

1291 ms

image_thumb

image_thumb

1192 ms

image_portletbig

image_portletbig

1092 ms

image_portletbig

image_portletbig

1064 ms

image_portletbig

image_portletbig

1073 ms

image_preview

image_preview

1691 ms

image_tile

image_tile

1234 ms

image_mini

image_mini

1274 ms

image_icon

image_icon

1192 ms

image_icon

image_icon

1111 ms

image_icon

image_icon

1103 ms

image_icon

image_icon

1325 ms

image_icon

image_icon

1409 ms

image_icon

image_icon

1340 ms

image_icon

image_icon

1366 ms

image_icon

image_icon

1315 ms

image_icon

image_icon

1434 ms

spinner.gif

spinner.gif

1282 ms

input_background.gif

input_background.gif

1340 ms

image_icon

image_icon

1358 ms

image_icon

image_icon

1356 ms

leftportletheaderbig.png

leftportletheaderbig.png

1315 ms

leftportletheader-green.png

leftportletheader-green.png

1261 ms

leftportletheader.png

leftportletheader.png

1264 ms

leftportletheader-lila.png

leftportletheader-lila.png

1318 ms

rightportletheaderbig.png

rightportletheaderbig.png

1329 ms

rightportletheader-lila.png

rightportletheader-lila.png

1324 ms

rightportletheader.png

rightportletheader.png

1270 ms

lefttopcurve.png

lefttopcurve.png

157 ms

leftmiddlecurve.png

leftmiddlecurve.png

177 ms

leftbottomcurve.png

leftbottomcurve.png

177 ms

righttopcurve.png

righttopcurve.png

243 ms

rightmiddlecurve.png

rightmiddlecurve.png

245 ms

rightbottomcurve.png

rightbottomcurve.png

246 ms

Accessibility Review

lindenpark.de accessibility score

80

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.

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

lindenpark.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lindenpark.de SEO score

78

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lindenpark.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 Lindenpark.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

lindenpark.de

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