13.7 sec in total
805 ms
12 sec
917 ms
Welcome to cariny.vn homepage info - get ready to check Cariny best content for Vietnam right away, or after learning these important things about cariny.vn
Phụ kiện tủ bếp, phụ kiện tủ áo, vòi rửa, chậu rửa, đèn led, tủ bếp cao cấp, tay nắm cánh tủ, kệ bát di động, kệ inox, sen tắm, ray cửa, vật liệu bề mặt
Visit cariny.vnWe analyzed Cariny.vn page load time and found that the first response time was 805 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cariny.vn performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value9.4 s
0/100
25%
Value18.7 s
0/100
10%
Value1,900 ms
8/100
30%
Value1.244
1/100
15%
Value34.0 s
0/100
10%
805 ms
244 ms
2405 ms
1478 ms
20 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 77% of them (95 requests) were addressed to the original Cariny.vn, 6% (7 requests) were made to Page.widget.zalo.me and 2% (2 requests) were made to Oss.maxcdn.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Cariny.vn.
Page size can be reduced by 629.3 kB (11%)
5.7 MB
5.1 MB
In fact, the total size of Cariny.vn main page is 5.7 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. 60% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 92.6 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 92.6 kB or 75% of the original size.
Potential reduce by 191.3 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. Cariny images are well optimized though.
Potential reduce by 229.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 229.7 kB or 28% of the original size.
Potential reduce by 115.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. Cariny.vn needs all CSS files to be minified and compressed as it can save up to 115.7 kB or 58% of the original size.
Number of requests can be reduced by 34 (30%)
114
80
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cariny. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
cariny.vn
805 ms
home
244 ms
2405 ms
bootstrap.min.css
1478 ms
font-awesome.min.css
20 ms
jquery.fancybox.css
483 ms
custom-theme.css
1014 ms
media.css
522 ms
bn-59842.png
1344 ms
Slide-44523.jpg
1949 ms
Slide-54309.jpg
2380 ms
Slide-3126.jpg
2066 ms
Slide-11521.jpg
1951 ms
Slide-43152.jpg
1973 ms
Slide-51688.jpg
2191 ms
Slide-5549.jpg
2453 ms
Slide-43526.jpg
4573 ms
Slide-34684.jpg
4518 ms
Slide-53757.jpg
2607 ms
Slide-30491.png
3004 ms
art-51503.jpeg
2667 ms
art-1191.jpg
2719 ms
art-59494.jpg
4857 ms
art-54448.jpg
2928 ms
avt-3803.jpg
3878 ms
skype.png
2715 ms
avt-29310.jpg
3328 ms
avt-58805.jpg
2995 ms
resizeimg.aspx
3292 ms
resizeimg.aspx
3561 ms
resizeimg.aspx
3602 ms
resizeimg.aspx
3841 ms
resizeimg.aspx
3872 ms
resizeimg.aspx
4107 ms
resizeimg.aspx
4148 ms
resizeimg.aspx
4129 ms
resizeimg.aspx
4289 ms
resizeimg.aspx
4346 ms
resizeimg.aspx
4379 ms
resizeimg.aspx
4882 ms
resizeimg.aspx
4421 ms
20150827110756-dathongbao.png
1305 ms
resizeimg.aspx
4241 ms
html5shiv.js
1010 ms
respond.min.js
1010 ms
jquery.min.js
4037 ms
sdk.js
1648 ms
plusone.js
10 ms
fontawesome-webfont.woff
12 ms
jquery.elevateZoom-3.0.8.min.js
4056 ms
element.js
43 ms
WebResource.axd
4044 ms
ScriptResource.axd
7468 ms
ScriptResource.axd
3333 ms
bootstrap.min.js
3384 ms
fluidvids.min.js
3315 ms
jquery.mousewheel-3.0.6.pack.js
3202 ms
jquery.fancybox.js
3161 ms
matchHeight.js
3152 ms
customScript.js
3002 ms
glyphicons-halflings-regular.woff
2970 ms
resizeimg.aspx
2945 ms
resizeimg.aspx
2854 ms
resizeimg.aspx
2861 ms
resizeimg.aspx
3687 ms
resizeimg.aspx
2421 ms
resizeimg.aspx
2164 ms
resizeimg.aspx
2233 ms
resizeimg.aspx
2147 ms
resizeimg.aspx
3119 ms
resizeimg.aspx
1937 ms
resizeimg.aspx
2011 ms
resizeimg.aspx
2159 ms
resizeimg.aspx
2052 ms
resizeimg.aspx
2103 ms
resizeimg.aspx
2180 ms
resizeimg.aspx
2233 ms
resizeimg.aspx
2293 ms
resizeimg.aspx
2252 ms
resizeimg.aspx
2278 ms
resizeimg.aspx
2267 ms
resizeimg.aspx
2356 ms
resizeimg.aspx
2378 ms
resizeimg.aspx
2356 ms
resizeimg.aspx
2268 ms
analytics.js
25 ms
page.widget.zalo.me
1321 ms
za.js
801 ms
resizeimg.aspx
2325 ms
resizeimg.aspx
2823 ms
collect
14 ms
js
61 ms
qc-28822.png
2249 ms
qc-15471.png
2275 ms
qc-5799.png
2258 ms
qc-9397.png
2355 ms
qc-46744.png
2388 ms
qc-39900.jpg
2331 ms
qc-15572.jpg
2291 ms
qc-59577.png
2381 ms
qc-43748.png
2383 ms
qc-5804.png
2446 ms
qc-56568.jpg
2375 ms
qc-37367.gif
2350 ms
bgMenuTop.png
2351 ms
bgFooterSlider.png
2340 ms
ajax-loader.gif
2310 ms
bgFooter.png
2234 ms
css2
35 ms
za.js
1079 ms
sdk-server-1.0.0.js
1375 ms
cphandler.js
272 ms
zinit.js
543 ms
all.min.css
1066 ms
main.02e85093.chunk.css
1064 ms
2.17bbab3c.chunk.js
2143 ms
main.fdb0f5d4.chunk.js
1084 ms
cb=gapi.loaded_0
71 ms
sdk.js
65 ms
v2.zopim.com
54 ms
js
68 ms
sdk.js
24 ms
asset_composer.js
39 ms
cariny.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
cariny.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
cariny.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 Cariny.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 Cariny.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.
cariny.vn
Open Graph description is not detected on the main page of Cariny. 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: