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

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

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.1 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.1 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

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.

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

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: