Tools & Wizards About Us
rhizokids.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rhizokids.com

RhizoKids | Fighting for a Cure

Page Load Speed

4 sec in total

First Response

896 ms

Resources Loaded

2.5 sec

Page Rendered

599 ms

rhizokids.com screenshot

About Website

Visit rhizokids.com now to see the best up-to-date Rhizo Kids content and also check out these interesting facts you probably never knew about rhizokids.com

because these children can't wait!

Visit rhizokids.com

Key Findings

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

Performance Metrics

rhizokids.com performance score

0

Network Requests Diagram

rhizokids.com

896 ms

wp-emoji-release.min.js

123 ms

settings.css

137 ms

main.min.css

133 ms

renew.css

210 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 29% of them (28 requests) were addressed to the original Rhizokids.com, 12% (11 requests) were made to Graphics8.nytimes.com and 8% (8 requests) were made to Typeface.nyt.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Rhizokids.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (30%)

Content Size

5.6 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rhizokids.com main page is 5.6 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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 36.8 kB

  • Original 46.5 kB
  • After minification 45.8 kB
  • After compression 9.7 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 36.8 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 397.6 kB

  • Original 3.8 MB
  • After minification 3.4 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. Rhizo Kids images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 949.9 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 488.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 949.9 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 295.3 kB

  • Original 354.6 kB
  • After minification 340.7 kB
  • After compression 59.3 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. Rhizokids.com needs all CSS files to be minified and compressed as it can save up to 295.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rhizokids.com

rhizokids.com

896 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

123 ms

settings.css

settings.css

137 ms

main.min.css

main.min.css

133 ms

renew.css

renew.css

210 ms

css

css

22 ms

jquery.js

jquery.js

203 ms

jquery-migrate.min.js

jquery-migrate.min.js

159 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

267 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

201 ms

x-head.min.js

x-head.min.js

196 ms

cs-head.min.js

cs-head.min.js

251 ms

x-body.min.js

x-body.min.js

264 ms

comment-reply.min.js

comment-reply.min.js

342 ms

cs-body.min.js

cs-body.min.js

420 ms

wp-embed.min.js

wp-embed.min.js

342 ms

index.html

index.html

114 ms

btn_donateCC_LG.gif

btn_donateCC_LG.gif

279 ms

pixel.gif

pixel.gif

307 ms

Logo.png

Logo.png

268 ms

Polaroids.png

Polaroids.png

1306 ms

conference2016-865x483.png

conference2016-865x483.png

914 ms

phenomenome-logo.png

phenomenome-logo.png

91 ms

clinicaltrial-865x483.jpg

clinicaltrial-865x483.jpg

371 ms

Jakeandjordyn.jpg

Jakeandjordyn.jpg

304 ms

marley-865x483.jpg

marley-865x483.jpg

337 ms

jude3.jpeg

jude3.jpeg

470 ms

ian-1.jpg

ian-1.jpg

699 ms

dna.jpg

dna.jpg

698 ms

families.jpg

families.jpg

752 ms

Ohio-Chap.jpg

Ohio-Chap.jpg

779 ms

common.css

common.css

179 ms

relatedOverlay.css

relatedOverlay.css

211 ms

embed.css

embed.css

204 ms

libraries.embed.min.js

libraries.embed.min.js

242 ms

vhs-2.x.min.js

vhs-2.x.min.js

276 ms

tagx.js

tagx.js

242 ms

ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf

ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf

166 ms

toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf

toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf

195 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

808 ms

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

195 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

194 ms

saveModal.css

saveModal.css

63 ms

fdj3cyx.js

fdj3cyx.js

85 ms

100000003842698

100000003842698

23 ms

tagx.nytimes.com

tagx.nytimes.com

55 ms

fdj3cyx.css

fdj3cyx.css

179 ms

csma.js

csma.js

164 ms

vhs.css

vhs.css

81 ms

rhizo-videoSixteenByNine600.jpg

rhizo-videoSixteenByNine600.jpg

222 ms

vhs_offsite.woff

vhs_offsite.woff

47 ms

fbevents.js

fbevents.js

161 ms

controltag

controltag

44 ms

ast

ast

33 ms

EventTracker.js

EventTracker.js

39 ms

analytics.js

analytics.js

7 ms

chartbeat.js

chartbeat.js

46 ms

keywee.js

keywee.js

47 ms

comscore.js

comscore.js

43 ms

collect

collect

22 ms

dyjq-min.js

dyjq-min.js

30 ms

dy-min.js

dy-min.js

32 ms

controltag.js.e0ce6829d34e23edb3c90f3615dd81e0

controltag.js.e0ce6829d34e23edb3c90f3615dd81e0

99 ms

et.nytimes.com

et.nytimes.com

97 ms

collect

collect

99 ms

sp.js

sp.js

60 ms

fbds.js

fbds.js

156 ms

ping

ping

48 ms

m

m

40 ms

i

i

66 ms

ga-audiences

ga-audiences

91 ms

vhs.woff

vhs.woff

57 ms

nyt-karnak-display-130124-400-normal.woff

nyt-karnak-display-130124-400-normal.woff

57 ms

nyt-franklin-700-normal.woff

nyt-franklin-700-normal.woff

110 ms

nyt-franklin-500-normal.woff

nyt-franklin-500-normal.woff

153 ms

nyt-franklin-300-normal.woff

nyt-franklin-300-normal.woff

147 ms

nyt-cheltenham-400-normal.woff

nyt-cheltenham-400-normal.woff

141 ms

nyt-cheltenham-300-normal.woff

nyt-cheltenham-300-normal.woff

120 ms

nyt-cheltenham-200-normal.woff

nyt-cheltenham-200-normal.woff

118 ms

118 ms

111 ms

et.nytimes.com

et.nytimes.com

31 ms

adsct

adsct

156 ms

optout_check

optout_check

86 ms

get

get

101 ms

a.gif

a.gif

436 ms

activityi;src=3951336;type=digit0;cat=seque0;ord=476032907608.8965

activityi;src=3951336;type=digit0;cat=seque0;ord=476032907608.8965

72 ms

activityi;src=3951336;type=digit0;cat=tier200;ord=3843861895147.711

activityi;src=3951336;type=digit0;cat=tier200;ord=3843861895147.711

70 ms

activityi;src=3951336;type=digit0;cat=tier300;ord=1728302524425.0894

activityi;src=3951336;type=digit0;cat=tier300;ord=1728302524425.0894

76 ms

event

event

59 ms

genericusersync.ashx

genericusersync.ashx

66 ms

67 ms

379708.gif

379708.gif

38 ms

cc

cc

29 ms

pixel.gif

pixel.gif

12 ms

SEO Factors

rhizokids.com SEO score

0

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

rhizokids.com

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