14.9 sec in total
625 ms
13.4 sec
857 ms
Click here to check amazing 5 Giay content for Vietnam. Otherwise, check out these important facts you probably never knew about 5giay.vn
5giay.vn - sàn mua bán online, ăng tin rao vặt nhanh chóng
Visit 5giay.vnWe analyzed 5giay.vn page load time and found that the first response time was 625 ms and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
5giay.vn performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.0 s
6/100
25%
Value10.7 s
7/100
10%
Value3,080 ms
2/100
30%
Value0.233
53/100
15%
Value17.2 s
4/100
10%
625 ms
2143 ms
844 ms
878 ms
1260 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 55% of them (89 requests) were addressed to the original 5giay.vn, 6% (9 requests) were made to Pagead2.googlesyndication.com and 4% (7 requests) were made to S0.2mdn.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain 5giay.vn.
Page size can be reduced by 665.0 kB (48%)
1.4 MB
723.6 kB
In fact, the total size of 5giay.vn main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 953.3 kB which makes up the majority of the site volume.
Potential reduce by 138.9 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 23.2 kB, which is 14% 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 138.9 kB or 83% of the original size.
Potential reduce by 36.6 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, 5 Giay needs image optimization as it can save up to 36.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 484.7 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 484.7 kB or 51% of the original size.
Potential reduce by 4.8 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. 5giay.vn needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 71% of the original size.
Number of requests can be reduced by 53 (35%)
150
97
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 5 Giay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
5giay.vn
625 ms
www.5giay.vn
2143 ms
css.php
844 ms
custom-node-icons
878 ms
css.php
1260 ms
jquery-1.11.0.min.js
3159 ms
xenforo.js
1821 ms
jquery.number.min.js
2086 ms
jquery.sticky.js
2176 ms
main.js
2353 ms
lazysizes.min.js
2516 ms
mBanner.css
1192 ms
mBanner.js
1482 ms
adsbygoogle.js
41 ms
analytics.js
287 ms
ga.js
304 ms
collect
49 ms
__utm.gif
33 ms
collect
69 ms
ga-audiences
49 ms
igo.jpg
396 ms
logo.png
579 ms
logo-congthuong.png
367 ms
dienthoaidoc490x180-g2-thao.gif
713 ms
phukiengiare-g-thao.gif
1389 ms
category-23px-light.png
674 ms
xenforo-ui-sprite.png
767 ms
search-icon.png
935 ms
68_1.jpg
1053 ms
71_1.jpg
1047 ms
42_1.jpg
1226 ms
168_1.jpg
1380 ms
node-sprite.png
1422 ms
gradient_tcat.gif
367 ms
topicfree_780x100-acg.gif
1987 ms
87_1.jpg
1638 ms
33_1.jpg
1637 ms
97_1.jpg
1747 ms
152_1.jpg
1894 ms
109_1.jpg
1880 ms
138_1.jpg
2100 ms
22_1.jpg
2124 ms
126_1.jpg
2145 ms
140_1.jpg
2232 ms
73_1.jpg
2431 ms
145_1.jpg
2358 ms
14_1.jpg
2383 ms
27_1.jpg
2479 ms
148_1.jpg
2599 ms
158_1.jpg
2633 ms
24_1.jpg
2765 ms
171_1.jpg
2721 ms
172_1.jpg
2828 ms
159_1.jpg
2876 ms
62_1.jpg
2965 ms
169_1.jpg
3087 ms
28_1.jpg
3060 ms
88_1.jpg
3117 ms
atrk.js
211 ms
sdk.js
308 ms
ca-pub-7184137093806691.js
52 ms
zrt_lookup.html
141 ms
show_ads_impl.js
141 ms
5giay_hoangha_r4_mobile.htm
2956 ms
atrk.gif
230 ms
ads
167 ms
osd.js
55 ms
195_1.jpg
2845 ms
ads
232 ms
ads
269 ms
391 ms
xd_arbiter.php
133 ms
harapage-780x100-h-acg.png
3168 ms
43_1.jpg
2748 ms
aclk
133 ms
192_1.jpg
2816 ms
aclk
80 ms
adchoice_1.4.png
80 ms
aclk
107 ms
adxsync
52 ms
inside.js
120 ms
aclk
109 ms
aclk
77 ms
pixel
152 ms
135_1.jpg
2689 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
111 ms
lidar.js
67 ms
208 ms
200 ms
aclk
81 ms
adxsync
82 ms
122 ms
139_1.jpg
2656 ms
pixel
57 ms
182_1.jpg
2780 ms
%7BSSP_USER_ID%7D
176 ms
index.html
91 ms
0714_Progressive_Scoreboard_160x600.html
136 ms
index.html
64 ms
%7BSSP_USER_ID%7D
259 ms
runtime.js
95 ms
css
201 ms
css
202 ms
main.css
24 ms
logo.png
28 ms
css
208 ms
css
257 ms
main.css
32 ms
32_1.jpg
2634 ms
main.css
4 ms
main.jpg
53 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
279 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
284 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
288 ms
119_1.jpg
2580 ms
44_1.jpg
2817 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
242 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
240 ms
160_1.jpg
2676 ms
yv
156 ms
activeview
39 ms
activeview
35 ms
yv
121 ms
55_1.jpg
2454 ms
41_1.jpg
2596 ms
yv
100 ms
activeview
57 ms
150_1.jpg
2587 ms
149_1.jpg
2456 ms
163_1.jpg
2621 ms
164_1.jpg
2506 ms
128_1.jpg
2477 ms
53_1.jpg
2459 ms
176_1.jpg
2654 ms
146_1.jpg
2501 ms
90_1.jpg
2486 ms
115_1.jpg
2412 ms
122_1.jpg
2407 ms
13_1.jpg
2563 ms
191_1.jpg
2566 ms
103_1.jpg
2418 ms
141_1.jpg
2392 ms
38_1.jpg
2518 ms
35_1.jpg
2526 ms
39_1.jpg
2473 ms
137_1.jpg
2418 ms
101_1.jpg
2443 ms
45_1.jpg
2526 ms
20_1.jpg
2472 ms
gpt.js
23 ms
form-button-white-25px.png
2348 ms
pubads_impl_83.js
56 ms
container.html
31 ms
ads
73 ms
bgntp1.png
2266 ms
hoangha-r4-trm.gif
4144 ms
5404153672642558377
10 ms
nav-bg.gif
2333 ms
navigation-tab.png
2328 ms
new.png
2321 ms
activeview
15 ms
5giay.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 match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
5giay.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
Page has valid source maps
5giay.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
VI
VI
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 5giay.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 5giay.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.
5giay.vn
Open Graph data is detected on the main page of 5 Giay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: