2.8 sec in total
13 ms
2.2 sec
571 ms
Visit better.com now to see the best up-to-date Better content for United States and also check out these interesting facts you probably never knew about better.com
Better Mortgage Corporation is a direct lender dedicated to providing a fast, transparent digital mortgage experience backed by superior customer support.
Visit better.comWe analyzed Better.com page load time and found that the first response time was 13 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
better.com performance score
name
value
score
weighting
Value1.8 s
88/100
10%
Value10.3 s
0/100
25%
Value7.8 s
24/100
10%
Value7,240 ms
0/100
30%
Value0
100/100
15%
Value19.7 s
2/100
10%
13 ms
44 ms
8 ms
31 ms
110 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 35% of them (25 requests) were addressed to the original Better.com, 11% (8 requests) were made to Static.olark.com and 6% (4 requests) were made to . The less responsive or slowest element that took the longest time to load (508 ms) relates to the external source D37gvrvc0wt4s1.cloudfront.net.
Page size can be reduced by 1.7 MB (67%)
2.5 MB
830.4 kB
In fact, the total size of Better.com main page is 2.5 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. 55% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 32.6 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 32.6 kB or 73% of the original size.
Potential reduce by 5.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. Better images are well optimized though.
Potential reduce by 900.8 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 900.8 kB or 69% of the original size.
Potential reduce by 722.1 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. Better.com needs all CSS files to be minified and compressed as it can save up to 722.1 kB or 83% of the original size.
Number of requests can be reduced by 35 (57%)
61
26
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Better. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
better.com
13 ms
better.com
44 ms
vendor-8eb9285fd31f3b7137a4fed4d106fcff.css
8 ms
mortgage-app-6e6195b6a4c6143363c0d62d28cb3591.css
31 ms
polyfill.min.js
110 ms
vendor-f73814c5612f8b18618ce0a6c7df3e06.js
101 ms
mortgage-app-06af5780f0534f930e823188eae2c931.js
86 ms
fonts.css
363 ms
index-285ee89dd5a80963f1acc4111266703a.css
42 ms
1B4B9A9F941BA4483.css
34 ms
rollbar.min.js
508 ms
loader0.js
462 ms
fbds.js
346 ms
ip-filter
334 ms
fs.js
441 ms
homepage1.jpg
232 ms
better-logo-grey.svg
69 ms
better-logo.svg
62 ms
stopwatch.svg
126 ms
communicate.svg
123 ms
sun-moon.svg
114 ms
100-online.svg
124 ms
house.svg
123 ms
trending.svg
186 ms
26-days.svg
184 ms
no.svg
188 ms
quote.svg
189 ms
arrow-right-orange.svg
188 ms
equal-housing.svg
240 ms
bbb.svg
237 ms
houses-pattern.svg
244 ms
homepage2.jpg
144 ms
6OdR3dyeE6KXy7JPvc=
13 ms
vw==
12 ms
ALhsP8M=
11 ms
10 ms
MaterialIcons-Regular.ttf
257 ms
icomoon.ttf
223 ms
analytics.min.js
209 ms
4430-415-10-5478.js
52 ms
124 ms
c
225 ms
page
419 ms
p
479 ms
conversion_async.js
109 ms
track.js
105 ms
fbevents.js
19 ms
analytics.js
89 ms
mixpanel-2-latest.min.js
217 ms
raven.min.js
115 ms
gtm.js
155 ms
prum.min.js
103 ms
67 ms
linkid.js
23 ms
44 ms
collect
10 ms
collect
62 ms
41 ms
ga-audiences
17 ms
55 ms
application2.js
128 ms
44 ms
page.gif
384 ms
activityi;src=5296301;type=bett0;cat=homep0;ord=5940152296214;~oref=https%3A%2F%2Fbetter.com%2F
88 ms
beacon.gif
134 ms
storage.html
39 ms
storage.js
28 ms
visits
213 ms
jquery.js
45 ms
b80a997c8771fb6ee707f72549a886f5.css
108 ms
s
102 ms
buttons-light.png
35 ms
better.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
button, link, and menuitem elements do not have accessible names.
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
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>).
better.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
better.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
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Better.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 Better.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.
better.com
Open Graph description is not detected on the main page of Better. 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: