8.1 sec in total
146 ms
7.5 sec
439 ms
Welcome to legacy.bhgre.com homepage info - get ready to check Legacy Bhgre best content for United States right away, or after learning these important things about legacy.bhgre.com
Let Better Homes and Gardens Real Estate Legacy help you find the home of your dreams. Browse listings, view photos, and connect with an agent today.
Visit legacy.bhgre.comWe analyzed Legacy.bhgre.com page load time and found that the first response time was 146 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
legacy.bhgre.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value20.0 s
0/100
25%
Value10.8 s
6/100
10%
Value4,010 ms
1/100
30%
Value0.014
100/100
15%
Value19.8 s
2/100
10%
146 ms
1029 ms
136 ms
209 ms
519 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Legacy.bhgre.com, 13% (10 requests) were made to Images-mls.static-ziprealty.com and 11% (8 requests) were made to Images.static-ziprealty.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Images.static-ziprealty.com.
Page size can be reduced by 1.7 MB (53%)
3.2 MB
1.5 MB
In fact, the total size of Legacy.bhgre.com main page is 3.2 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. 75% 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 66.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 14.7 kB, which is 18% 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 66.3 kB or 80% of the original size.
Potential reduce by 1.5 MB
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. Obviously, Legacy Bhgre needs image optimization as it can save up to 1.5 MB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 63.9 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 63.9 kB or 41% of the original size.
Potential reduce by 66.7 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. Legacy.bhgre.com needs all CSS files to be minified and compressed as it can save up to 66.7 kB or 48% of the original size.
Number of requests can be reduced by 34 (55%)
62
28
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy Bhgre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
legacy.bhgre.com
146 ms
better-homes-and-gardens-real-estate-legacy-7221c
1029 ms
zaplabs-common.js
136 ms
zaplabs-common.js
209 ms
zaplabs-common.js
519 ms
global-all.css
175 ms
theme_bhgre.css
247 ms
js
108 ms
splitioRunner.min.js
173 ms
ccm_gtm_event.js
176 ms
notice
171 ms
global.min.js
513 ms
analytics.js
536 ms
gtm.js
534 ms
fbevents.js
875 ms
4716330901
1075 ms
splitChanges
999 ms
277327_P00.jpg
3069 ms
medium.jpeg
4104 ms
1071 ms
ahs-logo-white-rgb.png
457 ms
277118_P00.jpg
3010 ms
277189_P00.jpg
3009 ms
277030_P00.jpg
3012 ms
276873_P00.jpg
3010 ms
276776_P00.jpg
3240 ms
73efaf78-44d6-4d0a-9924-7f67c572972a.jpg
3238 ms
276445_P00.jpg
3239 ms
276601_P00.jpg
3238 ms
277189_P00.jpg
3238 ms
apple_app_store.png
3007 ms
en_app_rgb_wo_45.png
3238 ms
mobile.png
3279 ms
company_logo_Horizontal.png
3238 ms
logo.png
3235 ms
conversion_async.js
2959 ms
cover_photo.jpg
3304 ms
zip-icons.woff
3163 ms
local-insights
2485 ms
collect
347 ms
collect
2788 ms
collect
2280 ms
1027511444315966
2306 ms
gpt.js
2747 ms
js_visitor_settings.php
2899 ms
splitChanges
2288 ms
2686 ms
4716330901
2604 ms
pixel
1230 ms
zaplabs-common.js
866 ms
yahoo-dom-event.js
511 ms
ziprealty-core.js
511 ms
610 ms
691 ms
565 ms
559 ms
885 ms
pubads_impl_2022092701.js
513 ms
ppub_config
643 ms
js_visitor_settings.php
89 ms
403 ms
v.gif
398 ms
rubicon
527 ms
195 ms
190 ms
189 ms
192 ms
v.gif
188 ms
appnexus
20 ms
rubicon
26 ms
rubicon
25 ms
generic
8 ms
rum
1355 ms
rum
1345 ms
generic
5 ms
legacy.bhgre.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-*] attributes do not match their roles
[role]s do not have all required [aria-*] attributes
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
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
[id] attributes on active, focusable elements are not unique
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>).
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.
legacy.bhgre.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
legacy.bhgre.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Legacy.bhgre.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 Legacy.bhgre.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.
legacy.bhgre.com
Open Graph data is detected on the main page of Legacy Bhgre. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: