Tools & Wizards About Us
reading.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

reading.com

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

Page Load Speed

1.2 sec in total

First Response

246 ms

Resources Loaded

784 ms

Page Rendered

187 ms

reading.com screenshot

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 246 ms and then it took 971 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

reading.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

reading.com

246 ms

app.css

195 ms

logo.svg

172 ms

css

70 ms

analytics.js

25 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 50% of them (4 requests) were addressed to the original Reading.com, 25% (2 requests) were made to Google-analytics.com and 13% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (246 ms) belongs to the original domain Reading.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.2 kB (36%)

Content Size

39.1 kB

After Optimization

24.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Reading.com main page is 39.1 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. Only 5% of websites need less resources to load. Javascripts take 21.0 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 2.0 kB

  • Original 3.0 kB
  • After minification 2.3 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 748 B, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 2.0 kB or 67% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-80%

Potential reduce by 12.1 kB

  • Original 15.1 kB
  • After minification 15.1 kB
  • After compression 3.0 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 needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

reading.com

reading.com

246 ms

app.css

app.css

195 ms

logo.svg

logo.svg

172 ms

css

css

70 ms

analytics.js

analytics.js

25 ms

circular-black.woff

circular-black.woff

229 ms

collect

collect

12 ms

ga-audiences

ga-audiences

43 ms

Accessibility Review

reading.com accessibility score

88

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

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

SEO Factors

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

reading.com

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