1.7 sec in total
38 ms
1.3 sec
324 ms
Visit lexingtonchicago.com now to see the best up-to-date Lexington Chicago content for United States and also check out these interesting facts you probably never knew about lexingtonchicago.com
Find new home communities near Chicago, IL, including new homes for sale in Glenview, Arlington Heights, Warrenville. See our floorplans today
Visit lexingtonchicago.comWe analyzed Lexingtonchicago.com page load time and found that the first response time was 38 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
lexingtonchicago.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value33.1 s
0/100
25%
Value13.8 s
1/100
10%
Value11,070 ms
0/100
30%
Value0.001
100/100
15%
Value38.6 s
0/100
10%
38 ms
337 ms
58 ms
27 ms
11 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 46% of them (52 requests) were addressed to the original Lexingtonchicago.com, 9% (10 requests) were made to D.adroll.com and 7% (8 requests) were made to Static.trulia-cdn.com. The less responsive or slowest element that took the longest time to load (363 ms) relates to the external source S.adroll.com.
Page size can be reduced by 1.6 MB (29%)
5.6 MB
4.0 MB
In fact, the total size of Lexingtonchicago.com main page is 5.6 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. 85% 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 31.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 8.2 kB, which is 20% 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 31.8 kB or 79% of the original size.
Potential reduce by 301.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. Lexington Chicago images are well optimized though.
Potential reduce by 762.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 762.6 kB or 69% of the original size.
Potential reduce by 508.4 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. Lexingtonchicago.com needs all CSS files to be minified and compressed as it can save up to 508.4 kB or 80% of the original size.
Number of requests can be reduced by 59 (63%)
94
35
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lexington Chicago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
lexingtonchicago.com
38 ms
www.lexingtonchicago.com
337 ms
bootstrap.min.css
58 ms
font-awesome.min.css
27 ms
jquery.mCustomScrollbar.min.css
11 ms
regular.css
13 ms
demibold.css
14 ms
lexington.css
14 ms
lexington-mobile-icons.css
14 ms
global.css
15 ms
header.css
19 ms
footer.css
26 ms
animate.css
28 ms
index.css
19 ms
pg_truliatool-generate.css
46 ms
jquery-1.10.2.min.js
98 ms
bootstrap.min.js
21 ms
jquery.validate.min.js
41 ms
jquery.spin.js
29 ms
jquery.cookie.js
30 ms
jquery.touchSwipe.min.js
30 ms
velocity.min.js
38 ms
velocity.ui.js
32 ms
jquery.mCustomScrollbar.concat.min.js
33 ms
global.js
38 ms
jquery.liveperson.js
40 ms
index.js
45 ms
css
26 ms
Guildquality.gif
186 ms
pencil.png
159 ms
logo-white.png
160 ms
slide-1.jpg
168 ms
slide-1-box.png
160 ms
slide-1-banner.png
163 ms
slide-1-text-2.png
160 ms
slide-1-text-3.png
163 ms
slide-3.jpg
170 ms
slide-3-seal.png
163 ms
slide-4.jpg
172 ms
slide-5.jpg
175 ms
arrow-left.png
164 ms
arrow-right.png
165 ms
cloud.png
167 ms
lexington-crossing-elevation-image-for-website-2.jpg
169 ms
lex-place-street-shot-9.jpg
169 ms
lexington-square.jpg
172 ms
tag.js
172 ms
js
82 ms
analytics.js
82 ms
gtm.js
84 ms
update.js
81 ms
slide-3-box.png
89 ms
slide-4-box.png
86 ms
slide-5-box.png
91 ms
none
85 ms
GCgb7bssGpwp7V5ynxmWy-YDkGZU0bw2OXG1Ku08t6E.ttf
80 ms
AvenirNextCondensed-Regular.woff
80 ms
lexington-icons.woff
78 ms
fontawesome-webfont.woff
79 ms
AvenirNextCondensed-DemiBold.woff
80 ms
embedded
178 ms
collect
35 ms
roundtrip.js
31 ms
.jsonp
65 ms
in.php
323 ms
storage.min.html
316 ms
22356471
73 ms
zones
282 ms
ga-audiences
284 ms
sbase-html5.css
6 ms
typography.css
52 ms
lib-oocss.css
36 ms
pg_truliatool-iframe.css
61 ms
pg_truliatool-iframe-calculator.css
60 ms
first_step.js
63 ms
site_js.js
165 ms
iframe.js
165 ms
iframe_calculator.js
59 ms
F7X6J6L4ZRFR7B4CJDEQGT.js
363 ms
22356471
149 ms
OpenSans-Regular-webfont.woff
124 ms
OpenSans-Semibold-webfont.woff
112 ms
OpenSans-Light-webfont.woff
112 ms
OpenSans-Bold-webfont.woff
112 ms
rta.js
72 ms
22356471
12 ms
UISuite.js
25 ms
overlay.js
28 ms
46
10 ms
live_chat_online_white.png
6 ms
22356471
6 ms
fbevents.hashing.js
101 ms
out
13 ms
32 ms
out
9 ms
out
11 ms
out
13 ms
out
14 ms
out
16 ms
out
17 ms
out
17 ms
out
17 ms
u.php
36 ms
adsct
126 ms
36 ms
bounce
46 ms
sd
25 ms
377928.gif
20 ms
u.php
70 ms
pixel
33 ms
tap.php
28 ms
19 ms
in
8 ms
mapuser
11 ms
lexingtonchicago.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
Form elements do not have associated labels
Links do not have a discernible name
lexingtonchicago.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lexingtonchicago.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexingtonchicago.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 Lexingtonchicago.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.
lexingtonchicago.com
Open Graph description is not detected on the main page of Lexington Chicago. 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: