Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ec-messenger.de

Mapp Marketing Cloud

Page Load Speed

5.8 sec in total

First Response

346 ms

Resources Loaded

4.4 sec

Page Rendered

1.1 sec

About Website

Click here to check amazing Ec Messenger content. Otherwise, check out these important facts you probably never knew about ec-messenger.de

Mapp Marketing Cloud allows you to collect and analyze your customer data with AI, and trigger personalized campaigns across email, SMS, app, and your website.

Visit ec-messenger.de

Key Findings

We analyzed Ec-messenger.de page load time and found that the first response time was 346 ms and then it took 5.5 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

ec-messenger.de performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

19/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,300 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.107

88/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

ec-messenger.de

346 ms

www.mapp.com

238 ms

mapp.com

1086 ms

style.min.css

122 ms

style.css

240 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ec-messenger.de, 87% (95 requests) were made to Mapp.com and 4% (4 requests) were made to B.sf-syn.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Mapp.com.

Page Optimization Overview & Recommendations

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

Content Size

3.2 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ec-messenger.de main page is 3.2 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 203.7 kB

  • Original 240.9 kB
  • After minification 196.7 kB
  • After compression 37.2 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 44.2 kB, which is 18% 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 203.7 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 24.2 kB

  • Original 2.7 MB
  • After minification 2.7 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. Ec Messenger images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 14 B

  • Original 191.8 kB
  • After minification 191.8 kB
  • After compression 191.7 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

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 50 (50%)

Requests Now

100

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

ec-messenger.de accessibility score

74

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

button, link, and menuitem elements do not have accessible names.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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

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

ec-messenger.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ec-messenger.de SEO score

86

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

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

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 Ec-messenger.de 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 Ec-messenger.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

Open Graph data is detected on the main page of Ec Messenger. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: