Tools & Wizards About Us
sango.us screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

sango.us

Tổng kho sàn gỗ, sàn nhựa, sàn gỗ ngoài trời giá rẻ

Page Load Speed

27.7 sec in total

First Response

640 ms

Resources Loaded

26.5 sec

Page Rendered

570 ms

sango.us screenshot

About Website

Visit sango.us now to see the best up-to-date Sango content for Vietnam and also check out these interesting facts you probably never knew about sango.us

Tổng kho SÀN ĐẸP chuyên nhập khẩu, phân phối, lắp đặt sàn gỗ công nghiệp, sàn gỗ ngoài trời, sàn gỗ tự nhiên, sàn nhựa từ Malaysia, Đức, Pháp, Thụy Sỹ, Thái Lan, Lào, Nam Phi ...LH: 0916422522

Visit sango.us

Key Findings

We analyzed Sango.us page load time and found that the first response time was 640 ms and then it took 27.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

sango.us performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.151

76/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

sango.us

640 ms

sango.us

1461 ms

js

71 ms

system.base.css

295 ms

system.menus.css

580 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 83% of them (135 requests) were addressed to the original Sango.us, 4% (6 requests) were made to Googletagmanager.com and 3% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Api.ipify.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 789.1 kB (16%)

Content Size

4.9 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sango.us main page is 4.9 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 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 210.1 kB

  • Original 243.4 kB
  • After minification 234.5 kB
  • After compression 33.4 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 210.1 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 469.1 kB

  • Original 4.3 MB
  • After minification 3.9 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, Sango needs image optimization as it can save up to 469.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-29%

Potential reduce by 81.0 kB

  • Original 277.9 kB
  • After minification 276.2 kB
  • After compression 196.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 81.0 kB or 29% of the original size.

CSS Optimization

-48%

Potential reduce by 28.8 kB

  • Original 59.6 kB
  • After minification 55.1 kB
  • After compression 30.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. Sango.us needs all CSS files to be minified and compressed as it can save up to 28.8 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 91 (58%)

Requests Now

156

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sango. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

sango.us

sango.us

640 ms

sango.us

sango.us

1461 ms

js

js

71 ms

system.base.css

system.base.css

295 ms

system.menus.css

system.menus.css

580 ms

system.messages.css

system.messages.css

814 ms

system.theme.css

system.theme.css

839 ms

aggregator.css

aggregator.css

832 ms

field.css

field.css

857 ms

node.css

node.css

855 ms

search.css

search.css

859 ms

user.css

user.css

1093 ms

views.css

views.css

1122 ms

lazyloader.css

lazyloader.css

1119 ms

client_menu.css

client_menu.css

1150 ms

jquery.mmenu.css

jquery.mmenu.css

1149 ms

default-theme-adminimal.css

default-theme-adminimal.css

1147 ms

colorbox_style.css

colorbox_style.css

1370 ms

ctools.css

ctools.css

1403 ms

formtips.css

formtips.css

1401 ms

megamenu.css

megamenu.css

1436 ms

megamenu-skins.css

megamenu-skins.css

1443 ms

menu_icons.css

menu_icons.css

1444 ms

panels.css

panels.css

1643 ms

jquery.qtip.min.css

jquery.qtip.min.css

43 ms

qtip.css

qtip.css

1692 ms

views_slideshow.css

views_slideshow.css

1696 ms

vinno_arcontactus.css

vinno_arcontactus.css

1726 ms

nice_menus.css

nice_menus.css

1734 ms

nice_menus_default.css

nice_menus_default.css

1741 ms

nivo-slider.css

nivo-slider.css

1919 ms

default.css

default.css

1980 ms

views_nivo_slider.css

views_nivo_slider.css

1981 ms

at.layout.css

at.layout.css

2006 ms

global.base.css

global.base.css

2024 ms

global.styles.css

global.styles.css

2032 ms

adaptivetheme_subtheme.responsive.layout.css

adaptivetheme_subtheme.responsive.layout.css

2197 ms

adaptivetheme_subtheme.fonts.css

adaptivetheme_subtheme.fonts.css

2264 ms

responsive.desktop.css

responsive.desktop.css

2261 ms

jquery.qtip.min.js

jquery.qtip.min.js

35 ms

js

js

53 ms

font-awesome.min.css

font-awesome.min.css

42 ms

css_injector_2.css

css_injector_2.css

2283 ms

css_injector_3.css

css_injector_3.css

2028 ms

css_injector_4.css

css_injector_4.css

1755 ms

css_injector_6.css

css_injector_6.css

1679 ms

css_injector_7.css

css_injector_7.css

1741 ms

css_injector_9.css

css_injector_9.css

1746 ms

css_injector_11.css

css_injector_11.css

1727 ms

css_injector_13.css

css_injector_13.css

1766 ms

css_injector_14.css

css_injector_14.css

1775 ms

jquery.min.js

jquery.min.js

1956 ms

jquery.once.js

jquery.once.js

1746 ms

drupal.js

drupal.js

1751 ms

admin_devel.js

admin_devel.js

1729 ms

equalheights.js

equalheights.js

1766 ms

jquery.lazyloader.js

jquery.lazyloader.js

1786 ms

vi_ksIzNHR5QK1dgliDKEqxVFAHqyjkq-b2ScFsDb5QeRA.js

vi_ksIzNHR5QK1dgliDKEqxVFAHqyjkq-b2ScFsDb5QeRA.js

1788 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

1763 ms

colorbox.js

colorbox.js

1767 ms

colorbox_style.js

colorbox_style.js

1768 ms

hoverintent.minified.js

hoverintent.minified.js

1811 ms

formtips.js

formtips.js

1884 ms

megamenu.js

megamenu.js

1805 ms

qtip.js

qtip.js

1764 ms

views_slideshow.js

views_slideshow.js

1773 ms

vinno_arcontactus.js

vinno_arcontactus.js

1771 ms

readmore.min.js

readmore.min.js

1817 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

1866 ms

views_nivo_slider.js

views_nivo_slider.js

1807 ms

jquery-no-conflict.min.js

jquery-no-conflict.min.js

1766 ms

jquery.mmenu.min-no-conflict.js

jquery.mmenu.min-no-conflict.js

1778 ms

load-jquery.mmenu-no-conflict.js

load-jquery.mmenu-no-conflict.js

1780 ms

client_menu.js

client_menu.js

1818 ms

googleanalytics.js

googleanalytics.js

1858 ms

js_injector_2.js

js_injector_2.js

1821 ms

js_injector_3.js

js_injector_3.js

1767 ms

js_injector_5.js

js_injector_5.js

1776 ms

js_injector_7.js

js_injector_7.js

1784 ms

js_injector_9.js

js_injector_9.js

1826 ms

js_injector_10.js

js_injector_10.js

1838 ms

browserclass.js

browserclass.js

1867 ms

analytics.js

analytics.js

16 ms

collect

collect

13 ms

collect

collect

13 ms

js

js

53 ms

ga-audiences

ga-audiences

103 ms

js

js

133 ms

gtm.js

gtm.js

133 ms

dmca_protected_sml_120f.png

dmca_protected_sml_120f.png

132 ms

zalo-icon.png

zalo-icon.png

326 ms

facebook-icon.png

facebook-icon.png

327 ms

call-icon-green.png

call-icon-green.png

330 ms

logo_trong_roi.png

logo_trong_roi.png

672 ms

san-go-lamilate-gia-re-nhat-ha-noi_0.jpg

san-go-lamilate-gia-re-nhat-ha-noi_0.jpg

1426 ms

san-go-ngoai-troi-tecwood-gia-re-nhat.jpg

san-go-ngoai-troi-tecwood-gia-re-nhat.jpg

1548 ms

kho-san-nhua-ha-noi.jpg

kho-san-nhua-ha-noi.jpg

1220 ms

banner-san-go-san-dep-ha-noi.jpg

banner-san-go-san-dep-ha-noi.jpg

1721 ms

san-go-cong-nghiep-gia-re-dep_0.jpg

san-go-cong-nghiep-gia-re-dep_0.jpg

1209 ms

tong-kho-san-nhua-gia-re-ha-noi.jpg

tong-kho-san-nhua-gia-re-ha-noi.jpg

1102 ms

vat-lieu-go-nhua-composite-ngoai-troi.jpg

vat-lieu-go-nhua-composite-ngoai-troi.jpg

1384 ms

mat-bac-cau-thang-go-cong-nghiep-dep.jpg

mat-bac-cau-thang-go-cong-nghiep-dep.jpg

1786 ms

san-go-tu-nhien-laoi-1-dep.jpg

san-go-tu-nhien-laoi-1-dep.jpg

1779 ms

tam-op-gia-go-pvc-dep_0.jpg

tam-op-gia-go-pvc-dep_0.jpg

1663 ms

san-go-ngoai-troi-san-dep-gia-re-nhat.jpg

san-go-ngoai-troi-san-dep-gia-re-nhat.jpg

1995 ms

san-go-cong-nghiep-malaysia-chinh-hang-gia-re-nhat.jpg

san-go-cong-nghiep-malaysia-chinh-hang-gia-re-nhat.jpg

2101 ms

san-go-chau-au.jpg

san-go-chau-au.jpg

1948 ms

san-go-cong-nghiep-gia-re-nhat_0.jpg

san-go-cong-nghiep-gia-re-nhat_0.jpg

2281 ms

san-go-cong-nghiep-thai-lan.jpg

san-go-cong-nghiep-thai-lan.jpg

2073 ms

san-go-viet-nam.jpg

san-go-viet-nam.jpg

2364 ms

san-go-duc.jpg

san-go-duc.jpg

2234 ms

san-go-indonesia-chiu-nuoc-gia-re.jpg

san-go-indonesia-chiu-nuoc-gia-re.jpg

2292 ms

san-go-han-quoc-dep.png

san-go-han-quoc-dep.png

2638 ms

gia-san-go-xuong-ca_0.jpg

gia-san-go-xuong-ca_0.jpg

2655 ms

san-go-cot-xanh-ha-noi-gia-re.jpg

san-go-cot-xanh-ha-noi-gia-re.jpg

2515 ms

san-go-cot-den-cdf-ha-noi-gia-re.jpg

san-go-cot-den-cdf-ha-noi-gia-re.jpg

2571 ms

van-san-go-12mm.jpg

van-san-go-12mm.jpg

2594 ms

kho-san-go-8mm.jpg

kho-san-go-8mm.jpg

2964 ms

op-tran-nhua-pvc-lam-song-gia-go.png

op-tran-nhua-pvc-lam-song-gia-go.png

3069 ms

phu-kien-san-go.jpg

phu-kien-san-go.jpg

2867 ms

chi-phi-thi-cong-san-go-ha-noi.jpg

chi-phi-thi-cong-san-go-ha-noi.jpg

2895 ms

lap-san-go-ngoai-troi_0.jpg

lap-san-go-ngoai-troi_0.jpg

2931 ms

san-nhua-van-tham.jpg

san-nhua-van-tham.jpg

2939 ms

tuyen-dai-ly-ban-san-go.jpg

tuyen-dai-ly-ban-san-go.jpg

3159 ms

sdk.js

sdk.js

240 ms

embed

embed

252 ms

embed

embed

254 ms

san-go-thai-lan-gia-re.jpg

san-go-thai-lan-gia-re.jpg

3121 ms

lap-san-go-cong-nghiep.jpg

lap-san-go-cong-nghiep.jpg

2941 ms

js

js

234 ms

api.ipify.org

api.ipify.org

19899 ms

sdk.js

sdk.js

177 ms

mobile.png

mobile.png

2907 ms

js

js

110 ms

chi-phi-thi-cong-san-go-ha-noi.jpg

chi-phi-thi-cong-san-go-ha-noi.jpg

2937 ms

js

js

107 ms

lap-san-go-ngoai-troi_0.jpg

lap-san-go-ngoai-troi_0.jpg

3024 ms

embed

embed

273 ms

embed

embed

269 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

23 ms

173 ms

san-nhua-van-tham.jpg

san-nhua-van-tham.jpg

2739 ms

js

js

60 ms

js

js

57 ms

tuyen-dai-ly-ban-san-go.jpg

tuyen-dai-ly-ban-san-go.jpg

2388 ms

san-go-thai-lan-gia-re.jpg

san-go-thai-lan-gia-re.jpg

2304 ms

lap-san-go-cong-nghiep.jpg

lap-san-go-cong-nghiep.jpg

2295 ms

bao_ve.png

bao_ve.png

2175 ms

bo_cong_thuon.png

bo_cong_thuon.png

2211 ms

phone-24.png

phone-24.png

2197 ms

sf_search.png

sf_search.png

2113 ms

bg-menubar.jpg

bg-menubar.jpg

2079 ms

line-li.jpg

line-li.jpg

2022 ms

bullet-more.png

bullet-more.png

2079 ms

li-bulltet-mn.jpg

li-bulltet-mn.jpg

1968 ms

star-icon.png

star-icon.png

2045 ms

loading.gif

loading.gif

1999 ms

sango.us

sango.us

2022 ms

responsive.smartphone.portrait.css

responsive.smartphone.portrait.css

285 ms

responsive.smartphone.landscape.css

responsive.smartphone.landscape.css

283 ms

responsive.tablet.portrait.css

responsive.tablet.portrait.css

286 ms

responsive.tablet.landscape.css

responsive.tablet.landscape.css

285 ms

Accessibility Review

sango.us accessibility score

66

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sango.us best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sango.us SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    VI

  • Language Claimed

    VI

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sango.us can be misinterpreted by Google and other search engines. Our service has detected that Vietnamese is used on the page, and it matches the claimed language. Our system also found out that Sango.us 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.

Social Sharing Optimization

sango.us

Open Graph description is not detected on the main page of Sango. 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: