Tools & Wizards About Us
history.fee.org screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

history.fee.org

Foundation for Economic Education (FEE) Historical Archive | Foundation for Economic Education

Page Load Speed

903 ms in total

First Response

129 ms

Resources Loaded

571 ms

Page Rendered

203 ms

history.fee.org screenshot

About Website

Welcome to history.fee.org homepage info - get ready to check History FEE best content for United States right away, or after learning these important things about history.fee.org

The Foundation for Economic Education turned 70 years old this year. Over the course of several decades, FEE collected a warehouse full of archives. Although the archives were eventually digitized, no...

Visit history.fee.org

Key Findings

We analyzed History.fee.org page load time and found that the first response time was 129 ms and then it took 774 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

history.fee.org performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value6,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.594

11/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

history.fee.org

129 ms

bootstrap.min.css

53 ms

font-awesome.min.css

83 ms

jquery.bxslider.css

50 ms

custom.min.css

76 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 67% of them (14 requests) were addressed to the original History.fee.org, 14% (3 requests) were made to Maxcdn.bootstrapcdn.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (129 ms) belongs to the original domain History.fee.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.3 kB (28%)

Content Size

145.7 kB

After Optimization

105.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of History.fee.org main page is 145.7 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. 35% of websites need less resources to load. Javascripts take 95.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 18.2 kB

  • Original 25.7 kB
  • After minification 21.8 kB
  • After compression 7.5 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 3.9 kB, which is 15% 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 18.2 kB or 71% of the original size.

Image Optimization

-31%

Potential reduce by 4.8 kB

  • Original 15.7 kB
  • After minification 10.8 kB

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. Obviously, History FEE needs image optimization as it can save up to 4.8 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 15.0 kB

  • Original 95.8 kB
  • After minification 95.8 kB
  • After compression 80.8 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 15.0 kB or 16% of the original size.

CSS Optimization

-26%

Potential reduce by 2.3 kB

  • Original 8.6 kB
  • After minification 8.6 kB
  • After compression 6.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. History.fee.org needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (65%)

Requests Now

17

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

history.fee.org

history.fee.org

129 ms

bootstrap.min.css

bootstrap.min.css

53 ms

font-awesome.min.css

font-awesome.min.css

83 ms

jquery.bxslider.css

jquery.bxslider.css

50 ms

custom.min.css

custom.min.css

76 ms

printing.min.css

printing.min.css

80 ms

rte.css

rte.css

71 ms

documentTabs.css

documentTabs.css

65 ms

treasure-overlay-spinner.css

treasure-overlay-spinner.css

70 ms

rocket-loader.min.js

rocket-loader.min.js

55 ms

v652eace1692a40cfa3763df669d7439c1639079717194

v652eace1692a40cfa3763df669d7439c1639079717194

92 ms

logo.png

logo.png

90 ms

ico-search.svg

ico-search.svg

88 ms

logo-footer.png

logo-footer.png

88 ms

neutratext-regular.woff

neutratext-regular.woff

58 ms

analytics.js

analytics.js

110 ms

angular.min.js

angular.min.js

64 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

60 ms

neutratext-bold.woff

neutratext-bold.woff

61 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

97 ms

collect

collect

14 ms

Accessibility Review

history.fee.org accessibility score

83

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

history.fee.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

history.fee.org SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 History.fee.org 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 History.fee.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

history.fee.org

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