2.3 sec in total
55 ms
1.8 sec
404 ms
Welcome to elend.com homepage info - get ready to check Elend best content for United States right away, or after learning these important things about elend.com
Get a Custom Rate Quote Online
Visit elend.comWe analyzed Elend.com page load time and found that the first response time was 55 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.
elend.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value21.7 s
0/100
25%
Value16.0 s
0/100
10%
Value17,060 ms
0/100
30%
Value0
100/100
15%
Value33.4 s
0/100
10%
55 ms
48 ms
211 ms
217 ms
132 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 84% of them (112 requests) were addressed to the original Elend.com, 4% (6 requests) were made to and 1% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (499 ms) belongs to the original domain Elend.com.
Page size can be reduced by 623.2 kB (24%)
2.6 MB
1.9 MB
In fact, the total size of Elend.com main page is 2.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. 35% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 52.3 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 17.2 kB, which is 28% 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 52.3 kB or 84% of the original size.
Potential reduce by 18.4 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. Elend images are well optimized though.
Potential reduce by 341.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 341.6 kB or 74% of the original size.
Potential reduce by 210.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. Elend.com needs all CSS files to be minified and compressed as it can save up to 210.8 kB or 80% of the original size.
Number of requests can be reduced by 104 (86%)
121
17
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elend. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 95 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
elend.com
55 ms
www.elend.com
48 ms
www.elend.com
211 ms
xwv5fmn.js
217 ms
base.css
132 ms
font-awesome.min.css
112 ms
elend_fonts.css
70 ms
skeleton.css
131 ms
layout.css
87 ms
odometer-theme-minimal.css
104 ms
angular-dropdowns.css
153 ms
styles.css
162 ms
KJE.css
243 ms
KJESiteSpecific.css
154 ms
jquery-1.11.1.min.js
173 ms
base.js
107 ms
odometer.min.js
127 ms
js
97 ms
underscore-min.js
182 ms
angular.min.js
192 ms
angular-route.js
199 ms
angular-resource.js
214 ms
angular-touch.min.js
248 ms
mask.min.js
204 ms
angular-local-storage.min.js
250 ms
jquery.hoverIntent.js
283 ms
ng-swipe.js
248 ms
matchMedia.js
228 ms
angular-dropdowns.js
408 ms
elend-common.js
408 ms
elend.js
406 ms
tabs.js
282 ms
dropdowns.js
406 ms
angular-animate.min.js
405 ms
re-tree.min.js
412 ms
ng-device-detector.min.js
466 ms
window-scroll.js
432 ms
scroll-top.js
432 ms
toggle-open.js
431 ms
carousel-scroll.js
462 ms
hover-intent.js
430 ms
startsWith.js
430 ms
coBrandData.js
499 ms
mortgageTypes.js
473 ms
dataStorage.js
408 ms
afrServices.js
413 ms
coBrandService.js
412 ms
loadingService.js
410 ms
sharedService.js
409 ms
applicationService.js
422 ms
userService.js
386 ms
authService.js
446 ms
d
108 ms
gtm.js
39 ms
logo.png
259 ms
authInterceptorService.js
334 ms
alertService.js
334 ms
analytics.js
38 ms
zipCodeService.js
336 ms
munchkin.js
67 ms
partnerService.js
341 ms
adwordsService.js
337 ms
focusFirstService.js
332 ms
scrollService.js
324 ms
collect
37 ms
versioningService.js
301 ms
nativeHideMenuService.js
307 ms
formController.js
330 ms
mainController.js
369 ms
munchkin.js
25 ms
collect
173 ms
closingCostController.js
274 ms
visitWebPage
61 ms
confirmationController.js
187 ms
wP8NMs8I0O9Qcc80z3wILLbLYEksts9wKK62y2hprrZNlvQ022mRzyMRW22y3w0677LbHXvvsd8BBhxx2xFHHHHfCSaecdsbZkKnzLrjoksuuuJqXmBshWbdCbu646577HnjokWyPPZHjqWeeh1y+9Mprb7z1znsffPwFWVVzEQAA
32 ms
DTLPCNDvUHHPNM98CCy2y2BJLLbPcCiutstoaa62TZb0NNtpkc8jEVttst8NOu+y2x1777HfAQYccdsRRxxx3wkmnnHbG2ZCp8y646JLLrrial5gbIVm3Qm7uuOue+x546JFsjz2R46lnnodcvvTKa2+89c57H3z8BVlVcxEAAA==
32 ms
wP8NMs8I0O9Qcc80z3wILLbLYEksts9wKK62y2hprrZNlvQ022mRzyMRW22y3w0677LbHXvvsd8BBhxx2xFHHHHfCSaecdsbZkKnzLrjoksuuuJqXmBshWbdCbu646577HnjokWyPPZHjqWeeh1y+9Mprb7z1znsffPwFWVVzEQAA
32 ms
DTLPCNDvUHHPNM98CCy2y2BJLLbPcCiutstoaa62TZb0NNtpkc8jEVttst8NOu+y2x1777HfAQYccdsRRxxx3wkmnnHbG2ZCp8y646JLLrrial5gbIVm3Qm7uuOue+x546JFsjz2R46lnnodcvvTKa2+89c57H3z8BVlVcxEAAA==
31 ms
wP8NMs8I0O9Qcc80z3wILLbLYEksts9wKK62y2hprrZNlvQ022mRzyMRW22y3w0677LbHXvvsd8BBhxx2xFHHHHfCSaecdsbZkKnzLrjoksuuuJqXmBshWbdCbu646577HnjokWyPPZHjqWeeh1y+9Mprb7z1znsffPwFWVVzEQAA
31 ms
wP8NMs8I0O9Qcc80z3wILLbLYEksts9wKK62y2hprrZNlvQ022mRzyMRW22y3w0677LbHXvvsd8BBhxx2xFHHHHfCSaecdsbZkKnzLrjoksuuuJqXmBshWbdCbu646577HnjokWyPPZHjqWeeh1y+9Mprb7z1znsffPwFWVVzEQAA
30 ms
searchResultsController.js
229 ms
homePageHeroController.js
172 ms
heroGetMyRateController.js
249 ms
heroApplyController.js
244 ms
blogCategories.js
184 ms
closingCostDetails.js
186 ms
coBrandHero.js
187 ms
disclaimer.js
188 ms
estimatedPrepaidEscrow.js
203 ms
p.gif
137 ms
getMyRate.js
207 ms
getTodaysRate.js
208 ms
governmentTaxesFees.js
220 ms
ga-audiences
44 ms
initialFeesWorksheet.js
198 ms
loanDescription.js
202 ms
miniDash.js
199 ms
mobileMenuClick.js
208 ms
mobileMenuToggle.js
195 ms
modalDirective.js
197 ms
passwordComplexityDetails.js
196 ms
partnerPhoneDirective.js
190 ms
scrollToGmr.js
183 ms
searchResults.js
193 ms
searchResultsHeader.js
193 ms
socialShare.js
194 ms
submitAction.js
185 ms
termGlossary.js
207 ms
thirdPartyDescription.js
185 ms
capitalizeDirective.js
190 ms
zipCodeDirective.js
191 ms
strictEmailDirective.js
183 ms
homePageHero.js
178 ms
heroGetMyRate.js
185 ms
heroApplyDirective.js
178 ms
questionButtonDirective.js
179 ms
questionDirective.js
192 ms
compareToDirective.js
160 ms
complexPasswordDirective.js
159 ms
markSectionCompleteDirective.js
215 ms
bbb_footer_logo.png
170 ms
equal-housing-lender.png
171 ms
home-page-hero.html
49 ms
modalDirective.html
36 ms
WaitScreenSpinner.gif
429 ms
hero_home.jpg
204 ms
eLEND-custom.woff
146 ms
fontawesome-webfont.woff
219 ms
home-01-lg.jpg
397 ms
get-todays-rate.html
25 ms
hero-apply.html
49 ms
hero-get-my-rate.html
121 ms
TickerRate
237 ms
nr-892.min.js
89 ms
elend.com accessibility score
elend.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
elend.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 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 Elend.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 Elend.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.
elend.com
Open Graph description is not detected on the main page of Elend. 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: