Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

horsereader.com

Horse Reader | Indie developer, making apps without ads or hidden costs

Page Load Speed

2.6 sec in total

First Response

293 ms

Resources Loaded

2.1 sec

Page Rendered

183 ms

horsereader.com screenshot

About Website

Click here to check amazing Horse Reader content. Otherwise, check out these important facts you probably never knew about horsereader.com

Welcome to the Horse Reader website Here you can learn more about the apps we have available on Amazon, Apple and Google Play. Horse Reader is dedicated to creating affordable, easy to use and kid saf...

Visit horsereader.com

Key Findings

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

Performance Metrics

horsereader.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

horsereader.com

293 ms

horsereader.wordpress.com

6 ms

horsereader.wordpress.com

23 ms

86 ms

style.css

87 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Horsereader.com, 38% (20 requests) were made to Horsereader.wordpress.com and 13% (7 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Horsereader.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.4 kB (19%)

Content Size

710.5 kB

After Optimization

572.1 kB

In fact, the total size of Horsereader.com main page is 710.5 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. 30% of websites need less resources to load. Images take 335.4 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 137.4 kB

  • Original 193.5 kB
  • After minification 190.6 kB
  • After compression 56.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 137.4 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 335.4 kB
  • After minification 335.4 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. Horse Reader images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 879 B

  • Original 163.2 kB
  • After minification 163.2 kB
  • After compression 162.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 162 B

  • Original 18.4 kB
  • After minification 18.4 kB
  • After compression 18.2 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. Horsereader.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (41%)

Requests Now

46

After Optimization

27

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horse Reader. 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 from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

horsereader.com accessibility score

98

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.

Best Practices

horsereader.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

horsereader.com SEO score

91

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Horsereader.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 Horsereader.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

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