Tools & Wizards About Us
fci.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fci.org

The Fred Rogers Company - The legacy Lives On

Page Load Speed

1 sec in total

First Response

53 ms

Resources Loaded

730 ms

Page Rendered

264 ms

fci.org screenshot

About Website

Click here to check amazing Fci content. Otherwise, check out these important facts you probably never knew about fci.org

We honor Fred by carrying on his work. We're proud to be building on his legacy in innovative ways through a wide variety of childrens media.

Visit fci.org

Key Findings

We analyzed Fci.org page load time and found that the first response time was 53 ms and then it took 994 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

fci.org performance score

0

Network Requests Diagram

fci.org

53 ms

www.fredrogers.org

72 ms

meanmenu.css

30 ms

structure.css

67 ms

media.css

47 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fci.org, 53% (41 requests) were made to Fredrogers.org and 12% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (180 ms) relates to the external source Fredrogers.org.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fci.org main page is 2.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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.6 kB

  • Original 42.9 kB
  • After minification 38.0 kB
  • After compression 10.3 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 4.9 kB, which is 11% 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 32.6 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 23.8 kB

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

JavaScript Optimization

-59%

Potential reduce by 217.8 kB

  • Original 366.1 kB
  • After minification 344.2 kB
  • After compression 148.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 217.8 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 85.4 kB

  • Original 103.0 kB
  • After minification 82.3 kB
  • After compression 17.6 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. Fci.org needs all CSS files to be minified and compressed as it can save up to 85.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (44%)

Requests Now

73

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fci.org

fci.org

53 ms

www.fredrogers.org

www.fredrogers.org

72 ms

meanmenu.css

meanmenu.css

30 ms

structure.css

structure.css

67 ms

media.css

media.css

47 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

45 ms

jquery.js

jquery.js

16 ms

jquery.meanmenu.js

jquery.meanmenu.js

45 ms

jquery.animate-colors.js

jquery.animate-colors.js

29 ms

jQueryRotate.js

jQueryRotate.js

44 ms

fred-rogers-scripts.js

fred-rogers-scripts.js

44 ms

video-js.css

video-js.css

51 ms

video.js

video.js

111 ms

buttons.js

buttons.js

15 ms

classic-081711.css

classic-081711.css

18 ms

reset.css

reset.css

13 ms

stylesheet.css

stylesheet.css

13 ms

background-top-1.jpg

background-top-1.jpg

180 ms

__utm.gif

__utm.gif

174 ms

cse.js

cse.js

170 ms

widgets.js

widgets.js

161 ms

analytics.js

analytics.js

156 ms

getAllAppDefault.esi

getAllAppDefault.esi

77 ms

background-2.jpg

background-2.jpg

76 ms

logo.png

logo.png

22 ms

left_button.png

left_button.png

18 ms

right-button.png

right-button.png

19 ms

img-slider-pc-15a.jpg

img-slider-pc-15a.jpg

55 ms

img-slider-neighbor.jpg

img-slider-neighbor.jpg

56 ms

img-slider-home-mr-rogers.jpg

img-slider-home-mr-rogers.jpg

87 ms

img-slider-store-toysrus.jpg

img-slider-store-toysrus.jpg

95 ms

img-slider-home-young-mr-rogers.jpg

img-slider-home-young-mr-rogers.jpg

73 ms

home-dtn.jpg

home-dtn.jpg

74 ms

circle.png

circle.png

73 ms

triangle.png

triangle.png

86 ms

triangle2.png

triangle2.png

85 ms

home-p+c.jpg

home-p+c.jpg

86 ms

home-odd.jpg

home-odd.jpg

86 ms

home-mrn.jpg

home-mrn.jpg

106 ms

newsletter-background-picture.png

newsletter-background-picture.png

110 ms

newsletter-icon.png

newsletter-icon.png

98 ms

triangle4.png

triangle4.png

97 ms

img-icon-facebook.png

img-icon-facebook.png

97 ms

facebook-icon.png

facebook-icon.png

106 ms

support-icon.png

support-icon.png

108 ms

twitter-icon.png

twitter-icon.png

116 ms

info-icon.png

info-icon.png

113 ms

watch-episodes.png

watch-episodes.png

124 ms

footer-episode-1.png

footer-episode-1.png

123 ms

footer-episode-2.png

footer-episode-2.png

122 ms

footer-episode-3.png

footer-episode-3.png

123 ms

trebucbd-webfont.woff

trebucbd-webfont.woff

123 ms

cse.js

cse.js

45 ms

collect

collect

14 ms

jsapi

jsapi

40 ms

getSegment.php

getSegment.php

16 ms

checkOAuth.esi

checkOAuth.esi

25 ms

t.dhj

t.dhj

14 ms

default+en.css

default+en.css

13 ms

default+en.I.js

default+en.I.js

52 ms

jquery.form-n-validate.js

jquery.form-n-validate.js

47 ms

t.dhj

t.dhj

24 ms

default.css

default.css

16 ms

cm

cm

25 ms

s-3271.xgi

s-3271.xgi

36 ms

39 ms

hbpix

hbpix

86 ms

50 ms

async-ads.js

async-ads.js

70 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

47 ms

small-logo.png

small-logo.png

18 ms

search_box_icon.png

search_box_icon.png

15 ms

clear.png

clear.png

16 ms

nav_logo114.png

nav_logo114.png

12 ms

pixel

pixel

18 ms

xrefid.xgi

xrefid.xgi

6 ms

pixel

pixel

31 ms

2981

2981

30 ms

SEO Factors

fci.org 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 Fci.org 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 Fci.org 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

fci.org

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