10.9 sec in total
21 ms
10.6 sec
336 ms
Click here to check amazing Wevity content for South Korea. Otherwise, check out these important facts you probably never knew about wevity.com
대학생 공모전 사이트 대외활동 서포터즈 모집 추천 아이디어 마케팅 광고 일러스트 디자인 웹툰 만화 미술 사진 소설 문학 시 ucc 영상 창업 경진대회
Visit wevity.comWe analyzed Wevity.com page load time and found that the first response time was 21 ms and then it took 10.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.
wevity.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value6.2 s
11/100
25%
Value11.5 s
5/100
10%
Value650 ms
46/100
30%
Value0
100/100
15%
Value14.9 s
8/100
10%
21 ms
854 ms
2068 ms
35 ms
26 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 92% of them (72 requests) were addressed to the original Wevity.com, 3% (2 requests) were made to T1.daumcdn.net and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Wevity.com.
Page size can be reduced by 1.1 MB (34%)
3.1 MB
2.0 MB
In fact, the total size of Wevity.com main page is 3.1 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. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 81.7 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 15.8 kB, which is 17% 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 81.7 kB or 87% of the original size.
Potential reduce by 966.8 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, Wevity needs image optimization as it can save up to 966.8 kB or 34% 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.8 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 1.1 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. Wevity.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 12% of the original size.
Number of requests can be reduced by 15 (20%)
75
60
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wevity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wevity.com
21 ms
wevity.com
854 ms
www.wevity.com
2068 ms
jquery-1.10.2.min.js
35 ms
jquery.easing.1.3.js
26 ms
jquery.bxslider.min.js
25 ms
design.js
23 ms
ui.common.js
25 ms
ui.message.js
34 ms
jquery.zeroclipboard.js
46 ms
jquery.bxslider.css
32 ms
design.css
878 ms
board.css
48 ms
js
60 ms
wcslog.js
22 ms
ui.calendar.js
49 ms
ba.min.js
18 ms
nanumgothic.css
29 ms
css
45 ms
noimgs.png
817 ms
20240801034908_25cf78bd.jpg
810 ms
m_btn_plus.png
854 ms
m_btn_menu.png
840 ms
logo_wevity.png
16 ms
btn_facebook.png
842 ms
btn_twitter.png
876 ms
m_btn_close.png
1590 ms
20240801034845_79dcea2c.jpg
821 ms
bg_left.png
1690 ms
bg_right.png
853 ms
btn_quick.png
1706 ms
img_customer.png
862 ms
20240619110935_40fdf0ba.jpg
863 ms
bg_msidea2.png
1658 ms
20240715004804_61e287aa.jpg
878 ms
20240719113906_f5bd7f2a.jpg
886 ms
20240730163109_0b75cf06.jpg
1691 ms
20240819171536_de1f2c10.jpg
1734 ms
20240715005058_614fd481.jpg
2389 ms
20240624142118_b9e52465.jpg
2479 ms
20240723103636_b9169d5b.png
2534 ms
20240812074255_d979ef5c.png
2549 ms
20240812100249_4b5fc10e.png
2590 ms
20240619010754_2dc9b0b3.png
2708 ms
btn_reg.png
2399 ms
btn_bigreg.png
3267 ms
20240819171356_bcafad98.jpg
2489 ms
20240807020308_bf66f51f.jpg
3441 ms
20240624141613_ea5706ad.jpg
2544 ms
20240719155153_9d942bfd.jpg
3594 ms
20240730162844_02cb2d9d.jpg
3619 ms
20240814155323_3e51172d.jpg
4019 ms
20240610175721_724aa0bd.jpg
2717 ms
20240812100040_bb9bbe74.png
2732 ms
20240723103509_576934c2.png
2743 ms
20240729154402_de993334.jpg
2730 ms
ct2.html
12 ms
20240812073756_41ca3c5a.png
3255 ms
20240814024345_f40f72fd.jpg
3443 ms
20240728215035_da82e482.jpg
3429 ms
20240813153646_d03505c1.jpg
4248 ms
20240619105729_8e54e191.jpg
2777 ms
20240724050217_681781e1.jpg
2788 ms
20240728221720_f6f80ab4.jpg
4394 ms
m_mailing.png
4441 ms
logo_footer.gif
3204 ms
bg_header.gif
4418 ms
bg_searchbar.png
4396 ms
btn_search.png
3691 ms
bg_newmainmenu.gif
4613 ms
bg_m_menu.gif
4608 ms
bg_cat.png
4614 ms
bg_msidea.png
4591 ms
bg_msnotice.png
4559 ms
bg_list.gif
3917 ms
bx_loader.gif
4727 ms
controls.png
4655 ms
main.js
3544 ms
wevity.com accessibility score
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
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
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.
wevity.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wevity.com 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
![]()
KO
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wevity.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Wevity.com 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.
wevity.com
Open Graph data is detected on the main page of Wevity. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: