Tools & Wizards About Us
posteo.org screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

posteo.org

Email green, secure, simple and ad-free - posteo.de -

Page Load Speed

4.8 sec in total

First Response

414 ms

Resources Loaded

3.2 sec

Page Rendered

1.2 sec

posteo.org screenshot

About Website

Welcome to posteo.org homepage info - get ready to check Posteo best content right away, or after learning these important things about posteo.org

Posteo is an innovative email provider that is concerned with sustainability and privacy and is completely ad-free. Our email accounts, calendars and address books can be synchronised - we use compreh...

Visit posteo.org

Key Findings

We analyzed Posteo.org page load time and found that the first response time was 414 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

posteo.org performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.386

27/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

posteo.org

414 ms

posteo.de

627 ms

en

208 ms

toggle-password-visibility.css

102 ms

swiper-bundle.min.css

204 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Posteo.org, 99% (76 requests) were made to Posteo.de. The less responsive or slowest element that took the longest time to load (953 ms) relates to the external source Posteo.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.9 kB (7%)

Content Size

850.2 kB

After Optimization

793.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Posteo.org main page is 850.2 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. 40% of websites need less resources to load. Images take 685.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 47.1 kB

  • Original 62.6 kB
  • After minification 53.5 kB
  • After compression 15.5 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 9.1 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 47.1 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 685.9 kB
  • After minification 685.9 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. Posteo images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 2.5 kB

  • Original 55.8 kB
  • After minification 55.5 kB
  • After compression 53.2 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

-16%

Potential reduce by 7.3 kB

  • Original 45.9 kB
  • After minification 45.9 kB
  • After compression 38.6 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. Posteo.org needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (21%)

Requests Now

72

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

posteo.org

posteo.org

414 ms

posteo.de

posteo.de

627 ms

en

en

208 ms

toggle-password-visibility.css

toggle-password-visibility.css

102 ms

swiper-bundle.min.css

swiper-bundle.min.css

204 ms

p_styles-website.css

p_styles-website.css

491 ms

basics.js

basics.js

304 ms

feedback-messages.js

feedback-messages.js

305 ms

responsive-nav.min.js

responsive-nav.min.js

306 ms

responsive-nav-init.js

responsive-nav-init.js

304 ms

posteo-website-onscroll.js

posteo-website-onscroll.js

403 ms

posteo-website.js

posteo-website.js

403 ms

swiper-bundle.min.js

swiper-bundle.min.js

608 ms

swiper-init-stage-slider.js

swiper-init-stage-slider.js

407 ms

swiper-init-press-slider.js

swiper-init-press-slider.js

606 ms

p-wm_detectTouchOrMouse.js

p-wm_detectTouchOrMouse.js

607 ms

ie11-polyfills.js

ie11-polyfills.js

607 ms

toggle-password-visibility.js

toggle-password-visibility.js

608 ms

toggle-password-visibility-login.js

toggle-password-visibility-login.js

609 ms

posteo-logo.svg

posteo-logo.svg

109 ms

fa-globe.svg

fa-globe.svg

111 ms

icon-plus-subnav.svg

icon-plus-subnav.svg

107 ms

slider-1-intro_de.png

slider-1-intro_de.png

162 ms

slider-10-themes_de.png

slider-10-themes_de.png

376 ms

slider-2-email_de.png

slider-2-email_de.png

402 ms

slider-3-kalender_de.png

slider-3-kalender_de.png

303 ms

slider-4-adressbuch_de.png

slider-4-adressbuch_de.png

212 ms

slider-5-nachhaltig.png

slider-5-nachhaltig.png

358 ms

slider-6-datenschutz.png

slider-6-datenschutz.png

315 ms

slider-7-verschluesselung.png

slider-7-verschluesselung.png

406 ms

slider-8-werbefrei.png

slider-8-werbefrei.png

419 ms

slider-9-umzugsservice.png

slider-9-umzugsservice.png

455 ms

mail_leistungen.png

mail_leistungen.png

479 ms

arrow-right-long.svg

arrow-right-long.svg

500 ms

p_icon_double-slash-dot_solid.svg

p_icon_double-slash-dot_solid.svg

506 ms

screenshot_guardian.png

screenshot_guardian.png

521 ms

screenshot_planetwissen.png

screenshot_planetwissen.png

552 ms

screenshot_stiwa.png

screenshot_stiwa.png

580 ms

screenshot_heise.png

screenshot_heise.png

600 ms

screenshot_dradio.png

screenshot_dradio.png

606 ms

screenshot_faz.png

screenshot_faz.png

622 ms

screenshot_oekotest.png

screenshot_oekotest.png

651 ms

screenshot_ard.png

screenshot_ard.png

681 ms

screenshot_technologyreview.png

screenshot_technologyreview.png

702 ms

screenshot_ct.png

screenshot_ct.png

707 ms

screenshot_computerbild.png

screenshot_computerbild.png

724 ms

screenshot_tagesspiegel.png

screenshot_tagesspiegel.png

747 ms

screenshot_linux.png

screenshot_linux.png

953 ms

DroidSans-webfont.woff

DroidSans-webfont.woff

785 ms

DroidSans-Bold-webfont.woff

DroidSans-Bold-webfont.woff

744 ms

screenshot_chip.png

screenshot_chip.png

744 ms

screenshot_futurzwei.png

screenshot_futurzwei.png

772 ms

screenshot_netzpolitik.png

screenshot_netzpolitik.png

775 ms

screenshot_spon.png

screenshot_spon.png

811 ms

screenshot_sz.png

screenshot_sz.png

818 ms

auth_token

auth_token

806 ms

screenshot_irishtimes.png

screenshot_irishtimes.png

821 ms

screenshot_berlinerzeitung.png

screenshot_berlinerzeitung.png

839 ms

screenshot_macwelt.png

screenshot_macwelt.png

829 ms

screenshot_stampa.png

screenshot_stampa.png

799 ms

screenshot_parisberlin.png

screenshot_parisberlin.png

713 ms

screenshot_n24.png

screenshot_n24.png

716 ms

fa-5-solid_caret-circle-left.svg

fa-5-solid_caret-circle-left.svg

689 ms

ripe.png

ripe.png

869 ms

tux.png

tux.png

694 ms

logo_gpe-strom.png

logo_gpe-strom.png

707 ms

navigator_start.png

navigator_start.png

702 ms

100pro_puzzle.png

100pro_puzzle.png

678 ms

strom_puzzle-gpe.png

strom_puzzle-gpe.png

665 ms

daten_puzzle.png

daten_puzzle.png

697 ms

einkauf_puzzle.png

einkauf_puzzle.png

708 ms

schloss_puzzle.png

schloss_puzzle.png

699 ms

anonym_puzzle.png

anonym_puzzle.png

680 ms

synch_puzzle.png

synch_puzzle.png

661 ms

sparschwein_puzzle.png

sparschwein_puzzle.png

698 ms

plus_puzzle.png

plus_puzzle.png

709 ms

p_print_website.css

p_print_website.css

103 ms

Accessibility Review

posteo.org accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

posteo.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

posteo.org SEO score

100

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

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 Posteo.org 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 Posteo.org 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

posteo.org

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