Tools & Wizards About Us
mywickr.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

mywickr.com

AWS Wickr | Protecting Communications with End-to-End Encryption

Page Load Speed

1.1 sec in total

First Response

44 ms

Resources Loaded

631 ms

Page Rendered

453 ms

mywickr.com screenshot

About Website

Click here to check amazing My Wickr content for United States. Otherwise, check out these important facts you probably never knew about mywickr.com

Wickr is a single end-to-end encrypted service that provides a full suite of collaboration capabilities on any device.

Visit mywickr.com

Key Findings

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

Performance Metrics

mywickr.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

mywickr.com

44 ms

www.wickr.com

87 ms

master-anon-142780530171352696.css

18 ms

setImmediate.js

29 ms

lodash.compat.js

44 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mywickr.com, 95% (41 requests) were made to Wickr.com and 2% (1 request) were made to Pi.pardot.com. The less responsive or slowest element that took the longest time to load (192 ms) relates to the external source Pi.pardot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (51%)

Content Size

2.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mywickr.com main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 110.0 kB

  • Original 138.6 kB
  • After minification 133.0 kB
  • After compression 28.6 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 110.0 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 19.6 kB

  • Original 890.6 kB
  • After minification 871.0 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. My Wickr images are well optimized though.

JavaScript Optimization

-86%

Potential reduce by 972.1 kB

  • Original 1.1 MB
  • After minification 572.2 kB
  • After compression 152.3 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 972.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (71%)

Requests Now

38

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mywickr.com

mywickr.com

44 ms

www.wickr.com

www.wickr.com

87 ms

master-anon-142780530171352696.css

master-anon-142780530171352696.css

18 ms

setImmediate.js

setImmediate.js

29 ms

lodash.compat.js

lodash.compat.js

44 ms

async.js

async.js

32 ms

jquery.js

jquery.js

54 ms

jquery-url-parser.js

jquery-url-parser.js

30 ms

jquery-ui.js

jquery-ui.js

58 ms

jquery-textchange.js

jquery-textchange.js

40 ms

selectize.js

selectize.js

50 ms

jquery.cookie.js

jquery.cookie.js

46 ms

polyglot.js

polyglot.js

50 ms

jquery.get-outer-html.js

jquery.get-outer-html.js

52 ms

jquery.find-by-name.js

jquery.find-by-name.js

52 ms

jquery.projector.js

jquery.projector.js

58 ms

jquery.bottomless.js

jquery.bottomless.js

60 ms

jquery.selective.js

jquery.selective.js

68 ms

jquery.images-ready.js

jquery.images-ready.js

66 ms

jquery.radio.js

jquery.radio.js

65 ms

jquery.json-call.js

jquery.json-call.js

73 ms

jquery.lister.js

jquery.lister.js

74 ms

content.js

content.js

73 ms

content.js

content.js

73 ms

ui-2.js

ui-2.js

72 ms

content.js

content.js

74 ms

content.js

content.js

75 ms

content.js

content.js

74 ms

content.js

content.js

76 ms

_site-compiled.js

_site-compiled.js

76 ms

main.css

main.css

67 ms

638247664196080562-front-page-consumer-final.full.png

638247664196080562-front-page-consumer-final.full.png

30 ms

932326741156000396-wickr-messenger-with-tm-and-reg-marks-final.png

932326741156000396-wickr-messenger-with-tm-and-reg-marks-final.png

12 ms

204378544277647-front-page-professional-final.full.png

204378544277647-front-page-professional-final.full.png

29 ms

501717431357427638-wickr-professional-with-tm-and-reg-marks.png

501717431357427638-wickr-professional-with-tm-and-reg-marks.png

12 ms

logo-lines.svg

logo-lines.svg

11 ms

662303379650878653-security-verified.full.jpg

662303379650878653-security-verified.full.jpg

13 ms

78716096394254378-woman-at-window-final.full.jpg

78716096394254378-woman-at-window-final.full.jpg

17 ms

231242968695405530-woman-at-night-2-final.full.jpg

231242968695405530-woman-at-night-2-final.full.jpg

18 ms

lineto-brown-pro-light.woff

lineto-brown-pro-light.woff

14 ms

lineto-brown-pro-bold.woff

lineto-brown-pro-bold.woff

12 ms

lineto-brown-pro-regular.woff

lineto-brown-pro-regular.woff

21 ms

pd.js

pd.js

192 ms

Accessibility Review

mywickr.com accessibility score

95

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

Links do not have a discernible name

Best Practices

mywickr.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mywickr.com SEO score

80

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mywickr.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 Mywickr.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

mywickr.com

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