Tools & Wizards About Us
feynman.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

feynman.com

Richard Feynman – Scientist. Teacher. Raconteur. Musician

Page Load Speed

1.5 sec in total

First Response

310 ms

Resources Loaded

1.1 sec

Page Rendered

96 ms

feynman.com screenshot

About Website

Visit feynman.com now to see the best up-to-date Feynman content for United States and also check out these interesting facts you probably never knew about feynman.com

Richard Feynman, scientist, teacher, raconteur, and drummer. He assisted in the development of the atomic bomb, expanded the understanding of quantumelectrodynamics, translated Mayan hieroglyphics, an...

Visit feynman.com

Key Findings

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

Performance Metrics

feynman.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

www.feynman.com

310 ms

wp-emoji-release.min.js

65 ms

style.min.css

122 ms

all.css

124 ms

bootstrap.css

185 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 83% of them (29 requests) were addressed to the original Feynman.com, 11% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (425 ms) belongs to the original domain Feynman.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.0 kB (32%)

Content Size

370.3 kB

After Optimization

252.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Feynman.com main page is 370.3 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. 50% of websites need less resources to load. Javascripts take 166.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 37.7 kB

  • Original 47.7 kB
  • After minification 46.7 kB
  • After compression 10.0 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 37.7 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 26.6 kB
  • After minification 26.6 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. Feynman images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 44.6 kB

  • Original 166.5 kB
  • After minification 166.5 kB
  • After compression 121.9 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 44.6 kB or 27% of the original size.

CSS Optimization

-28%

Potential reduce by 35.6 kB

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

Requests Breakdown

Number of requests can be reduced by 24 (83%)

Requests Now

29

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.feynman.com

www.feynman.com

310 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

65 ms

style.min.css

style.min.css

122 ms

all.css

all.css

124 ms

bootstrap.css

bootstrap.css

185 ms

front.css

front.css

239 ms

css

css

19 ms

athemes-glyphs.css

athemes-glyphs.css

130 ms

bootstrap.min.css

bootstrap.min.css

191 ms

style.css

style.css

183 ms

jquery.js

jquery.js

250 ms

jquery-migrate.min.js

jquery-migrate.min.js

196 ms

bootstrap.min.js

bootstrap.min.js

264 ms

front.js

front.js

270 ms

chosen.jquery.min.js

chosen.jquery.min.js

271 ms

bootstrap.min.js

bootstrap.min.js

273 ms

superfish.js

superfish.js

299 ms

supersubs.js

supersubs.js

299 ms

settings.js

settings.js

307 ms

css

css

35 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

367 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

369 ms

jquery.form.min.js

jquery.form.min.js

372 ms

wp-embed.min.js

wp-embed.min.js

375 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

425 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

378 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

379 ms

feynapple.jpg

feynapple.jpg

62 ms

fdanim.gif

fdanim.gif

63 ms

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftoEdKZd2GP.ttf

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftoEdKZd2GP.ttf

8 ms

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIfto9tWZd2GP.ttf

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIfto9tWZd2GP.ttf

12 ms

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftoqNWZd2GP.ttf

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftoqNWZd2GP.ttf

32 ms

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftodtWZd2GP.ttf

3y9I6aknfjLm_3lMKjiMgmUUYBs04aUXNxt9gW2LIftodtWZd2GP.ttf

31 ms

athemes-glyphs.woff

athemes-glyphs.woff

119 ms

mejs-controls.svg

mejs-controls.svg

63 ms

Accessibility Review

feynman.com accessibility score

89

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

feynman.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

feynman.com SEO score

100

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

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

feynman.com

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