Tools & Wizards About Us
ezmedicom.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

ezmedicom.com

이지메디컴

Page Load Speed

11.9 sec in total

First Response

599 ms

Resources Loaded

10.4 sec

Page Rendered

868 ms

ezmedicom.com screenshot

About Website

Visit ezmedicom.com now to see the best up-to-date Ezmedicom content and also check out these interesting facts you probably never knew about ezmedicom.com

이지메디컴은 Medical e-Commerce Leader로서 의료 e-Business를 선도하는미래 지향적인 기업으로 구매병원, 공급사, 투자자 모두의 Win-Win을 약속드립니다.

Visit ezmedicom.com

Key Findings

We analyzed Ezmedicom.com page load time and found that the first response time was 599 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

ezmedicom.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value47.9 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value370 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

ezmedicom.com

599 ms

index

397 ms

gtm.js

57 ms

aos.css

402 ms

swiper-bundle.min.css

569 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 89% of them (118 requests) were addressed to the original Ezmedicom.com, 8% (10 requests) were made to Cdn.jsdelivr.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Ezmedicom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (10%)

Content Size

16.6 MB

After Optimization

14.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ezmedicom.com main page is 16.6 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. Only a small number of websites need less resources to load. Images take 16.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 46.8 kB

  • Original 55.2 kB
  • After minification 37.7 kB
  • After compression 8.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 17.5 kB, which is 32% 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 46.8 kB or 85% of the original size.

Image Optimization

-8%

Potential reduce by 1.3 MB

  • Original 16.0 MB
  • After minification 14.7 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. Ezmedicom images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 280.1 kB

  • Original 398.3 kB
  • After minification 382.3 kB
  • After compression 118.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 280.1 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 120.1 kB

  • Original 141.3 kB
  • After minification 124.9 kB
  • After compression 21.2 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. Ezmedicom.com needs all CSS files to be minified and compressed as it can save up to 120.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (23%)

Requests Now

120

After Optimization

93

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezmedicom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ezmedicom.com

ezmedicom.com

599 ms

index

index

397 ms

gtm.js

gtm.js

57 ms

aos.css

aos.css

402 ms

swiper-bundle.min.css

swiper-bundle.min.css

569 ms

popup.css

popup.css

573 ms

main.css

main.css

950 ms

jquery.min.js

jquery.min.js

1167 ms

gsap.min.js

gsap.min.js

993 ms

swiper-bundle.min.js

swiper-bundle.min.js

884 ms

aos.js

aos.js

761 ms

custom.js

custom.js

765 ms

jquery.cookie.js

jquery.cookie.js

952 ms

common.js

common.js

957 ms

custom.popup.js

custom.popup.js

1096 ms

main.js

main.js

1143 ms

js

js

69 ms

countUp.js

countUp.js

960 ms

noframework.waypoints.js

noframework.waypoints.js

969 ms

scroll_countup.js

scroll_countup.js

1010 ms

reset.css

reset.css

340 ms

base.css

base.css

384 ms

style.css

style.css

394 ms

css2

css2

34 ms

pretendard.css

pretendard.css

36 ms

logo.png

logo.png

196 ms

ic_ezbot.png

ic_ezbot.png

255 ms

topvisual_img01.jpg

topvisual_img01.jpg

3130 ms

topvisual_img02.jpg

topvisual_img02.jpg

2375 ms

topvisual_img03.jpg

topvisual_img03.jpg

1569 ms

main_banner_01.jpg

main_banner_01.jpg

377 ms

main_list_bg.png

main_list_bg.png

1875 ms

list_img_01.png

list_img_01.png

850 ms

list_img_02.png

list_img_02.png

656 ms

list_img_03.png

list_img_03.png

1036 ms

list_img_04.png

list_img_04.png

1252 ms

listobx_01_bg.png

listobx_01_bg.png

2738 ms

listobx_02_bg.png

listobx_02_bg.png

2643 ms

listobx_03_bg.png

listobx_03_bg.png

2899 ms

listobx_04_bg.png

listobx_04_bg.png

3382 ms

management_bg.jpg

management_bg.jpg

4088 ms

icon_01.png

icon_01.png

2845 ms

main_list_arrow.png

main_list_arrow.png

2928 ms

icon_02.png

icon_02.png

3046 ms

icon_03.png

icon_03.png

3091 ms

icon_04.png

icon_04.png

3118 ms

icon_05.png

icon_05.png

3248 ms

sliderlist_img_bg_01.png

sliderlist_img_bg_01.png

4234 ms

ic_manage_01_m.png

ic_manage_01_m.png

3310 ms

sliderlist_img_bg_02.png

sliderlist_img_bg_02.png

4104 ms

ic_manage_02_m.png

ic_manage_02_m.png

3448 ms

sliderlist_img_bg_03.png

sliderlist_img_bg_03.png

4453 ms

ic_manage_03_m.png

ic_manage_03_m.png

3572 ms

sliderlist_img_bg_04.png

sliderlist_img_bg_04.png

4593 ms

ic_manage_04_m.png

ic_manage_04_m.png

3798 ms

sliderlist_img_bg_05.png

sliderlist_img_bg_05.png

4932 ms

ic_manage_05_m.png

ic_manage_05_m.png

4280 ms

banner_01.png

banner_01.png

4301 ms

banner_01_m.png

banner_01_m.png

4426 ms

banner_02.png

banner_02.png

4473 ms

banner_02_m.png

banner_02_m.png

4498 ms

Pretendard-Regular.woff

Pretendard-Regular.woff

74 ms

Pretendard-Medium.woff

Pretendard-Medium.woff

87 ms

Pretendard-Light.woff

Pretendard-Light.woff

194 ms

Pretendard-ExtraLight.woff

Pretendard-ExtraLight.woff

193 ms

Pretendard-Thin.woff

Pretendard-Thin.woff

195 ms

Pretendard-SemiBold.woff

Pretendard-SemiBold.woff

190 ms

Pretendard-Bold.woff

Pretendard-Bold.woff

194 ms

Pretendard-ExtraBold.woff

Pretendard-ExtraBold.woff

198 ms

Pretendard-Black.woff

Pretendard-Black.woff

197 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

banner_03.png

banner_03.png

4434 ms

chkAccessInit

chkAccessInit

4414 ms

banner_03_m.png

banner_03_m.png

4294 ms

banner_04.png

banner_04.png

4044 ms

banner_04_m.png

banner_04_m.png

3949 ms

banner_05.png

banner_05.png

3779 ms

banner_05_m.png

banner_05_m.png

3614 ms

banner_06.png

banner_06.png

3296 ms

banner_06_m.png

banner_06_m.png

3024 ms

banner_07.png

banner_07.png

2627 ms

banner_07_m.png

banner_07_m.png

2364 ms

banner_08.png

banner_08.png

2318 ms

banner_08_m.png

banner_08_m.png

2213 ms

banner_09.png

banner_09.png

2196 ms

banner_09_m.png

banner_09_m.png

2198 ms

banner_10.png

banner_10.png

2154 ms

banner_10_m.png

banner_10_m.png

2110 ms

banner_11.png

banner_11.png

2128 ms

banner_11_m.png

banner_11_m.png

2132 ms

banner_12.png

banner_12.png

2044 ms

banner_12_m.png

banner_12_m.png

2007 ms

banner_13.png

banner_13.png

2020 ms

banner_13_m.png

banner_13_m.png

1944 ms

banner_14.png

banner_14.png

1890 ms

banner_14_m.png

banner_14_m.png

1669 ms

banner_15.png

banner_15.png

1401 ms

banner_15_m.png

banner_15_m.png

1403 ms

banner_16.png

banner_16.png

1352 ms

banner_16_m.png

banner_16_m.png

1321 ms

banner_17.png

banner_17.png

1477 ms

banner_17_m.png

banner_17_m.png

1233 ms

banner_18.png

banner_18.png

1231 ms

banner_18_m.png

banner_18_m.png

1224 ms

banner_19.png

banner_19.png

1280 ms

banner_19_m.png

banner_19_m.png

1211 ms

banner_20.png

banner_20.png

1237 ms

banner_20_m.png

banner_20_m.png

1378 ms

banner_21.png

banner_21.png

1221 ms

banner_21_m.png

banner_21_m.png

1276 ms

banner_22.png

banner_22.png

1177 ms

banner_22_m.png

banner_22_m.png

1194 ms

banner_23.png

banner_23.png

1187 ms

banner_23_m.png

banner_23_m.png

1220 ms

banner_24.png

banner_24.png

1269 ms

banner_24_m.png

banner_24_m.png

1232 ms

banner_25.png

banner_25.png

1209 ms

banner_25_m.png

banner_25_m.png

1435 ms

banner_26.png

banner_26.png

1185 ms

banner_26_m.png

banner_26_m.png

1219 ms

banner_27.png

banner_27.png

1263 ms

banner_27_m.png

banner_27_m.png

1234 ms

d894ba2c06844c79851e4b48c4a6893a.png

d894ba2c06844c79851e4b48c4a6893a.png

2201 ms

quick_icon_02_over.png

quick_icon_02_over.png

1230 ms

quick_icon_01_over.png

quick_icon_01_over.png

1219 ms

quick_icon_03_over.png

quick_icon_03_over.png

1292 ms

quick_icon_04_over.png

quick_icon_04_over.png

1260 ms

quick_icon_05_over.png

quick_icon_05_over.png

1305 ms

footer_logo.png

footer_logo.png

1245 ms

footer_icon_01.png

footer_icon_01.png

1256 ms

footer_icon_02.png

footer_icon_02.png

1281 ms

footer_icon_03.png

footer_icon_03.png

1275 ms

Accessibility Review

ezmedicom.com accessibility score

89

Accessibility Issues

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ezmedicom.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ezmedicom.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezmedicom.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 Ezmedicom.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.

Social Sharing Optimization

ezmedicom.com

Open Graph description is not detected on the main page of Ezmedicom. 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: