Tools & Wizards About Us
app.lockrmail.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

app.lockrmail.com

lockrMail | protect your inbox and preserve your privacy

Page Load Speed

1.1 sec in total

First Response

60 ms

Resources Loaded

964 ms

Page Rendered

72 ms

app.lockrmail.com screenshot

About Website

Welcome to app.lockrmail.com homepage info - get ready to check App LockrMail best content for United States right away, or after learning these important things about app.lockrmail.com

Organize and protect your inbox with lockrMail. We provide a free productivity tool that acts as a pre-filter for your inbox, keeping your identity private and secure.

Visit app.lockrmail.com

Key Findings

We analyzed App.lockrmail.com page load time and found that the first response time was 60 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

app.lockrmail.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value4,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

app.lockrmail.com

60 ms

app.lockrmail.com

56 ms

gtm.js

66 ms

2.eeec9ed3.chunk.css

30 ms

main.ef719134.chunk.css

107 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 18% of them (6 requests) were addressed to the original App.lockrmail.com, 38% (13 requests) were made to D.adroll.com and 9% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (524 ms) relates to the external source Widget.joinatlas.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.5 kB (14%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of App.lockrmail.com 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 6.7 kB

  • Original 9.7 kB
  • After minification 9.7 kB
  • After compression 3.0 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 69% of the original size.

JavaScript Optimization

-14%

Potential reduce by 244.6 kB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.5 MB

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 244.6 kB or 14% of the original size.

CSS Optimization

-18%

Potential reduce by 27.2 kB

  • Original 150.3 kB
  • After minification 150.3 kB
  • After compression 123.1 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. App.lockrmail.com needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (81%)

Requests Now

21

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

app.lockrmail.com

app.lockrmail.com

60 ms

app.lockrmail.com

app.lockrmail.com

56 ms

gtm.js

gtm.js

66 ms

2.eeec9ed3.chunk.css

2.eeec9ed3.chunk.css

30 ms

main.ef719134.chunk.css

main.ef719134.chunk.css

107 ms

onboarding.js

onboarding.js

524 ms

2.e09aec92.chunk.js

2.e09aec92.chunk.js

196 ms

main.824a4525.chunk.js

main.824a4525.chunk.js

190 ms

roundtrip.js

roundtrip.js

65 ms

js

js

106 ms

fbevents.js

fbevents.js

56 ms

js

js

89 ms

7JCBP3VE5JCG3OTQUIL5UJ

7JCBP3VE5JCG3OTQUIL5UJ

15 ms

out

out

12 ms

BVDGST3BQ5DD3PXLIODBV7

BVDGST3BQ5DD3PXLIODBV7

8 ms

out

out

11 ms

out

out

19 ms

out

out

19 ms

out

out

18 ms

out

out

18 ms

out

out

20 ms

out

out

31 ms

out

out

31 ms

out

out

31 ms

tap.php

tap.php

112 ms

Pug

Pug

100 ms

rum

rum

25 ms

pixel

pixel

27 ms

sd

sd

34 ms

xuid

xuid

13 ms

sync

sync

22 ms

bounce

bounce

17 ms

in

in

6 ms

sdk.js

sdk.js

25 ms

Accessibility Review

app.lockrmail.com accessibility score

67

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.

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

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

app.lockrmail.com 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

Page has valid source maps

SEO Factors

app.lockrmail.com SEO score

85

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 App.lockrmail.com 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 App.lockrmail.com 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

app.lockrmail.com

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