9.3 sec in total
1.1 sec
7.7 sec
453 ms
Visit can-ho.vn now to see the best up-to-date Can Ho content for Vietnam and also check out these interesting facts you probably never knew about can-ho.vn
can-ho.vn trang mua bán đất Lâm Đồng chính chủ, giá rẻ [TIME thang/nam]. Đa dạng các loại hình như đất đền, đất thổ cư, nông nghiệp với giá mới nhất.
Visit can-ho.vnWe analyzed Can-ho.vn page load time and found that the first response time was 1.1 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
can-ho.vn performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value5.1 s
25/100
25%
Value10.9 s
6/100
10%
Value3,150 ms
2/100
30%
Value0.001
100/100
15%
Value15.3 s
7/100
10%
1115 ms
45 ms
1866 ms
1654 ms
1076 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 61% of them (43 requests) were addressed to the original Can-ho.vn, 24% (17 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Can-ho.vn.
Page size can be reduced by 208.7 kB (4%)
5.5 MB
5.3 MB
In fact, the total size of Can-ho.vn main page is 5.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. 70% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 72.0 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 72.0 kB or 80% of the original size.
Potential reduce by 25.9 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. Can Ho images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 109.0 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. Can-ho.vn needs all CSS files to be minified and compressed as it can save up to 109.0 kB or 88% of the original size.
Number of requests can be reduced by 24 (47%)
51
27
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Can Ho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
can-ho.vn
1115 ms
css
45 ms
css.css
1866 ms
jquery.js
1654 ms
script.min.js
1076 ms
api.js
48 ms
animate.css
1583 ms
wow.min.js
1080 ms
font-awesome.min.css
1353 ms
fontawesome-all.min.js
5632 ms
jquery.fancybox.css
1351 ms
jquery.fancybox.pack.js
1879 ms
jquery.fancybox-thumbs.css
1707 ms
jquery.fancybox-thumbs.js
1712 ms
jquery.navHighlighter.js
1866 ms
sticky-kit.min.js
1866 ms
frame_script.js
1897 ms
jquery.fancybox.css
1981 ms
jquery.fancybox.js
4120 ms
platform.js
34 ms
popper.min.js
23 ms
bootstrap.min.js
26 ms
css2
20 ms
gtm.js
147 ms
logo-white.png
488 ms
menu_mobile.png
494 ms
icon_6.png
505 ms
86eaec8f38829bdcc293.jpg
2165 ms
z5550360541668-d58f719c99aa4936ed31e070a92c297e-jpg-1718696744-.jpg
1793 ms
z5550355880390-7e02b4cff2b49a9dabb9486b476e656d-jpg-1718696747-.jpg
2909 ms
z5550355895819-ffa8c6419bd17d9cdcae06ca06372a1e-jpg-1718696746-.jpg
2558 ms
z5550355906862-ac5755e8abc2cbf83621379a8cae160e-jpg-1718696745-.jpg
2764 ms
avt.jpg
3756 ms
ti_fixed_3_t.png
2738 ms
z5550292647555-333a88df492ddaaf5db06afcc2b75eb3-jpg-1718694589-.jpg
3469 ms
325586599-707489244371705-8746539418755966475-n-jpg-1718602874-.jpg
4953 ms
62ba348f0019a047f9084-jpg-1718602873-.jpg
3982 ms
09b3f6d2c344631a3a552-jpg-1718602875-.jpg
4043 ms
1a3f535e66c8c6969fd91-jpg-1718602875-.jpg
4650 ms
icon_1.png
4030 ms
icon_2.png
4255 ms
icon_4.png
4299 ms
icon_5.png
4324 ms
icon_3.png
4306 ms
logo-bidv-jpg-20240315164122pCHoK3Fns.jpg
4571 ms
logo-mb-new-png-202403151622161E7LOQJWha.png
4612 ms
ti_fixed_3.png
4569 ms
recaptcha__en.js
73 ms
KFOmCnqEu92Fr1Me5Q.ttf
71 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
153 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
165 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
170 ms
KFOkCnqEu92Fr1Mu52xP.ttf
170 ms
KFOjCnqEu92Fr1Mu51S7ABc9.ttf
170 ms
KFOjCnqEu92Fr1Mu51TjARc9.ttf
168 ms
KFOjCnqEu92Fr1Mu51TzBhc9.ttf
164 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WCzsW_LA.ttf
184 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WCwkW_LA.ttf
186 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC2UW_LA.ttf
186 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC7sW_LA.ttf
184 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WCzsX_LA.ttf
186 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC-UR_LA.ttf
186 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC9wR_LA.ttf
186 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC7sR_LA.ttf
187 ms
wlptgwvFAVdoq2_F94zlCfv0bz1WC5IR_LA.ttf
186 ms
arrown_menu_accordion.png
4519 ms
fontawesome-webfont.woff
4783 ms
can-ho.vn
4090 ms
sdk.js
57 ms
sdk.js
7 ms
can-ho.vn 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
can-ho.vn 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
can-ho.vn 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Can-ho.vn can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Can-ho.vn 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.
can-ho.vn
Open Graph data is detected on the main page of Can Ho. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: