4.6 sec in total
831 ms
3.3 sec
541 ms
Click here to check amazing Tiki content for Vietnam. Otherwise, check out these important facts you probably never knew about tiki.vn
Tiện lợi mua sắm hàng triệu mặt hàng, dịch vụ. Vô vàn ưu đãi freeship, mã giảm giá. Hoàn tiền 15% tối đa 600k/tháng với thẻ tín dụng TikiCARD.
Visit tiki.vnWe analyzed Tiki.vn page load time and found that the first response time was 831 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tiki.vn performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value11.8 s
0/100
25%
Value13.3 s
2/100
10%
Value3,710 ms
1/100
30%
Value0.153
75/100
15%
Value23.0 s
1/100
10%
831 ms
904 ms
1031 ms
1030 ms
1035 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tiki.vn, 79% (49 requests) were made to Frontend.tikicdn.com and 15% (9 requests) were made to Salt.tikicdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Frontend.tikicdn.com.
Page size can be reduced by 178.9 kB (58%)
309.5 kB
130.6 kB
In fact, the total size of Tiki.vn main page is 309.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 234.1 kB which makes up the majority of the site volume.
Potential reduce by 169.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 169.4 kB or 72% of the original size.
Potential reduce by 9.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. Obviously, Tiki needs image optimization as it can save up to 9.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9 B
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.
Number of requests can be reduced by 44 (72%)
61
17
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tiki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and as a result speed up the page load time.
tiki.vn
831 ms
_sprite.css
904 ms
ee828743c9afa9792cf20d75995e134e.png
1031 ms
6fef2e788f00a16dc7d5a1dfc5d0e97a.png
1030 ms
6baaecfa664314469ab50758e5ee46ca.png
1035 ms
d7b6a3bd7d57d37ef6e437aa0de4821b.png
1064 ms
8ca7e2cc5ede8c09e34d1beb50267f4f.png
1066 ms
f5ee506836792eb7775e527ef8350a44.png
1087 ms
67396e2dcdf5d503349d4628501c4831.png
1277 ms
1bb77cdb828972a5284a06dac79c0afc.png
1278 ms
dmca_protected_sml_120y.png
21 ms
bo-cong-thuong-2.png
872 ms
bo-cong-thuong.svg
1092 ms
e71563afb23e3f34a148fe1b7d3413c5.png
1244 ms
qrcode.png
882 ms
appstore.png
885 ms
playstore.png
886 ms
polyfills-d0c6744c799cfb7f2ac3.js
769 ms
fa5f8105.05892ccab76286789d24.js
607 ms
9d6ab11ee0e10e4e4652f3acd876cf3f74d49441.d0d695ee72317becb59d.js
646 ms
c05e89f3cb14cb0d0cfe51d1fae26b56d9a06df2.8beba230dbaa00be4135.js
647 ms
comp.HeaderRevamp.a195b22181e8268e376a.js
650 ms
comp.UniversalFreeShipPlus.9a54e2adc266eba6d56e.js
822 ms
comp.BannersCarousel.0af20c784f06700fad20.js
827 ms
comp.QuickLinks.b4c81d65255fe1e8ccfd.js
860 ms
comp.Footer.f286441b407cc848dc20.js
863 ms
webpack-ce0abe554c51ebfb6288.js
866 ms
framework.c1cda632ed7b1ab932be.js
985 ms
6cf515ba9108ff7c4acb8f40acb6e3bc1826a847.9abb3ef5b6b56a145496.js
1037 ms
a444081ab51fc1df511b001c4dff439a3643fdbf.5d943ab7d14cd0f22390.js
1042 ms
main-9c347bcf985fb1c82f0e.js
1075 ms
e971612a.4a560fd6abf12c175d4a.js
1293 ms
8daf538b.ff7b57ecd2badad5f15c.js
1299 ms
a663a7efa79b133df77b08ddababa8a1d85f675e.80868360d1cb723c040f.js
1199 ms
0276021fec9316fc7b8aa948d2bef1512240cced.df5ca9453be08ef5d210.js
1252 ms
c4297cff18a6f3bc8e1542a52a130f69ce8037b5.d1f87e76604e715e27e2.js
1256 ms
1c04d6b5e66b9e6b8b5e8884479981874f8d96b4.f03a77938433bd3b61f3.js
1936 ms
efabeecd04cb350da69c172f13043b2cd2e97d5f.2d2d68e2a55f487a2a78.js
1415 ms
883bec30c3d4eff617fa308637f062ccdcbb9348.c3a5e79c37767a761b4a.js
2117 ms
df699e572d61e11af911d22187401fe64a4b1915.a0a723994d1ec7ff0c24.js
1472 ms
2e6be4c61179439e8ce869f26f8657d90cedc36f.4c4e330d954eb7bfc873.js
1508 ms
3ca90c0b18bbee061157589dea0cd63163a7e797.9feb6db83ae46ebb3eaf.js
1514 ms
87209e5ed717a494e0192306ee7c44080b37d422.4a90aed2d743b4d735c5.js
1630 ms
ca40081782f300cd92ce449d65684eb138afbe60.1a17ea5a9cb598d6f2bd.js
1689 ms
c37ad3999f2076bab6929ed359e2ef17b79d8b3b.1172f9027e096ad9cb82.js
1724 ms
lib.pouchdb-browser.a30a894134e851f41a97.js
1732 ms
_app-27d18f46ad788ebc2500.js
1845 ms
amplitude-8.18.4-min.gz.js
18 ms
js
62 ms
e5908a55.7e7327fa86992426c29c.js
1538 ms
419885c24f222147a836331090a81ab6c86c636d.1b2861c566e46de664cc.js
1561 ms
322eaa9279358fda6b991bd1bf1c39699fe76544.db9019664e43171d0ca5.js
1524 ms
f7fba06b716a34e5eeed09d15d1b94978e2da1ea.793094a4b3a5ab31f020.js
1637 ms
382ecf5080bafc4f8aa09e463b10584d1a0a543a.6900beb12e36d4ecf779.js
1711 ms
08e8b924bec408f14f831e23cf63518fb33b18cf.b6b03fd23a6b1b0dad83.js
1551 ms
09b7c64ff70a6ffb5b029f7a43fd6d8abc4fd975.158b0678617827f1212c.js
1766 ms
a232ae60ad746ca8b71582e62b62d1e7fb44b030.3da5247619c71ae05dc8.js
1527 ms
625157420d2f6ba670a0963cbd49ce53da3d04d4.c0cbea2a9f7ecd9f621e.js
1637 ms
27e707a338ba946ab009663bb1aed042a6fe81a3.d977c2bdbea00fff1f17.js
1688 ms
HomepageRevamp-51aa8cb99359a19c3a62.js
1568 ms
_buildManifest.js
1550 ms
_ssgManifest.js
1562 ms
tiki.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-hidden="true"] is present on the document <body>
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.
tiki.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tiki.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
VI
VI
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tiki.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 Tiki.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.
tiki.vn
Open Graph data is detected on the main page of Tiki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: