1.8 sec in total
285 ms
930 ms
597 ms
Click here to check amazing Luisdortiz Elliman content for United States. Otherwise, check out these important facts you probably never knew about luisdortiz.elliman.com
Browse our wide range of homes for sale and rent. Contact our real estate agents to find your dream home.
Visit luisdortiz.elliman.comWe analyzed Luisdortiz.elliman.com page load time and found that the first response time was 285 ms and then it took 1.5 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.
luisdortiz.elliman.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value18.6 s
0/100
25%
Value12.3 s
3/100
10%
Value5,320 ms
0/100
30%
Value0.126
83/100
15%
Value18.7 s
3/100
10%
285 ms
9 ms
45 ms
43 ms
39 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Luisdortiz.elliman.com, 43% (31 requests) were made to Aws.elliman.com and 32% (23 requests) were made to Resources-aws.elliman.com. The less responsive or slowest element that took the longest time to load (285 ms) belongs to the original domain Luisdortiz.elliman.com.
Page size can be reduced by 804.6 kB (14%)
5.6 MB
4.8 MB
In fact, the total size of Luisdortiz.elliman.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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 92.2 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 35.3 kB, which is 34% 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 92.2 kB or 90% of the original size.
Potential reduce by 301.2 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. Luisdortiz Elliman images are well optimized though.
Potential reduce by 411.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 411.2 kB or 77% of the original size.
Number of requests can be reduced by 14 (22%)
64
50
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Luisdortiz Elliman. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
luisdortiz.elliman.com
285 ms
ga.js
9 ms
core.css
45 ms
mootools.js
43 ms
core.js
39 ms
gml0xoe.js
88 ms
style.css
39 ms
script.js
31 ms
__utm.gif
55 ms
collect
103 ms
d
245 ms
logo.gif
69 ms
5e237156c4a11948b89f57c2099ce89bd7750059+440++0
100 ms
c09b73c963223f84f3d5081fa74fec76be68404c+440++0
103 ms
51f25a5005851a07b7ad976045a6034e07dff095+440++0
96 ms
c3086f99a654246bc86d237dcc3a1f27fff3c245+440++0
95 ms
c1f885fcffb67348c94dc4f8d5ed648b370ab754+440++0
107 ms
a21b036271da6066dae53cbd4ca3bfb6c02b5ad9+440++0
126 ms
e7f880fed6f6d1e4e325c9f181fe1333739c2675+440++0
104 ms
8b9d019751a63febf3a16d4f6f9926639b3940a6+440++0
103 ms
e62d14c6b3b26fa3d115d4bba90e32c07470488b+440++0
102 ms
8e1e61a592a30d8b103f100ed70a6b9ec1687320+440++0
106 ms
f61d3952acf6bb563d936b3db5fed7a46bbe2ae8+440++0
106 ms
bfb3bc26e7c2842f75abe238aa1abb8ae2b3a172+440++0
109 ms
d916c33c682784f0a02241517161e4d09a5d88e1+440++0
110 ms
5ec8d02cd80fcc10ae404a9bcaa2597ea0d2b94c+440++0
108 ms
ad509c232aa38b722cfe4a7b1fa4aa7e8f4e6356+440++0
120 ms
9b291a53cea5059bc3eece216dc952609c40351f+440++0
113 ms
join.gif
66 ms
spaceball_small.png
69 ms
icon_facebook.png
64 ms
icon_twitter.png
66 ms
icon_linkedin.png
67 ms
icon_instagram.png
68 ms
house.gif
66 ms
8c9fb3c5d2c3e072ce1da0dc11611a639a3d404f+w+h+1
70 ms
0ac74885856961c0dd046f385b4c6a63cd3e786a+w+h+1
84 ms
4feae9264d1b01591a5f9667ec2d486681a184a5+w+h+1
89 ms
988d84c7be48b4a15d82904f743f211aad3425e2+w+h+1
72 ms
dfa8ef8f3ea6bcfbbd958f948fcab6648e9fbf19+w+h+1
76 ms
57c373e47d763916e59b9d5c0051b35cb2ab11ae+w+h+1
94 ms
c610de4a40a42359ab189782558a0d9cd8f06b47+w+h+1
79 ms
e85424d27f1fe7b6f3c6388a83a782a21c3af468+w+h+1
86 ms
f8254ceb861ff23d2efdb46de2b0fc3e8b9c99e2+w+h+1
96 ms
5e2b843f750f2da5bab3f62b4917b4fded9d2589+w+h+1
84 ms
2ac60ab5c28bd0be2e3eedea8a92719f61f3df9f+w+h+1
110 ms
7646d6e3a95321320895d9c2e878f7dbdcf247dd+w+h+1
106 ms
a4fd10745a490d8f48eda48cb5e9c6c20d6463d2+w+h+1
103 ms
4a8c59bde4bea4f5aca1ac642721199118b75835+w+h+1
105 ms
af6de477028155bf36f57d7cf98bb1c8601290b1+w+h+1
107 ms
line.gif
19 ms
textfield_bg.gif
19 ms
menu_franklin.gif
16 ms
view_icons.png
21 ms
bg.gif
20 ms
tabs.gif
13 ms
tabs_r.gif
20 ms
hr.png
20 ms
info.png
22 ms
quant.js
31 ms
UA
78 ms
2bgfadqkngAAAA==
78 ms
t836BSb7nBIA
76 ms
t836BSb7nBIA
78 ms
T+m9yeLl6lYAAAA
77 ms
AzTYpiE=
76 ms
CTCommon.js
143 ms
space.png
51 ms
plusone.js
109 ms
pixel;r=536827117;a=p-7bfmzdfsiY5iI;fpan=1;fpa=P0-1261594809-1458404627196;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458404627196;tzo=-180;ref=;url=http%3A%2F%2Fluisdortiz.elliman.com%2F;ogl=
48 ms
p.gif
126 ms
cb=gapi.loaded_0
5 ms
luisdortiz.elliman.com 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-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
[aria-*] attributes do not have valid values
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
luisdortiz.elliman.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
luisdortiz.elliman.com 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Luisdortiz.elliman.com 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 Luisdortiz.elliman.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.
luisdortiz.elliman.com
Open Graph description is not detected on the main page of Luisdortiz Elliman. 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: