Tools & Wizards About Us
wearreader.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

wearreader.com

Wear Reader™- The World's first speed eReader for Apple Watch & Android Wearables

Page Load Speed

1.1 sec in total

First Response

140 ms

Resources Loaded

811 ms

Page Rendered

196 ms

wearreader.com screenshot

About Website

Welcome to wearreader.com homepage info - get ready to check Wear Reader best content right away, or after learning these important things about wearreader.com

Whether you're on the train, bus, or subway, you'll never again have to grab a book from your bag again. Wear Reader lets you read books straight from your wrist while you're on the go. Simply upload ...

Visit wearreader.com

Key Findings

We analyzed Wearreader.com page load time and found that the first response time was 140 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

wearreader.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

wearreader.com

140 ms

css

16 ms

index.css

76 ms

jquery-2.0.2.min.js

146 ms

banner2.jpg

297 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 50% of them (10 requests) were addressed to the original Wearreader.com, 25% (5 requests) were made to Fonts.gstatic.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (669 ms) belongs to the original domain Wearreader.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.4 kB (13%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wearreader.com main page is 2.0 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. 40% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 17.6 kB

  • Original 26.8 kB
  • After minification 26.3 kB
  • After compression 9.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 17.6 kB or 66% of the original size.

Image Optimization

-11%

Potential reduce by 205.7 kB

  • Original 1.9 MB
  • After minification 1.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. Obviously, Wear Reader needs image optimization as it can save up to 205.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 32.0 kB

  • Original 82.3 kB
  • After minification 82.3 kB
  • After compression 50.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 32.0 kB or 39% of the original size.

CSS Optimization

-11%

Potential reduce by 119 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 988 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. Wearreader.com needs all CSS files to be minified and compressed as it can save up to 119 B or 11% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wear Reader. According to our analytics all requests are already optimized.

Network Requests Diagram

wearreader.com

wearreader.com

140 ms

css

css

16 ms

index.css

index.css

76 ms

jquery-2.0.2.min.js

jquery-2.0.2.min.js

146 ms

banner2.jpg

banner2.jpg

297 ms

watch_empty.png

watch_empty.png

206 ms

iphone_screen.png

iphone_screen.png

669 ms

dune2.png

dune2.png

423 ms

apple_watch.png

apple_watch.png

496 ms

app_store_button.jpg

app_store_button.jpg

228 ms

download.png

download.png

245 ms

analytics.js

analytics.js

50 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

26 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

27 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

29 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

27 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

27 ms

collect

collect

46 ms

collect

collect

39 ms

js

js

67 ms

Accessibility Review

wearreader.com accessibility score

51

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wearreader.com SEO score

67

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

Image elements do not have [alt] attributes

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

wearreader.com

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