3.6 sec in total
165 ms
2.9 sec
472 ms
Visit lff.com now to see the best up-to-date Lff content and also check out these interesting facts you probably never knew about lff.com
Visit lff.comWe analyzed Lff.com page load time and found that the first response time was 165 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lff.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value4.7 s
32/100
25%
Value7.3 s
29/100
10%
Value220 ms
87/100
30%
Value0.742
6/100
15%
Value7.0 s
53/100
10%
165 ms
163 ms
401 ms
54 ms
41 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lff.com, 88% (97 requests) were made to Lefkofskyfoundation.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (869 ms) relates to the external source Lefkofskyfoundation.com.
Page size can be reduced by 269.6 kB (13%)
2.1 MB
1.8 MB
In fact, the total size of Lff.com main page is 2.1 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 220.3 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 220.3 kB or 77% of the original size.
Potential reduce by 33.7 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. Lff images are well optimized though.
Potential reduce by 8.6 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 6.9 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. Lff.com has all CSS files already compressed.
Number of requests can be reduced by 31 (30%)
104
73
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
lff.com
165 ms
lefkofskyfoundation.com
163 ms
lefkofskyfoundation.com
401 ms
css2
54 ms
bootstrap.min.css
41 ms
all.css
57 ms
style.min.css
200 ms
styles.css
225 ms
style.css
281 ms
dashicons.min.css
378 ms
genericons.css
299 ms
font-awesome.min.css
241 ms
all.min.css
294 ms
style.css
313 ms
style.css
308 ms
aos.css
538 ms
open-iconic-bootstrap.css
428 ms
bootstrap.css
445 ms
style.css
414 ms
jquery.min.js
608 ms
jquery-migrate.min.js
484 ms
lff-app.js
483 ms
popper.min.js
48 ms
bootstrap.min.js
81 ms
aos.js
516 ms
js
73 ms
index.js
429 ms
index.js
445 ms
davidwalsh.js
467 ms
bootstrap.js
500 ms
hoverIntent.min.js
521 ms
maxmegamenu.js
560 ms
public.js
554 ms
lff-app.css
379 ms
lff_logo.png
99 ms
education.png
99 ms
human_rights.png
99 ms
medical.png
228 ms
arts_culture.png
228 ms
lff_logos_0060_Anderson-Ranch.png
227 ms
lff_logos_0064_Alzheimers-Drug-Discovery-Foundation.png
274 ms
lff_logos_0063_American-Brain-Tumor-Association.png
228 ms
lff_logos_0061_AMLE.png
228 ms
lff_logos_0057_Aspen-Art-Museum.png
341 ms
lff_logos_0059_Ann-Robert-Lurie-Childrens-Hospital.png
330 ms
lff_logos_0056_AUSL.png
439 ms
lff_logos_0049_Childrens-National-Hospital-Foundation.png
360 ms
lff_logos_0065_After-School-Matters.png
358 ms
lff_logos_0055_Broadway-Cares.png
325 ms
lff_logos_0048_Cleveland-Clinic.png
476 ms
center-for-reproductive-rights.png
485 ms
lff_logos_0051_Chicago-Public-Education-Fund.png
448 ms
lff_logos_0022_My-Chi.-My-Future-1.png
502 ms
lff_logos_0052_Chicago-Media-Project.png
453 ms
lff_logos_0050_Childrens-First-Fund.png
585 ms
lff_logos_0053_Chicago-Botanic-Gardens.png
609 ms
lff_logos_0046_Cradles-to-Crayons.png
665 ms
lff_logos_0047_Communities-in-Schools.png
580 ms
lff_logos_0042_Erikson-Institute.png
582 ms
lff_logos_0034_Joffrey-Ballet.png
595 ms
lff_logos_0043_Enlace.png
705 ms
lff_logos_0041_Everytown-for-Gun-Safety.png
675 ms
lff_logos_0039_Grantmakers-for-Thriving-Youth.png
721 ms
lff_logos_0023_Museum-of-Science-and-Industry.png
715 ms
lff_logos_0031_Lurie-Comprehensive-Cancer-Center.png
708 ms
lff_logos_0040_Fund-for-a-Safer-Future.png
769 ms
lff_logos_0038_Greenhouse-Scholars.png
768 ms
lff_logos_0036_Human-Rights-Watch.png
798 ms
lff_logos_0037_High-Jump.png
776 ms
lff_logos_0024_Museum-of-Contemporary-Art.png
791 ms
js
159 ms
analytics.js
199 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
197 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
199 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
199 ms
lff_logos_0033_Just-the-Pill.png
747 ms
lff_logos_0025_Millenium-Park-Foundation.png
791 ms
lff_logos_0029_MD-Anderson-Cancer-Center.png
747 ms
lff_logos_0035_Jewish-United-Fund.png
678 ms
lff_logos_0032_Kids-First-Chicago.png
687 ms
lff_logos_0019_Northwestern-University.png
706 ms
lff_logos_0027_Men-4-Choice.png
869 ms
lff_logos_0022_My-Chi.-My-Future.png
709 ms
lff_logos_0014_Ravinia.png
785 ms
collect
12 ms
lff_logos_0012_St.-Jude-Childrens-Research-Hospital.png
678 ms
lff_logos_0028_Medical-Missions-for-Children.png
744 ms
lff_logos_0018_OneGoal.png
788 ms
lff_logos_0010_Steppenwolf.png
669 ms
lff_logos_0011_Stanford-Medicine.png
786 ms
lff_logos_0026_Midwest-Access-Project.png
719 ms
lff_logos_0016_Pitch-In-Wood-Family-Foundation.png
715 ms
lff_logos_0009_The-Renaissance-Society.png
706 ms
lff_logos_0021_National-Institute-for-Reproductive-Health.png
710 ms
whitney.png
744 ms
lff_logos_0008_University-of-Chicago.png
731 ms
partnership_for_safe_and_peaceful_communities.png
669 ms
lff_logos_0001_Writers-Theater.png
687 ms
lff_logos_0007_University-of-Michigan-Health-Care-System.png
683 ms
lff_logos_0017_Peer-Health-Exchange.png
709 ms
lff_logos_0005_Urban-Initiatives.png
710 ms
lff_logos_0006_University-of-Pennsylvania.png
640 ms
lff_logos_0003_Weill-Cornell-Medical.png
667 ms
lff_logos_0013_Sexuality-Information-and-Education-Council-of-the-United-States-SIECUS.png
697 ms
lff_logos_0004_US-Holocaust-Museum.png
636 ms
lff_logos_0002_World-Central-Kitchen.png
803 ms
lff_logos_0000_YLabs.png
691 ms
sb_logo.png
723 ms
ving_logo.png
671 ms
hsb_logo.png
649 ms
lff.com 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
lff.com 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
Page has valid source maps
lff.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lff.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 Lff.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.
lff.com
Open Graph description is not detected on the main page of Lff. 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: