Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

reading.com

Reading.com | Teach Your Child To Read Early, Step by Step

Page Load Speed

1.6 sec in total

First Response

65 ms

Resources Loaded

764 ms

Page Rendered

732 ms

About Website

Click here to check amazing Reading content for Puerto Rico. Otherwise, check out these important facts you probably never knew about reading.com

Backed by expert science, Reading.com offers parents a revolutionary step by step program that makes teaching your child to read easy and fun. Start today!

Visit reading.com

Key Findings

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

Performance Metrics

reading.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.7 s

18/100

10%

Network Requests Diagram

reading.com

65 ms

reading.com

35 ms

www.reading.com

173 ms

rw.js

54 ms

j.php

72 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 67% of them (20 requests) were addressed to the original Reading.com, 7% (2 requests) were made to Fonts.googleapis.com and 7% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (173 ms) belongs to the original domain Reading.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.0 kB (18%)

Content Size

1.1 MB

After Optimization

931.0 kB

In fact, the total size of Reading.com main page is 1.1 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. HTML takes 497.9 kB which makes up the majority of the site volume.

HTML Optimization

-42%

Potential reduce by 208.7 kB

  • Original 497.9 kB
  • After minification 495.8 kB
  • After compression 289.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 208.7 kB or 42% of the original size.

Image Optimization

-0%

Potential reduce by 174 B

  • Original 123.3 kB
  • After minification 123.1 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. Reading images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 132 B

  • Original 476.3 kB
  • After minification 476.3 kB
  • After compression 476.2 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

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

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

Accessibility Review

reading.com accessibility score

84

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

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

reading.com best practices score

83

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

SEO Factors

reading.com SEO score

85

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

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 Reading.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 Reading.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 Reading. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: