3.1 sec in total
391 ms
2.5 sec
245 ms
Welcome to sold.com homepage info - get ready to check SOLD best content for Colombia right away, or after learning these important things about sold.com
The Nation's Leading Online Marketplace for Buying and Selling Real Estate.
Visit sold.comWe analyzed Sold.com page load time and found that the first response time was 391 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.
sold.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value10.5 s
0/100
25%
Value3.5 s
87/100
10%
Value2,930 ms
3/100
30%
Value0.447
20/100
15%
Value15.7 s
6/100
10%
391 ms
297 ms
227 ms
58 ms
540 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sold.com, 12% (9 requests) were made to D.adroll.com and 5% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (540 ms) relates to the external source Cdn.auction.com.
Page size can be reduced by 574.0 kB (53%)
1.1 MB
514.4 kB
In fact, the total size of Sold.com main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 704.2 kB which makes up the majority of the site volume.
Potential reduce by 81.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 25.7 kB, which is 27% 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 81.3 kB or 86% of the original size.
Potential reduce by 25.5 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. SOLD images are well optimized though.
Potential reduce by 467.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 467.2 kB or 66% of the original size.
Number of requests can be reduced by 41 (67%)
61
20
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SOLD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
www.auction.com
391 ms
site3.8558eb1f.css
297 ms
homepage.f82b44d8.css
227 ms
752091841.js
58 ms
ext2.622fc9d1.js
540 ms
common3.710befd4.js
384 ms
homepage.41669b7c.js
228 ms
geo2.js
52 ms
event
46 ms
in-the-news-left.png
6 ms
in_the_news_1024.png
34 ms
in-the-news-right.png
19 ms
event
27 ms
munchkin-beta.js
345 ms
hotjar-45084.js
317 ms
analytics.js
331 ms
gtm.js
353 ms
gtm.js
396 ms
xhr
137 ms
9287aa41-4fff-42bd-99a3-ad780133b9c4.js
208 ms
logo-light.svg
178 ms
Homepage_Hero_Residential_2.jpg
174 ms
triangle_down_white.svg
154 ms
app_store_badge.svg
146 ms
social_facebook.svg
149 ms
social_twitter.svg
144 ms
social_google_plus.svg
242 ms
social_linked_in.svg
311 ms
social_you_tube.svg
308 ms
social_slide_share.svg
304 ms
search_white_large_28.png
154 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
80 ms
munchkin.js
30 ms
collect
25 ms
collect
84 ms
rd
44 ms
visitWebPage
441 ms
id
268 ms
ga-audiences
188 ms
conversion_async.js
206 ms
roundtrip.js
205 ms
bat.js
272 ms
getguid.php
268 ms
quant.js
188 ms
fbevents.js
186 ms
blank.gif
106 ms
78 ms
pixel;r=2127499425;a=p-ec2zPnDO4Fe1E;labels=_fp.event.Home%20Page;fpan=1;fpa=P0-161269192-1458193867887;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458193867886;tzo=-180;ref=;url=https%3A%2F%2Fwww.auction.com%2F;ogl=
82 ms
79 ms
81 ms
id
44 ms
s74945926428772
24 ms
25 ms
Q2JCQ4BAFBCRFAY5B2YRWD.js
36 ms
js
19 ms
i.js
232 ms
10 ms
out
11 ms
45 ms
out
18 ms
out
18 ms
out
25 ms
out
22 ms
out
34 ms
out
27 ms
out
31 ms
u.php
39 ms
adsct
179 ms
pixel
135 ms
98 ms
sync
12 ms
377928.gif
12 ms
in
6 ms
sd
27 ms
sold.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.
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.
sold.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
sold.com SEO score
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 Sold.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 Sold.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.
sold.com
Open Graph description is not detected on the main page of SOLD. 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: