32.3 sec in total
15 ms
30 sec
2.3 sec
Welcome to farnsworthproject.org homepage info - get ready to check Farnsworth Project best content right away, or after learning these important things about farnsworthproject.org
Floods at Farnsworth over the past 60 years have caused extensive damage to the structure and its contents.
Visit farnsworthproject.orgWe analyzed Farnsworthproject.org page load time and found that the first response time was 15 ms and then it took 32.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
farnsworthproject.org performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value23.5 s
0/100
25%
Value14.0 s
1/100
10%
Value14,330 ms
0/100
30%
Value0.18
67/100
15%
Value23.9 s
1/100
10%
15 ms
110 ms
9988 ms
114 ms
127 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Farnsworthproject.org, 72% (68 requests) were made to Edithfarnsworthhouse.org and 4% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Tripadvisor.com.
Page size can be reduced by 1.0 MB (43%)
2.4 MB
1.4 MB
In fact, the total size of Farnsworthproject.org main page is 2.4 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. 55% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.
Potential reduce by 1.0 MB
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 1.0 MB or 86% of the original size.
Potential reduce by 13.1 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. Farnsworth Project images are well optimized though.
Potential reduce by 1.1 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.
Potential reduce by 3.7 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. Farnsworthproject.org needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 12% of the original size.
Number of requests can be reduced by 72 (86%)
84
12
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Farnsworth Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 68 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
farnsworthproject.org
15 ms
110 ms
9988 ms
wp-emoji-release.min.js
114 ms
simple-banner.css
127 ms
wppopups-base.css
170 ms
style.min.css
198 ms
jquery.min.js
194 ms
jquery-migrate.min.js
180 ms
simple-banner.js
213 ms
external-tracking.min.js
218 ms
addthis_widget.js
26 ms
437 ms
style.min.css
205 ms
regenerator-runtime.min.js
206 ms
wp-polyfill.min.js
206 ms
hooks.min.js
207 ms
wppopups.js
205 ms
cssua.js
206 ms
fusion-animations.js
364 ms
fusion-vertical-menu-widget.js
367 ms
modernizr.js
367 ms
fusion.js
365 ms
bootstrap.transition.js
364 ms
bootstrap.tooltip.js
364 ms
jquery.requestAnimationFrame.js
428 ms
jquery.easing.js
430 ms
jquery.fitvids.js
577 ms
jquery.flexslider.js
577 ms
jquery.ilightbox.js
579 ms
jquery.mousewheel.js
578 ms
jquery.placeholder.js
580 ms
jquery.fade.js
579 ms
fusion-parallax.js
580 ms
fusion-video-general.js
580 ms
fusion-video-bg.js
581 ms
fusion-lightbox.js
582 ms
fusion-tooltip.js
581 ms
fusion-sharing-box.js
584 ms
jquery.sticky-kit.js
610 ms
fusion-youtube.js
611 ms
vimeoPlayer.js
709 ms
avada-general-footer.js
637 ms
avada-quantity.js
702 ms
avada-crossfade-images.js
692 ms
avada-select.js
794 ms
avada-tabs-widget.js
792 ms
jquery.elasticslider.js
790 ms
analytics.js
144 ms
moatframe.js
223 ms
layers.fa6cd1947ce26e890d3d.js
81 ms
CoE2017_WidgetAsset-14348-2.png
3451 ms
fusion-alert.js
656 ms
awb-off-canvas.js
647 ms
fusion-flexslider.js
648 ms
fusion-container.js
649 ms
avada-elastic-slider.js
647 ms
avada-gravity-forms.js
648 ms
avada-drop-down.js
650 ms
collect
146 ms
collect
162 ms
collect
146 ms
avada-to-top.js
493 ms
avada-header.js
492 ms
avada-menu.js
500 ms
wejs
19528 ms
avada-sidebars.js
522 ms
bootstrap.scrollspy.js
546 ms
avada-scrollspy.js
547 ms
fusion-responsive-typography.js
493 ms
fusion-scroll-to-anchor.js
496 ms
182 ms
fusion-general-global.js
365 ms
fusion-video.js
394 ms
fusion-column.js
439 ms
awb-icons.woff
406 ms
fa-solid-900.woff
548 ms
fa-regular-400.woff
518 ms
EdithFarnsworthHouse_LOGO_K.png
518 ms
Farnsworth-Flood_mr1.jpg
683 ms
NTHPsite_LOGO_White.png
544 ms
output.cd413ebdce98.css
29 ms
output.e89846825ae9.css
5 ms
output.b36836681687.js
11 ms
djangojs.js
82 ms
output.781bb6115676.js
79 ms
160 ms
78 ms
roboto-v20-vietnamese_latin-ext_latin_greek-ext_greek_cyrillic-ext_cyrillic-regular.woff
31 ms
roboto-v20-vietnamese_latin-ext_latin_greek-ext_greek_cyrillic-ext_cyrillic-500.woff
35 ms
roboto-v20-vietnamese_latin-ext_latin_greek-ext_greek_cyrillic-ext_cyrillic-700.woff
41 ms
_ate.track.config_resp
157 ms
300lo.json
184 ms
sh.f48a1a04fe8dbf021b4cda1d.html
28 ms
140.61020b6c086bdb8bc696.js
5 ms
farnsworthproject.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
farnsworthproject.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
farnsworthproject.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Farnsworthproject.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 Farnsworthproject.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.
farnsworthproject.org
Open Graph data is detected on the main page of Farnsworth Project. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: