1.5 sec in total
23 ms
1.2 sec
192 ms
Welcome to lrei.org homepage info - get ready to check Lrei best content for United States right away, or after learning these important things about lrei.org
LREI is a preK-12 coeducational independent school located in Greenwich Village, NYC. The diverse, creative community is a leader in progressive education.
Visit lrei.orgWe analyzed Lrei.org page load time and found that the first response time was 23 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster. This domain responded with an error, which can significantly jeopardize Lrei.org rating and web reputation
lrei.org performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value23.7 s
0/100
25%
Value23.5 s
0/100
10%
Value38,470 ms
0/100
30%
Value0.096
91/100
15%
Value53.4 s
0/100
10%
23 ms
408 ms
41 ms
47 ms
44 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 34% of them (32 requests) were addressed to the original Lrei.org, 42% (39 requests) were made to Cdn.media56.whipplehill.net and 9% (8 requests) were made to Farm2.staticflickr.com. The less responsive or slowest element that took the longest time to load (408 ms) belongs to the original domain Lrei.org.
Page size can be reduced by 373.6 kB (11%)
3.3 MB
2.9 MB
In fact, the total size of Lrei.org main page is 3.3 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 28.9 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 28.9 kB or 82% of the original size.
Potential reduce by 204.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. Lrei images are well optimized though.
Potential reduce by 124.2 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 124.2 kB or 60% of the original size.
Potential reduce by 15.6 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. Lrei.org needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 81% of the original size.
Number of requests can be reduced by 22 (24%)
90
68
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lrei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lrei.org
23 ms
www.lrei.org
408 ms
hp.css
41 ms
bulletin.css
47 ms
jscrollpane.css
44 ms
large_link307411_55706.jpg
61 ms
large_link318738_55549.jpg
60 ms
large_link280639_55581.jpg
57 ms
large_link318762_55577.jpg
67 ms
large_link334353_55707.jpg
59 ms
large_link294126_55568.jpg
59 ms
large_link328532_55580.jpg
74 ms
large_link334363_55584.jpg
73 ms
large_link316226_55583.jpg
70 ms
large_link307450_55571.jpg
72 ms
large_link318756_55555.jpg
73 ms
large_link278907_55588.jpg
83 ms
large_link334365_55582.jpg
84 ms
large_link330810_55587.jpg
104 ms
large_link307417_55567.jpg
85 ms
large_link318531_55586.jpg
88 ms
large_link301366_55547.jpg
84 ms
large_link282255_55574.jpg
94 ms
large_link402639_55546.jpg
99 ms
large_link402640_55551.jpg
89 ms
large_link402635_55569.jpg
91 ms
large_link281575_55548.jpg
94 ms
large_link402645_55572.jpg
96 ms
large_link598338_56097.jpg
136 ms
large_link448376_46861.jpg
94 ms
large_link448377_46986.png
97 ms
large_link448378_46985.png
128 ms
jquery.min.js
101 ms
willow.min.js
100 ms
jquery.pdsearch.js
113 ms
jquery.position.js
110 ms
jquery.bulletin.js
111 ms
jquery.menu.min.js
111 ms
BrightcoveExperiences.js
62 ms
jquery.jscrollpane.min.js
58 ms
jquery.cycle.all.min.js
63 ms
jquery.flickr.api.js
56 ms
jquery.mousewheel.js
56 ms
jquery.tmpl.min.js
56 ms
hp.js
56 ms
s_code_remote.js
59 ms
widgets.js
98 ms
large_link229684_39298.png
76 ms
large_link229685_39297.png
75 ms
large_link229686_39296.png
78 ms
searchBar.png
45 ms
topOverlay.png
49 ms
pagerBG.png
44 ms
linkArrow.png
38 ms
newsBG.png
39 ms
todayEventsBG.png
44 ms
fullCalendar.png
74 ms
feedsBG.png
79 ms
galleryBG.png
72 ms
footerBG.png
77 ms
footer.png
78 ms
nav1.png
85 ms
large_link229687_39294.png
72 ms
large_link365648_39300.png
73 ms
large_link234355_39299.png
72 ms
ga.js
42 ms
json.asp
136 ms
json.asp
54 ms
jquery.autocomplete.css
39 ms
jquery.autocomplete.min.js
37 ms
json.asp
254 ms
189 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
197 ms
__utm.gif
33 ms
searchBtn.png
28 ms
pagerOn.png
31 ms
pagerOff.png
29 ms
flyupBG.gif
19 ms
24757041263_1623572e91_s.jpg
117 ms
25016156159_aeeb9fe134_s.jpg
108 ms
25290729811_4dc9e2f351_s.jpg
121 ms
25016159499_a13aec96f5_s.jpg
130 ms
25088137910_2c4a5739c8_s.jpg
137 ms
25088146110_fab54625b1_s.jpg
126 ms
24753168804_25ab014fc2_s.jpg
133 ms
25088147970_0a9bdf81ef_s.jpg
131 ms
syndication
130 ms
357603092176461824
154 ms
feed
330 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
30 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
59 ms
195ea01430cd6130d38c7bfc84b03f51_normal.png
30 ms
cube_normal.jpg
32 ms
lrei.org accessibility score
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
ARIA input fields do not have accessible names
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
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>).
lrei.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lrei.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 Lrei.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 Lrei.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.
lrei.org
Open Graph description is not detected on the main page of Lrei. 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: