14.2 sec in total
564 ms
12.6 sec
1.1 sec
Visit vdo.vn now to see the best up-to-date VDO content for Vietnam and also check out these interesting facts you probably never knew about vdo.vn
Trang chủ VDO cung cấp các thông tin tổng quan về VDO: Lịch sử hình thành, các sản phẩm, hệ thống phân phối, đối tác chiến lược, khách hàng thân thiết.
Visit vdo.vnWe analyzed Vdo.vn page load time and found that the first response time was 564 ms and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
vdo.vn performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value42.7 s
0/100
25%
Value10.8 s
6/100
10%
Value3,110 ms
2/100
30%
Value0.349
32/100
15%
Value16.6 s
5/100
10%
564 ms
2213 ms
958 ms
716 ms
393 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vdo.vn, 66% (105 requests) were made to Res.vdo.vn and 17% (27 requests) were made to Dis.vdo.com.vn. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source Res.vdo.vn.
Page size can be reduced by 5.7 MB (21%)
27.9 MB
22.2 MB
In fact, the total size of Vdo.vn main page is 27.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. Only a small number of websites need less resources to load. Images take 26.6 MB which makes up the majority of the site volume.
Potential reduce by 850.1 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 256.7 kB, which is 29% 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 850.1 kB or 96% of the original size.
Potential reduce by 4.8 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, VDO needs image optimization as it can save up to 4.8 MB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 29.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. This website has mostly compressed JavaScripts.
Potential reduce by 19.6 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. Vdo.vn needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 22% of the original size.
Number of requests can be reduced by 39 (26%)
150
111
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VDO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
vdo.vn
564 ms
dis.vdo.com.vn
2213 ms
output.css
958 ms
common.css
716 ms
all.css
393 ms
all.css
51 ms
tw-elements.min.css
69 ms
flexmasonry.css
404 ms
owl.carousel.min.css
717 ms
owl.theme.default.min.css
725 ms
card.css
727 ms
font-awesome.css
746 ms
all.css
27 ms
flexmasonry.css
13 ms
sdk.js
1640 ms
tw-elements.umd.min.js
43 ms
jquery.min.js
721 ms
owl.carousel.min.js
485 ms
flowbite.min.js
28 ms
rotate-icon.js
485 ms
menu.js
490 ms
scroll.js
588 ms
modal-search.js
711 ms
js
72 ms
css
39 ms
gtm.js
95 ms
banner-1-desktop-884fdf7b66981.png
2033 ms
down-circle-button.png
247 ms
contact-phone.png
266 ms
contact-zalo.png
267 ms
contact-message.png
266 ms
card-contact-phone.png
369 ms
card-contact-zalo.png
378 ms
card-contact-message.png
506 ms
dot.png
509 ms
logo-footer.png
506 ms
xac-nhan.png
514 ms
facebook.png
608 ms
twitter.png
617 ms
instagram.png
745 ms
banner-1-desktop-884fdebd89abe.png
1938 ms
vi.png
982 ms
en.png
999 ms
vdo-logo-8b099beccc311.gif
8290 ms
Doi-tac_Gigabyte-89bea2f32b38b.png
1007 ms
Doi-tac_Inwin-89bea25157027.png
1551 ms
Doi-tac_Samsung-89bea13d3771c.png
1553 ms
Doi-tac_Micron-89be9c331eda1.png
1553 ms
Intel%C2%AE-Server-Board-S2600WF0R--8b90a0bb5a55c.jpg
1697 ms
Intel%C2%AE-Server-Board-S2600WF0R--8b909b543bb68.jpg
1758 ms
W291-Z00_rev.C00-01-87208dd50124c.png
4148 ms
Icon-1.png
1938 ms
Icon-2.png
1959 ms
Icon-3.png
2171 ms
Icon-4.png
2174 ms
G292-Z45_rev.ICU1-01-870acdbb9eb11.png
2919 ms
S472-Z30_rev.A00-01-870a4732758be.png
3481 ms
R282-P92_rev.100-01-86f1fe5ad8afa.png
2647 ms
TO24-JD0_rev.100-01-86bcf5a3e8e42.png
3350 ms
IW-RA100_01-87a1fb8b84c30.png
2883 ms
IW-RA102_01-87a211fa7968f.png
3121 ms
IW-RF100_01-87a22663df933.png
3162 ms
IW-RF100S_01-87a23486a186f.png
3358 ms
IW-R200N_01-87a25000b8351.png
3408 ms
IW-R200-01N_01-87a2dc9dfef01.png
3825 ms
IW-R200-02N_01-87a2f36ee6bd2.png
3597 ms
IW-R300N_01-87a305e9343d3.jpg
3649 ms
IW-R300-01N_01-87a3133ae16f9.jpg
3732 ms
Web-Banner-[Recovered]-01-8c48c47e572e4.png
3838 ms
W331-Z00_rev.100-01-87205126594fa.png
4137 ms
W332-Z00_rev.100-01-8720622fd9139.png
5495 ms
W291-Z00_rev.B00-01-87207c1a45313.png
4075 ms
S251-3O0_rev.IBC1-01-870a337ad1f46.png
4080 ms
S251-3O0_rev.IBH1-01-870a3b38a3a2c.png
4317 ms
S251-3O0_rev.IBC1-01-870a50cf0b0e0.png
4320 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
23 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
43 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf
43 ms
fontawesome-webfont.woff
1517 ms
Web-Banner-[Recovered]-02-8c48c79cfeaab.png
3402 ms
Web-Banner-[Recovered]-03-8c48c6f198a8c.png
3874 ms
mini-2-86bc085c0fd57.png
3553 ms
page.widget.zalo.me
1393 ms
za.js
1119 ms
js
136 ms
mini-3-86bc1ba0ad0f5.png
3011 ms
mini-7-86bc2b8abb414.png
3073 ms
500-86bc3733674d8.png
3243 ms
Mini-19-86bc40a098cf8.png
3042 ms
mini-15-86bc4b491cc77.png
2957 ms
mini-20-86bc58e14cdb3.png
3101 ms
mini-16-86bc66759647b.png
3096 ms
500-86bccb9aaafb6.png
3151 ms
Mini-4-86bcdb5810032.png
3388 ms
Industiral-Wi-Fi-6E-89b127a90c71b.png
3102 ms
AI-Edge-Wi-Fi-6E-89b12e8da4132.png
3340 ms
css2
89 ms
za.js
253 ms
sdk-server-1.0.0.js
1093 ms
cphandler.js
262 ms
zinit.js
523 ms
all.min.css
1009 ms
main.d49f197b.chunk.css
1010 ms
2.ef1b18a1.chunk.js
1795 ms
main.e5889962.chunk.js
1029 ms
IoT-Wi-Fi-6-89b134630ff4c.png
2713 ms
Wi-Fi-6E-Dipole-Antenna-89b137b7a0f6d.png
2624 ms
Wi-Fi-6E-PIFA-Antenna-89b13bcd4c3cc.png
2921 ms
Wireless-USBHDMI-89b14762c78d8.jpg
2480 ms
Wireless-USB-89b14d113914e.png
2586 ms
WiGigHub-89b1525c166e0.png
2394 ms
WiGig-USB-Adapter-89b156da1724b.jpg
2398 ms
IP-COM-Expander-Lite-89b15a6d99209.jpg
2434 ms
TO24-JD1_rev.100-01-86bd31d72fc80.png
2506 ms
CMT4034_rev.1.0-01-86bc88710537e.png
2405 ms
CMT4032_rev.1.0-01-86bc8ff4be504.png
2345 ms
CLNCA12_rev.1.x-01-86bc984f3a409.png
4036 ms
MS73-HB2_rev.1.x-01-870a1e9eaea47.png
2274 ms
MS73-HB0_rev.1.x-01-870a129fb5029.png
2402 ms
MS73-HB1_rev.1.x-01-870a183daee5e.png
2436 ms
MS33-AR0_rev.1.x-01-870a286286db3.png
3679 ms
MS33-AR1_rev.1.x-01-870a2e1d3176c.png
2218 ms
MS03-CE0_rev.1.x-01-870a33ec6db87.png
2366 ms
he-thong-phan-phoi-desktop-84acd1920531f.png
2314 ms
1-Bo-CA-8b45964ea4f5b.png
2431 ms
5-TPBank-8b459559fc3cc.png
2373 ms
2-bo-tu-lenh-86-8b45960ba1114.png
2315 ms
6-Naspas-8b459519e7460.png
2433 ms
3-Bo-Y-Te-8b4595d1b6f84.png
2369 ms
7-vnpay-8b4594d819f41.png
2318 ms
4-Bo-GDDT-8b4595967e4ed.png
2421 ms
8-vnpt-8b45946f5e660.png
2351 ms
14-gtel-ict-8b45924d2286f.png
2476 ms
15-Mobifone-8b4591f7bab4a.png
2394 ms
16-vtc-8b45919b0d9c6.png
2403 ms
17-htc-itc-8b45914b12918.png
2458 ms
9-viettel-8b45933bbe247.png
2390 ms
23-pvi-8b458f6555697.png
2317 ms
10-FPT-8b4592fda9ecc.png
2451 ms
24-petrovietnam-8b458e8e92a1a.png
2403 ms
12-Telehouse-8b458e082970f.png
2403 ms
25-vng-8b458d6229035.png
2498 ms
13-cmc-8b4592a8c49cf.png
2408 ms
26-vin-group-8b458d13240ef.png
2307 ms
31-evn-8b4580986ea3a.png
2384 ms
32-dai-hoc-y-8b457fb1e3f1d.png
2391 ms
18-eco-dc-8b4590cde6765.png
2412 ms
19-vietnam-mobile-8b45907ac0374.png
2421 ms
20-benh-vien-hop-luc-8b4590297ced3.png
2305 ms
21-bach-mai-8b458fd466af3.png
2374 ms
27-vin-ai-8b458c6ea11a9.png
2383 ms
28-xelex-8b458c1756e34.png
2392 ms
29-co-yeu-viet-nam-8b458bb9c23ec.png
2266 ms
30-DH-Vinh-8b458171f3b43.png
2160 ms
Anh-1a-8b696fb79f571.jpg
2021 ms
Anh-1-8b695282be1ab.jpg
2070 ms
Cloud-PBX111-8a87f55833a3a.png
1968 ms
Micron-89727d7dd7b88.png
2466 ms
ss-test-897074547489f.png
1997 ms
Gigabyte-hop-tac-VDO-897281951db1f.png
1884 ms
vdo.vn 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 have valid values
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
vdo.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
vdo.vn SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
VI
VI
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vdo.vn 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 Vdo.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.
vdo.vn
Open Graph description is not detected on the main page of VDO. 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: