Tools & Wizards About Us
lpef.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

lpef.org

Education Non Profit | Los Gatos | LPEF - Loma Public Education Fund

Page Load Speed

4 sec in total

First Response

1.2 sec

Resources Loaded

2.6 sec

Page Rendered

213 ms

lpef.org screenshot

About Website

Visit lpef.org now to see the best up-to-date LPEF content and also check out these interesting facts you probably never knew about lpef.org

Loma Public Education Fund is a Los Gatos non profit who sole mission is to support Loma Prieta Elementary and CT English Middle School through fundraising.

Visit lpef.org

Key Findings

We analyzed Lpef.org page load time and found that the first response time was 1.2 sec and then it took 2.8 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

lpef.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value14,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.2 s

1/100

10%

Network Requests Diagram

www.lpef.org

1217 ms

minified.js

197 ms

focus-within-polyfill.js

359 ms

polyfill.min.js

359 ms

bootstrap-features.24d4529b.bundle.min.js

384 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Lpef.org, 66% (21 requests) were made to Static.parastorage.com and 19% (6 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lpef.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 502.6 kB (68%)

Content Size

739.0 kB

After Optimization

236.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Lpef.org main page is 739.0 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. 60% of websites need less resources to load. HTML takes 531.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 418.0 kB

  • Original 531.7 kB
  • After minification 530.0 kB
  • After compression 113.7 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 418.0 kB or 79% of the original size.

Image Optimization

-52%

Potential reduce by 84.5 kB

  • Original 163.5 kB
  • After minification 79.0 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. Obviously, LPEF needs image optimization as it can save up to 84.5 kB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 48 B

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

Requests Breakdown

Number of requests can be reduced by 9 (39%)

Requests Now

23

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lpef.org

www.lpef.org

1217 ms

minified.js

minified.js

197 ms

focus-within-polyfill.js

focus-within-polyfill.js

359 ms

polyfill.min.js

polyfill.min.js

359 ms

bootstrap-features.24d4529b.bundle.min.js

bootstrap-features.24d4529b.bundle.min.js

384 ms

main.24eb524d.bundle.min.js

main.24eb524d.bundle.min.js

377 ms

lodash.min.js

lodash.min.js

376 ms

react.production.min.js

react.production.min.js

382 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

373 ms

thunderbolt

thunderbolt

786 ms

wix-perf-measure.bundle.min.js

wix-perf-measure.bundle.min.js

338 ms

react-dom.production.min.js

react-dom.production.min.js

764 ms

LPEF_logo1-1.jpg

LPEF_logo1-1.jpg

1113 ms

web-photos-button.jpg

web-photos-button.jpg

1111 ms

keep22.jpg

keep22.jpg

1113 ms

KEEP-thermometer-8.jpg

KEEP-thermometer-8.jpg

1113 ms

Screen%20Shot%202020-02-03%20at%2011_31_48%20AM_pn.png

Screen%20Shot%202020-02-03%20at%2011_31_48%20AM_pn.png

1127 ms

6d1a3bf766a5407f8b9aa0f7e9342d43.jpg

6d1a3bf766a5407f8b9aa0f7e9342d43.jpg

1111 ms

ironpatern.6522082f.png

ironpatern.6522082f.png

625 ms

thunderbolt

thunderbolt

234 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

44 ms

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

43 ms

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

33 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

44 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

43 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

44 ms

opensans-bolditalic-webfont.woff

opensans-bolditalic-webfont.woff

61 ms

opensans-italic-webfont.woff

opensans-italic-webfont.woff

59 ms

deprecation-en.v5.html

deprecation-en.v5.html

13 ms

bolt-performance

bolt-performance

56 ms

deprecation-style.v5.css

deprecation-style.v5.css

10 ms

right-arrow.svg

right-arrow.svg

8 ms

Accessibility Review

lpef.org accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

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

lpef.org best practices score

92

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

Page has valid source maps

SEO Factors

lpef.org SEO score

93

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

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

lpef.org

Open Graph data is detected on the main page of LPEF. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: