Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

farnsworthproject.org

R esearch by the Trust and its consultants has proven that flooding is an increasing threat to Farnsworth House.

Page Load Speed

32.3 sec in total

First Response

15 ms

Resources Loaded

30 sec

Page Rendered

2.3 sec

farnsworthproject.org screenshot

About Website

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

Key Findings

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

Performance Metrics

farnsworthproject.org performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value14,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

farnsworthproject.org

15 ms

110 ms

9988 ms

wp-emoji-release.min.js

114 ms

simple-banner.css

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 Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (43%)

Content Size

2.4 MB

After Optimization

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.

HTML Optimization

-86%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 166.6 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 1.0 MB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 13.1 kB

  • Original 1.2 MB
  • After minification 1.1 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. Farnsworth Project images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 1.1 kB

  • Original 24.4 kB
  • After minification 24.4 kB
  • After compression 23.4 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.

CSS Optimization

-12%

Potential reduce by 3.7 kB

  • Original 31.0 kB
  • After minification 31.0 kB
  • After compression 27.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. 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.

Requests Breakdown

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

Requests Now

84

After Optimization

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.

Accessibility Review

farnsworthproject.org accessibility score

88

Accessibility Issues

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.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

farnsworthproject.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

farnsworthproject.org SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

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

Social Sharing Optimization

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: