Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

weeklyreader.com

Scholastic Classroom & News Magazines | Subscribe Now!

Page Load Speed

2.1 sec in total

First Response

50 ms

Resources Loaded

1.5 sec

Page Rendered

459 ms

weeklyreader.com screenshot

About Website

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

Scholastic Classroom Magazines & Scholastic News Magazines cover the latest topics to enhance instruction in math, science, reading, social studies, and more! Subscribe Today!

Visit weeklyreader.com

Key Findings

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

Performance Metrics

weeklyreader.com performance score

0

Network Requests Diagram

weeklyreader.com

50 ms

classroommagazines.scholastic.com

74 ms

header.css

45 ms

jquery-ui-1.8.4.custom.css

94 ms

cmshared.css

96 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weeklyreader.com, 65% (87 requests) were made to Classroommagazines.scholastic.com and 11% (14 requests) were made to Scholastic.com. The less responsive or slowest element that took the longest time to load (387 ms) relates to the external source Classroommagazines.scholastic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (55%)

Content Size

3.4 MB

After Optimization

1.5 MB

In fact, the total size of Weeklyreader.com main page is 3.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 121.5 kB

  • Original 150.1 kB
  • After minification 136.7 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 121.5 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 12.3 kB

  • Original 1.1 MB
  • After minification 1.1 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. Weeklyreader images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 864.4 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 362.1 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 864.4 kB or 70% of the original size.

CSS Optimization

-93%

Potential reduce by 854.3 kB

  • Original 915.1 kB
  • After minification 816.8 kB
  • After compression 60.8 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. Weeklyreader.com needs all CSS files to be minified and compressed as it can save up to 854.3 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (55%)

Requests Now

131

After Optimization

59

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

SEO Factors

weeklyreader.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weeklyreader.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Weeklyreader.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 description is not detected on the main page of Weeklyreader. 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: