1.1 sec in total
76 ms
877 ms
167 ms
Visit 160leroy.com now to see the best up-to-date 160 Leroy content and also check out these interesting facts you probably never knew about 160leroy.com
160 Leroy is your last chance to own a home on the water in the West Village. One- to four-bedroom condos and penthouse available. Concept by Ian Schrager.
Visit 160leroy.comWe analyzed 160leroy.com page load time and found that the first response time was 76 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
160leroy.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value8.6 s
1/100
25%
Value5.9 s
48/100
10%
Value460 ms
62/100
30%
Value0
100/100
15%
Value10.7 s
22/100
10%
76 ms
66 ms
36 ms
34 ms
34 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 89% of them (34 requests) were addressed to the original 160leroy.com, 5% (2 requests) were made to Cdnjs.cloudflare.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (208 ms) belongs to the original domain 160leroy.com.
Page size can be reduced by 72.6 kB (1%)
7.4 MB
7.3 MB
In fact, the total size of 160leroy.com main page is 7.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. 60% of websites need less resources to load. Images take 7.2 MB which makes up the majority of the site volume.
Potential reduce by 57.8 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.8 kB, which is 15% 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 57.8 kB or 81% of the original size.
Potential reduce by 498 B
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. 160 Leroy images are well optimized though.
Potential reduce by 10.4 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 10.4 kB or 21% of the original size.
Potential reduce by 3.8 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. 160leroy.com needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 27% of the original size.
Number of requests can be reduced by 15 (43%)
35
20
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 160 Leroy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.160leroy.com
76 ms
gtm.js
66 ms
swiper.min.css
36 ms
normalize.css
34 ms
syntax.css
34 ms
application.css
58 ms
jquery-2.2.3.min.js
24 ms
jquery.lazy.min.js
43 ms
modernizr.js
62 ms
application.js
63 ms
swiper.jquery.min.js
46 ms
home.js
78 ms
intro-logo.png
149 ms
intro-text.png
40 ms
icon-loading.png
18 ms
logo-160.png
23 ms
icon-nav.png
21 ms
concept-hero-from-river-01.jpg
25 ms
residence-courtyard-entrance.jpg
24 ms
Amenities_Courtyard-from-Lobby_1.jpg
55 ms
residence-floating-hero.jpg
50 ms
concept-hero-detail-01.jpg
75 ms
Residence-Livingroom_1.jpg
42 ms
Residence-Bedroom_1.jpg
51 ms
Residence_Master-Bathroom_1.jpg
71 ms
Residence_UnitE_Kitchen_1.jpg
65 ms
Residence_UnitE_Kitchen-Larder_1.jpg
82 ms
Residence_PH-Rooftop_1.jpg
78 ms
icon-arrow-right.png
80 ms
icon-arrow-left.png
88 ms
icon-add.png
88 ms
icon-information.png
99 ms
icon-fact-sheet.png
106 ms
icon-close.png
104 ms
icon-accordion-arrow-inactive.png
104 ms
icon-expand.png
105 ms
2F1EBB_4_0.woff
175 ms
2F1EBB_5_0.woff
208 ms
160leroy.com accessibility score
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
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
160leroy.com 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
Page has valid source maps
160leroy.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 160leroy.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 160leroy.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.
160leroy.com
Open Graph description is not detected on the main page of 160 Leroy. 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: