9.1 sec in total
762 ms
7.6 sec
697 ms
Welcome to vivastudio.co.kr homepage info - get ready to check VIVASTUDIO best content for South Korea right away, or after learning these important things about vivastudio.co.kr
VIVASTUDIO - 비바스튜디오 공식 온라인 스토어
Visit vivastudio.co.krWe analyzed Vivastudio.co.kr page load time and found that the first response time was 762 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
vivastudio.co.kr performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value41.7 s
0/100
25%
Value16.7 s
0/100
10%
Value1,560 ms
13/100
30%
Value0.148
76/100
15%
Value37.9 s
0/100
10%
762 ms
953 ms
291 ms
187 ms
67 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 17% of them (18 requests) were addressed to the original Vivastudio.co.kr, 24% (25 requests) were made to Chat-static.happytalkio.com and 10% (10 requests) were made to Cafe24img.poxo.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Cafe24.poxo.com.
Page size can be reduced by 4.5 MB (46%)
9.9 MB
5.3 MB
In fact, the total size of Vivastudio.co.kr main page is 9.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. 80% 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 9.4 MB which makes up the majority of the site volume.
Potential reduce by 93.2 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 13.0 kB, which is 11% 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 93.2 kB or 78% of the original size.
Potential reduce by 4.4 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, VIVASTUDIO needs image optimization as it can save up to 4.4 MB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.5 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.
Number of requests can be reduced by 58 (68%)
85
27
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VIVASTUDIO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
vivastudio.co.kr
762 ms
vivastudio.co.kr
953 ms
jet.js
291 ms
common.js
187 ms
font-awesome.min.css
67 ms
notosanskr.css
48 ms
kp.js
101 ms
js
110 ms
cid.generate.js
372 ms
wcslog.js
108 ms
optimizer.php
556 ms
optimizer_user.php
560 ms
jquery-3.2.1.min.js
66 ms
swiper-bundle.css
175 ms
swiper-bundle.min.js
72 ms
jquery-1.11.0.min.js
42 ms
jquery-migrate-1.2.1.min.js
53 ms
main_slider.min.js
599 ms
main_slider.js
599 ms
jquery-3.1.0.min.js
781 ms
jquery-1.9.1.min.js
57 ms
snap.js
917 ms
js
140 ms
wp_astg_2.0_mall.js
61 ms
kakao.min.js
166 ms
i18n.php
1320 ms
optimizer.php
1490 ms
optimizer_user.php
756 ms
swiper-bundle.min.js
25 ms
gtm.js
86 ms
icon_201901241804301800.png
1011 ms
24092b1a5a614ab0053a76f16dad0c26.jpg
340 ms
txt_progress.gif
507 ms
icon_201901241804363000.png
1018 ms
search_icon.png
1020 ms
search_btn_x.png
1023 ms
pc_mid_24SS_240306.jpg
2735 ms
mid_pc_231025.jpg
5304 ms
rlqhs.gif
1193 ms
btn_search.gif
1203 ms
5e5ba26e9ef1a3eff0b73ddff8b4b5a5.jpg
403 ms
8a5659a685bddcb8f53a0adf947edbff.jpg
407 ms
00e8324c1f6be7798576882692c45bb7.jpg
538 ms
520fd4a10aca951dcc88c179a7531113.jpg
334 ms
b6c3f3ce6175fed506e9ae3d8847e67d.jpg
342 ms
ec98de1e23713c1b1b60c6c2962356f4.jpg
403 ms
efcf1d24b8e3a7a1edfbb1efcbcf2803.jpg
410 ms
32b3a5df5e3000e25bbb1e3672cc4319.jpg
412 ms
7ed15fdeea62b4c4c21b0da517ba3c14.jpg
415 ms
img_loading.gif
522 ms
web-logo.png
261 ms
HRegular.woff
437 ms
HMedium.woff
388 ms
HLight.woff
389 ms
HBold.woff
436 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLPg9w.woff
48 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgySLPg9w.woff
270 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLPg9w.woff
105 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzmoySLPg9w.woff
104 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLPg9w.woff
105 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzjQ1SLPg9w.woff
103 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01SLPg9w.woff
106 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzmo1SLPg9w.woff
155 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1SLPg9w.woff
154 ms
fbevents.js
37 ms
pc_main_24SS_240510.jpg
1244 ms
fontawesome-webfont.woff
95 ms
tracking.js
1414 ms
storage
803 ms
wpc.php
811 ms
pixel
70 ms
usersync
724 ms
WIDER
40 ms
storage
216 ms
pixel
24 ms
pixel
47 ms
wpg.php
244 ms
usersync
659 ms
button
216 ms
polyfills-4f07b0c20fc9b3d5aa59.js
384 ms
main-8f14ee0978249d4838d8.js
575 ms
webpack-e067438c4cf4ef2ef178.js
578 ms
framework.1cde045124b4a7914091.js
778 ms
f357f4e3.d32c165e533a63787f2e.js
600 ms
cb1608f2.e165191215595e067da9.js
599 ms
958b4c57.32684ee438d552036466.js
610 ms
c943faba.7d1a899dac0432e83bce.js
764 ms
af13d906.a804e7b996dbeb810f1b.js
769 ms
ec1189df.ef5f80c4bafde0f1cc8b.js
784 ms
dfe1566c.66318f9ca02279f24098.js
798 ms
commons.2fae8cec0c3c0c05269b.js
1014 ms
74dfff515e69b5b4dc2cf810cb4cecee4ab83217.ee79573914dddc901e28.js
1144 ms
3f46df925423d5c64a69562d6ae1385432735eb0.1e351bb4edd232575d41.js
960 ms
4b40f431fcde1732c0dd294d0cf9b2fac504dae5.603d37ea579e85699571.js
968 ms
_app-ce0218b53e2c70e207bc.js
1165 ms
b0d83d1a.859f89eb1c277efc1273.js
1400 ms
e8ee99f13f1e4d46881f90903eaae49123b0869d.32c5a0493ffd40825671.js
1342 ms
40332ee1415d5430f4fa0be30d5c1ba7b73cdd43.09d7be1e3fb834180bff.js
1161 ms
f7a9922557e4ecbe96b1a45137be304e5aafa26d.0f3fae6b97f3e7d98060.js
1417 ms
959782938b524824b2749953f9a55103c0edf640.ace172daef085ca5c712.js
1334 ms
button-41ad67c1a3f7c39e119c.js
1357 ms
_buildManifest.js
1358 ms
_ssgManifest.js
1524 ms
wpp.php
200 ms
wpg_a.php
207 ms
vivastudio.co.kr accessibility score
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
Image elements do not have [alt] attributes
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.
vivastudio.co.kr 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
Issues were logged in the Issues panel in Chrome Devtools
vivastudio.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivastudio.co.kr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Vivastudio.co.kr 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.
vivastudio.co.kr
Open Graph data is detected on the main page of VIVASTUDIO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: