Tools & Wizards About Us
whatchareading.com screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

whatchareading.com

What'cha Reading Press

Page Load Speed

4.3 sec in total

First Response

163 ms

Resources Loaded

1.7 sec

Page Rendered

2.5 sec

whatchareading.com screenshot

About Website

Click here to check amazing What Cha Reading content for Russia. Otherwise, check out these important facts you probably never knew about whatchareading.com

Small Press Publisher

Visit whatchareading.com

Key Findings

We analyzed Whatchareading.com page load time and found that the first response time was 163 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whatchareading.com performance score

0

Network Requests Diagram

whatchareading.com

163 ms

whatchareading.com

312 ms

www.whatchareadingpress.com

14 ms

chucksuffel.wordpress.com

24 ms

118 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Whatchareading.com, 30% (24 requests) were made to Chucksuffel.wordpress.com and 12% (10 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source Chucksuffel.wordpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 293.1 kB (2%)

Content Size

13.0 MB

After Optimization

12.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatchareading.com main page is 13.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. Only a small number of websites need less resources to load. Images take 12.6 MB which makes up the majority of the site volume.

HTML Optimization

-34%

Potential reduce by 138 B

  • Original 402 B
  • After minification 379 B
  • After compression 264 B

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 138 B or 34% of the original size.

Image Optimization

-2%

Potential reduce by 288.7 kB

  • Original 12.6 MB
  • After minification 12.3 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. What Cha Reading images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.2 kB

  • Original 382.8 kB
  • After minification 382.8 kB
  • After compression 378.6 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 154 B

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

Requests Breakdown

Number of requests can be reduced by 31 (45%)

Requests Now

69

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Cha 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 20 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whatchareading.com

whatchareading.com

163 ms

whatchareading.com

whatchareading.com

312 ms

www.whatchareadingpress.com

www.whatchareadingpress.com

14 ms

chucksuffel.wordpress.com

chucksuffel.wordpress.com

24 ms

118 ms

style.css

style.css

100 ms

108 ms

108 ms

121 ms

129 ms

css

css

143 ms

120 ms

133 ms

116 ms

128 ms

widgets.js

widgets.js

135 ms

hovercards.min.js

hovercards.min.js

135 ms

wpgroho.js

wpgroho.js

133 ms

124 ms

133 ms

index.min.js

index.min.js

132 ms

index.min.js

index.min.js

132 ms

132 ms

w.js

w.js

132 ms

conf

conf

351 ms

ga.js

ga.js

257 ms

typewriter.jpg

typewriter.jpg

70 ms

wonderlandconundrumcoverforstore-1.jpg

wonderlandconundrumcoverforstore-1.jpg

716 ms

ADjx6Y4ADcQ

ADjx6Y4ADcQ

383 ms

wpcom-gray-white.png

wpcom-gray-white.png

215 ms

master.html

master.html

263 ms

g.gif

g.gif

258 ms

284 ms

whatcha-reading-logo-cmyk.jpg

whatcha-reading-logo-cmyk.jpg

653 ms

fpy7phwxwaa2f2d.jpg

fpy7phwxwaa2f2d.jpg

332 ms

contractofaliftimesript01.png

contractofaliftimesript01.png

311 ms

contractofaliftimesript02.png

contractofaliftimesript02.png

311 ms

contractoalifetimecthullutt01.png

contractoalifetimecthullutt01.png

287 ms

killerelvisscriptpage1.png

killerelvisscriptpage1.png

403 ms

1.png

1.png

659 ms

ssrwscriptpage1.png

ssrwscriptpage1.png

377 ms

ssrwscriptpage2-1.png

ssrwscriptpage2-1.png

539 ms

elvis-cat-alf-page-1-2-26-19.jpg

elvis-cat-alf-page-1-2-26-19.jpg

664 ms

page11-ssscrp1.png

page11-ssscrp1.png

667 ms

page11-ssp1.png

page11-ssp1.png

666 ms

page4-swscrp5.png

page4-swscrp5.png

668 ms

page4-swp5.png

page4-swp5.png

669 ms

52797010_791486784565038_2162419628700073984_n.jpg

52797010_791486784565038_2162419628700073984_n.jpg

733 ms

52612850_789282791452104_7491548773936529408_o.jpg

52612850_789282791452104_7491548773936529408_o.jpg

670 ms

page6-swscrp6.png

page6-swscrp6.png

732 ms

page6-swp6.png

page6-swp6.png

671 ms

page13-ssscrp2.png

page13-ssscrp2.png

732 ms

page13-ssp2.png

page13-ssp2.png

736 ms

page15-ssscrp3.png

page15-ssscrp3.png

732 ms

page15-ssp3.png

page15-ssp3.png

742 ms

g.gif

g.gif

255 ms

g.gif

g.gif

258 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJPkqs.woff

0QI6MX1D_JOuGQbT0gvTJPa787weuxJPkqs.woff

256 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJPkqs.woff

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJPkqs.woff

255 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoqF2mg.woff

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoqF2mg.woff

149 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0CoqF2mg.woff

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0CoqF2mg.woff

149 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff

148 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff

149 ms

Genericons.svg

Genericons.svg

98 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

13 ms

__utm.gif

__utm.gif

79 ms

rlt-proxy.js

rlt-proxy.js

22 ms

23 ms

ata.js

ata.js

16 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

38 ms

base.js

base.js

64 ms

ad_status.js

ad_status.js

209 ms

AZmawUnBjeS4tv-yJel4MSA3UkbDC8sKRCiM64fOhhQ.js

AZmawUnBjeS4tv-yJel4MSA3UkbDC8sKRCiM64fOhhQ.js

188 ms

embed.js

embed.js

108 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

114 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

115 ms

id

id

38 ms

Create

Create

77 ms

actionbar.css

actionbar.css

83 ms

actionbar.js

actionbar.js

83 ms

Accessibility Review

whatchareading.com accessibility score

33

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

whatchareading.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

whatchareading.com SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatchareading.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 Whatchareading.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

whatchareading.com

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