Tools & Wizards About Us
postner.de screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

postner.de

PoLi | Online Marketing- & WordPress-Agentur aus Essen/NRW

Page Load Speed

4.9 sec in total

First Response

681 ms

Resources Loaded

3.3 sec

Page Rendered

868 ms

postner.de screenshot

About Website

Click here to check amazing Po Stner content. Otherwise, check out these important facts you probably never knew about postner.de

PoLi ist die Digitalagentur für hochwertige Kommunikations- und Marketinglösungen mit über 18 Jahren Erfahrung. Wir arbeiten schnell und unkompliziert.

Visit postner.de

Key Findings

We analyzed Postner.de page load time and found that the first response time was 681 ms and then it took 4.2 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

postner.de performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

55/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

12/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

www.postner.de

681 ms

wp-emoji-release.min.js

131 ms

styles.css

225 ms

style.css

209 ms

normalize.css

228 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 53% of them (68 requests) were addressed to the original Postner.de, 26% (33 requests) were made to Maps.google.com and 12% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (991 ms) belongs to the original domain Postner.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 731.5 kB (38%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Postner.de main page is 1.9 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 921.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 57.9 kB

  • Original 69.3 kB
  • After minification 63.3 kB
  • After compression 11.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. 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 57.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 38.7 kB

  • Original 921.9 kB
  • After minification 883.2 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. Po Stner images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 511.5 kB

  • Original 771.5 kB
  • After minification 748.3 kB
  • After compression 260.0 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 511.5 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 123.3 kB

  • Original 146.0 kB
  • After minification 102.9 kB
  • After compression 22.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. Postner.de needs all CSS files to be minified and compressed as it can save up to 123.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (36%)

Requests Now

112

After Optimization

72

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.postner.de

www.postner.de

681 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

131 ms

styles.css

styles.css

225 ms

style.css

style.css

209 ms

normalize.css

normalize.css

228 ms

main.css

main.css

237 ms

base.css

base.css

234 ms

skeleton.css

skeleton.css

244 ms

layout.css

layout.css

312 ms

portfoliostyle.css

portfoliostyle.css

328 ms

roll_over.css

roll_over.css

333 ms

jquery.fancybox.css

jquery.fancybox.css

337 ms

media_queries.css

media_queries.css

340 ms

responsiveexample.css

responsiveexample.css

347 ms

skeleton2.css

skeleton2.css

416 ms

js

js

19 ms

comment-reply.min.js

comment-reply.min.js

507 ms

jquery.js

jquery.js

566 ms

jquery.form.min.js

jquery.form.min.js

505 ms

scripts.js

scripts.js

505 ms

modernizr.custom.76532.js

modernizr.custom.76532.js

507 ms

plugins.js

plugins.js

522 ms

respond.min.js

respond.min.js

561 ms

jquery.inview.js

jquery.inview.js

563 ms

customScripts.js

customScripts.js

561 ms

jquery.fancybox.js

jquery.fancybox.js

595 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

620 ms

jquery.isotope.min.js

jquery.isotope.min.js

642 ms

wp-embed.min.js

wp-embed.min.js

685 ms

geweih-trans-klein1.png

geweih-trans-klein1.png

689 ms

bannerfooter.png

bannerfooter.png

687 ms

identity.png

identity.png

685 ms

brand.png

brand.png

887 ms

design.png

design.png

886 ms

websites.png

websites.png

887 ms

psd2.png

psd2.png

887 ms

motion.png

motion.png

887 ms

1451080966.png

1451080966.png

888 ms

css

css

25 ms

css

css

37 ms

banner.jpg

banner.jpg

912 ms

master_c.png

master_c.png

460 ms

profile_bg_01.png

profile_bg_01.png

476 ms

profile_bg_03.png

profile_bg_03.png

459 ms

profile_bg_02.png

profile_bg_02.png

460 ms

profile_footer.png

profile_footer.png

476 ms

p42.jpg

p42.jpg

757 ms

progress_02.png

progress_02.png

551 ms

progress_01.png

progress_01.png

554 ms

p52.jpg

p52.jpg

775 ms

portfolio_all_btn.png

portfolio_all_btn.png

574 ms

portfolio_design_btn.png

portfolio_design_btn.png

655 ms

portfolio_websites_btn.png

portfolio_websites_btn.png

672 ms

portfolio_publikationen_btn.png

portfolio_publikationen_btn.png

612 ms

ray1.jpg

ray1.jpg

816 ms

route3_icon.jpg

route3_icon.jpg

714 ms

mediale.png

mediale.png

919 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

12 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

14 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

16 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

13 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

13 ms

PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf

PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf

13 ms

PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf

PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf

13 ms

PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf

PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf

23 ms

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

23 ms

PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf

PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf

23 ms

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

21 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

22 ms

kids.png

kids.png

991 ms

tuerenwechsel2.jpg

tuerenwechsel2.jpg

803 ms

screenguide.jpg

screenguide.jpg

786 ms

03-12-2013-12-10-591.jpg

03-12-2013-12-10-591.jpg

861 ms

buch.jpg

buch.jpg

835 ms

email.png

email.png

854 ms

phone.png

phone.png

848 ms

facebook.png

facebook.png

909 ms

twitter.png

twitter.png

845 ms

xing.png

xing.png

862 ms

klout.png

klout.png

865 ms

linkedin.png

linkedin.png

865 ms

google.png

google.png

917 ms

ga.js

ga.js

196 ms

piwik.js

piwik.js

423 ms

ajax-loader.gif

ajax-loader.gif

766 ms

common.js

common.js

6 ms

map.js

map.js

23 ms

util.js

util.js

20 ms

marker.js

marker.js

20 ms

onion.js

onion.js

33 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

91 ms

stats.js

stats.js

26 ms

controls.js

controls.js

19 ms

transparent.png

transparent.png

29 ms

css

css

39 ms

spotlight-poi.png

spotlight-poi.png

35 ms

google4.png

google4.png

48 ms

mapcnt6.png

mapcnt6.png

49 ms

sv5.png

sv5.png

49 ms

vt

vt

50 ms

vt

vt

69 ms

vt

vt

41 ms

vt

vt

44 ms

vt

vt

43 ms

vt

vt

42 ms

vt

vt

68 ms

vt

vt

77 ms

vt

vt

78 ms

vt

vt

79 ms

vt

vt

81 ms

vt

vt

100 ms

vt

vt

96 ms

vt

vt

100 ms

vt

vt

109 ms

vt

vt

110 ms

vt

vt

102 ms

vt

vt

131 ms

vt

vt

133 ms

vt

vt

128 ms

vt

vt

135 ms

vt

vt

143 ms

vt

vt

140 ms

vt

vt

158 ms

vt

vt

161 ms

tmapctrl4.png

tmapctrl4.png

16 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

6 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

6 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

7 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

6 ms

Accessibility Review

postner.de accessibility score

96

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

postner.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

SEO Factors

postner.de SEO score

99

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

postner.de

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