6.2 sec in total
1.1 sec
5.1 sec
61 ms
Welcome to wettrustglobal.com homepage info - get ready to check Wettrust Global best content for South Korea right away, or after learning these important things about wettrustglobal.com
Wettrust, company specialized in feminine care, is a brand owner and manufacturer of both medical devices and cosmetics.
Visit wettrustglobal.comWe analyzed Wettrustglobal.com page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wettrustglobal.com performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value11.3 s
0/100
25%
Value12.8 s
3/100
10%
Value470 ms
61/100
30%
Value0.001
100/100
15%
Value16.2 s
5/100
10%
1103 ms
95 ms
523 ms
515 ms
533 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wettrustglobal.com, 20% (16 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Wettrust.com.
Page size can be reduced by 2.7 MB (23%)
11.9 MB
9.2 MB
In fact, the total size of Wettrustglobal.com main page is 11.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 11.4 MB which makes up the majority of the site volume.
Potential reduce by 31.3 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 4.3 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 31.3 kB or 83% of the original size.
Potential reduce by 2.3 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, Wettrust Global needs image optimization as it can save up to 2.3 MB 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 278.2 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 278.2 kB or 69% of the original size.
Potential reduce by 93.9 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. Wettrustglobal.com needs all CSS files to be minified and compressed as it can save up to 93.9 kB or 82% of the original size.
Number of requests can be reduced by 30 (51%)
59
29
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wettrust Global. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.wettrust.com
1103 ms
js
95 ms
jquery-1.11.3.min.js
523 ms
jquery-migrate-1.2.1.min.js
515 ms
jquery.easing.1.3.js
533 ms
slick.min.js
702 ms
slick.css
533 ms
swiper.min.js
1040 ms
swiper-bundle.css
684 ms
aos.js
697 ms
aos.css
867 ms
font.css
700 ms
common.css
853 ms
common.js
871 ms
jquery.mousewheel.min.js
874 ms
TweenLite.min.js
46 ms
ScrollToPlugin.min.js
55 ms
waypoints.min.js
61 ms
jquery.sticky.js
880 ms
lodash.min.js
1022 ms
jquery.fullpage.min.css
1038 ms
jquery.fullpage.min.js
1046 ms
index.js
1047 ms
jquery-ui.js
41 ms
js
64 ms
webfont.js
38 ms
css2
28 ms
css
46 ms
css2
48 ms
index_pc.css
177 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoyeLQ.ttf
512 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgyeLQ.ttf
544 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQyeLQ.ttf
543 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozeLQ.ttf
542 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01eLQ.ttf
543 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1eLQ.ttf
544 ms
index_tablet.css
249 ms
css
29 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
510 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
513 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
521 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
522 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
523 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
524 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
524 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
524 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
525 ms
main_logo.png
213 ms
b_file_1612159198wqm6bkuvhq.png
1430 ms
b_file_16121591230fdgkqrwee.png
1413 ms
b_file_1605260743tl3mfwmgx3.jpg
212 ms
b_file_1605260472crfqhjatu2.jpg
212 ms
b_file_1605260361quxz496z57.jpg
391 ms
b_file_1605260180emcobdhv5j.jpg
390 ms
arr_prev.png
387 ms
arr_next.png
386 ms
foot_logo.png
572 ms
sns_icon1.png
573 ms
sns_icon2.png
573 ms
sns_icon3.png
574 ms
quick_icon1.png
725 ms
quick_icon2.png
731 ms
side_nav_dot_icon.png
703 ms
file1_164904998939iamof2x1.jpg
1407 ms
file1_1649320582c6zxqvlf63.png
1531 ms
file2_1649320639lcsa9vpm7y.png
2067 ms
file1_1649319063fb72lxft3v.png
1578 ms
file2_1649319117c6u6yygqkw.png
1546 ms
file1_1622078200x77mc6gvsl.jpg
1564 ms
file2_1622077827cvj8rtwczn.jpg
1583 ms
board_play_btn1.png
1700 ms
foot_wave01.png
1720 ms
foot_wave02.png
1740 ms
foot_wave03.png
1753 ms
HelveticaNeue-Light.otf
1755 ms
HelveticaNeue-Bold.otf
1822 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLPg9A.ttf
430 ms
NotoSansKR-Black-Hestia.woff
99 ms
NotoSansKR-Bold-Hestia.woff
144 ms
index_mobile.css
176 ms
wettrustglobal.com 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
Buttons do not have an accessible 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.
wettrustglobal.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wettrustglobal.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wettrustglobal.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wettrustglobal.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.
wettrustglobal.com
Open Graph description is not detected on the main page of Wettrust Global. 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: