Tools & Wizards About Us
markmail.org screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

markmail.org

Home - MarkMail - Community libraries

Page Load Speed

9.9 sec in total

First Response

587 ms

Resources Loaded

4.2 sec

Page Rendered

5.1 sec

markmail.org screenshot

About Website

Visit markmail.org now to see the best up-to-date Mark Mail content for United States and also check out these interesting facts you probably never knew about markmail.org

Visit markmail.org

Key Findings

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

Performance Metrics

markmail.org performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

markmail.org

587 ms

base_1454161917.css

103 ms

home_1454161917.css

136 ms

mk_1454161917.js

1040 ms

base_1454161917.js

1040 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 75% of them (12 requests) were addressed to the original Markmail.org, 13% (2 requests) were made to Stats.g.doubleclick.net and 6% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Markmail.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.0 kB (64%)

Content Size

957.1 kB

After Optimization

340.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Markmail.org main page is 957.1 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. 25% of websites need less resources to load. Javascripts take 877.1 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 6.7 kB

  • Original 9.9 kB
  • After minification 9.4 kB
  • After compression 3.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. 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 6.7 kB or 67% of the original size.

Image Optimization

-7%

Potential reduce by 4.2 kB

  • Original 59.7 kB
  • After minification 55.5 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. Mark Mail images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 598.1 kB

  • Original 877.1 kB
  • After minification 867.4 kB
  • After compression 279.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 598.1 kB or 68% of the original size.

CSS Optimization

-77%

Potential reduce by 8.0 kB

  • Original 10.4 kB
  • After minification 8.2 kB
  • After compression 2.4 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. Markmail.org needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (33%)

Requests Now

15

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

markmail.org

markmail.org

587 ms

base_1454161917.css

base_1454161917.css

103 ms

home_1454161917.css

home_1454161917.css

136 ms

mk_1454161917.js

mk_1454161917.js

1040 ms

base_1454161917.js

base_1454161917.js

1040 ms

api.js

api.js

16 ms

so_1454161917.js

so_1454161917.js

1038 ms

dc.js

dc.js

922 ms

ml-logo.png

ml-logo.png

448 ms

help_cream.png

help_cream.png

471 ms

bullet.png

bullet.png

471 ms

feed-icon-10x10.gif

feed-icon-10x10.gif

471 ms

hdi_ibm.gif

hdi_ibm.gif

470 ms

marklogic-small.png

marklogic-small.png

475 ms

__utm.gif

__utm.gif

645 ms

recaptcha__en.js

recaptcha__en.js

622 ms

Accessibility Review

markmail.org accessibility score

50

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

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

Best Practices

markmail.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

markmail.org SEO score

54

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Markmail.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Markmail.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

markmail.org

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