Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

jfi.org

Jewish Film Institute: Presenter of the San Francisco Jewish Film Festival (SFJFF)

Page Load Speed

2.6 sec in total

First Response

170 ms

Resources Loaded

2 sec

Page Rendered

419 ms

jfi.org screenshot

About Website

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

The Jewish Film Institute (JFI) is the premier curatorial voice for Jewish film and media, a leading arts and culture organization in the Bay Area and presenter of the annual San Francisco Jewish Film...

Visit jfi.org

Key Findings

We analyzed Jfi.org page load time and found that the first response time was 170 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

jfi.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

jfi.org

170 ms

jfi.org

360 ms

styles

158 ms

igx-dev

240 ms

jquery-3.2.1

381 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 89% of them (25 requests) were addressed to the original Jfi.org, 7% (2 requests) were made to Googletagmanager.com and 4% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (861 ms) belongs to the original domain Jfi.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.3 kB (8%)

Content Size

7.5 MB

After Optimization

6.9 MB

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

HTML Optimization

-84%

Potential reduce by 37.8 kB

  • Original 45.0 kB
  • After minification 34.3 kB
  • After compression 7.2 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 10.6 kB, which is 24% 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 37.8 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 557.5 kB

  • Original 7.5 MB
  • After minification 6.9 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. Jfi images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 4 (16%)

Requests Now

25

After Optimization

21

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jfi. 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 as a result speed up the page load time.

Accessibility Review

jfi.org accessibility score

74

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 match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

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

jfi.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

jfi.org SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Jfi.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 Jfi.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 Jfi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: