2.3 sec in total
167 ms
1.6 sec
575 ms
Welcome to lfhs.org homepage info - get ready to check LFHS best content right away, or after learning these important things about lfhs.org
Visit lfhs.orgWe analyzed Lfhs.org page load time and found that the first response time was 167 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
lfhs.org performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value21.0 s
0/100
25%
Value13.3 s
2/100
10%
Value750 ms
39/100
30%
Value0.041
99/100
15%
Value22.3 s
1/100
10%
167 ms
42 ms
671 ms
30 ms
9 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lfhs.org, 78% (76 requests) were made to Lakeforestschools.org and 8% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (671 ms) relates to the external source Lakeforestschools.org.
Page size can be reduced by 872.1 kB (26%)
3.4 MB
2.5 MB
In fact, the total size of Lfhs.org main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 79.1 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 79.1 kB or 79% of the original size.
Potential reduce by 243.9 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. LFHS images are well optimized though.
Potential reduce by 386.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 386.9 kB or 74% of the original size.
Potential reduce by 162.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. Lfhs.org needs all CSS files to be minified and compressed as it can save up to 162.3 kB or 84% of the original size.
Number of requests can be reduced by 45 (54%)
84
39
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LFHS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
lfhs.org
167 ms
lfhs
42 ms
index.aspx
671 ms
dc.js
30 ms
jquery.min.js
9 ms
base.css
46 ms
twitter_footer.js
47 ms
gallery.css
54 ms
calendar.css
56 ms
news.css
66 ms
Classic.css
47 ms
jquery.prettyphoto.css
72 ms
thickbox.css
55 ms
WebResource.axd
69 ms
ImageList.js
65 ms
jquery.prettyPhoto.js
77 ms
Html5Media.js
76 ms
jquery.thickbox.js
75 ms
WysiwygFileLibrary.js
78 ms
CEFileLibrary.js
76 ms
CEEncodingFix.js
81 ms
ScriptResource.axd
109 ms
ScriptResource.axd
104 ms
ScriptResource.axd
102 ms
CombineScriptsHandler.ashx
121 ms
enquire2.1.0.min.js
89 ms
appendAround.js
92 ms
responsive.css
111 ms
schools.css
107 ms
imagesloaded.pkgd.min.js
117 ms
masonry.pkgd.min.js
118 ms
jquery.carouFredSel-6.2.0.js
122 ms
enquire.min.js
121 ms
school.js
132 ms
HttpCombineHandler.ashx
139 ms
DivWebPartZone.min.js
125 ms
reset.css
108 ms
fonts.css
110 ms
structure.css
119 ms
navigation.css
125 ms
html.css
133 ms
misc.css
143 ms
module.css
133 ms
css
26 ms
css
37 ms
css
47 ms
css
47 ms
print.css
80 ms
__utm.gif
50 ms
sdk.js
46 ms
css
22 ms
body.jpg
214 ms
container.jpg
49 ms
border.gif
51 ms
schoolfront3.jpg
217 ms
LFOH_026414.jpg
226 ms
LFHS_0236.jpg
227 ms
lk_forest_1620_yb3.jpg
227 ms
IMG_2375.jpg
227 ms
Applause_2016_LFHS_ILMEA_AllState2.jpg
230 ms
LFOH_BKGV_012.jpg
234 ms
LFOH__219.jpg
331 ms
Go_SCOUTS2.jpg
270 ms
lfhsmobile.jpg
315 ms
lg-scioly.jpg
311 ms
xlg-eday1.jpg
321 ms
lg-herestoyou.jpg
306 ms
lg-foundation_planting.tiff
305 ms
lg-project_safe_prom_2016.jpg
334 ms
lg-ap.jpg
337 ms
lg-Applause_2016_Honors_Winners_11.png
418 ms
lg-TEDxLFHS_White_Large.png
365 ms
lfhs.jpg
335 ms
lfhs-body.gif
339 ms
lfhs-border.gif
343 ms
lf115-logo.png
344 ms
nav.png
360 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
27 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
29 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
1KlmlHXZHUehH22N_q86AA.woff
29 ms
Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff
28 ms
b9QBgL0iMZfDSpmcXcE8nCSLrGe-fkSRw2DeVgOoWcQ.woff
27 ms
fontawesome-webfont.woff
349 ms
entypo.woff
358 ms
315 ms
AgXDSqZJmy12qS0ixjs6V3hCUOGz7vYGh680lGh-uXM.woff
17 ms
xd_arbiter.php
134 ms
xd_arbiter.php
139 ms
button.gif
312 ms
exclamation.png
283 ms
footer.jpg
313 ms
fs-powered-white.svg
314 ms
loadingAnimation.gif
200 ms
button-gold.gif
202 ms
ribbet.png
205 ms
lfhs.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
lfhs.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
lfhs.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lfhs.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lfhs.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lfhs.org
Open Graph description is not detected on the main page of LFHS. 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: