10.6 sec in total
708 ms
9.7 sec
178 ms
Click here to check amazing MACROGEN content for Egypt. Otherwise, check out these important facts you probably never knew about macrogen.com
내 몸 사용 설명서를 제공하여 인류의 건강한 삶을 돕는 글로벌 헬스케어 기업 마크로젠
Visit macrogen.comWe analyzed Macrogen.com page load time and found that the first response time was 708 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
macrogen.com performance score
name
value
score
weighting
Value23.8 s
0/100
10%
Value28.2 s
0/100
25%
Value23.8 s
0/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value25.4 s
0/100
10%
708 ms
1058 ms
916 ms
5 ms
640 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 98% of them (152 requests) were addressed to the original Macrogen.com, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Macrogen.com.
Page size can be reduced by 75.3 kB (17%)
446.8 kB
371.5 kB
In fact, the total size of Macrogen.com main page is 446.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 378.0 kB which makes up the majority of the site volume.
Potential reduce by 30.0 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 7.8 kB, which is 21% 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 30.0 kB or 83% of the original size.
Potential reduce by 33.2 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. MACROGEN images are well optimized though.
Potential reduce by 6.3 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 6.3 kB or 25% of the original size.
Potential reduce by 5.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. Macrogen.com needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 76% of the original size.
Number of requests can be reduced by 49 (32%)
153
104
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MACROGEN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
macrogen.com
708 ms
1058 ms
index.css
916 ms
jquery-1.7.2.min.js
5 ms
common.js
640 ms
scroll.js
205 ms
base.css
314 ms
ga.js
39 ms
pop_140120_4.jpg
1223 ms
ci.gif
318 ms
util_bl.gif
302 ms
util_home.gif
400 ms
util_sitemap.gif
606 ms
dot_global.gif
607 ms
dropbox.gif
609 ms
ko_flag.gif
638 ms
eng_flag.gif
596 ms
chi_flag.gif
797 ms
fran_flag.gif
914 ms
ger_flag.gif
915 ms
spa_flag.gif
915 ms
por_flag.gif
961 ms
gnb1.png
997 ms
gnb2.png
1215 ms
gnb3.png
1216 ms
gnb4.png
1217 ms
gnb5.png
1276 ms
gnb7.gif
1192 ms
gnb1_snb1.png
1389 ms
gnb1_snb2.png
1513 ms
gnb1_snb4.png
1514 ms
gnb1_snb5.png
1516 ms
gnb1_snb6.png
1421 ms
gnb5_snb3.png
1591 ms
gnb1_snb7.png
1584 ms
gnb1_snb8.png
1625 ms
gnb2_snb1.png
1816 ms
gnb2_snb2.png
1817 ms
gnb2_snb4.png
1819 ms
gnb3_snb1.png
1781 ms
gnb3_snb2.png
1910 ms
gnb3_snb3.png
1827 ms
gnb3_snb4.png
1978 ms
gnb3_snb5.png
2116 ms
__utm.gif
11 ms
gnb3_snb7.png
1832 ms
gnb4_snb1.png
1817 ms
gnb5_snb2.png
1638 ms
gnb5_snb4.png
1643 ms
index_bg.jpg
2799 ms
index_img1.gif
1633 ms
dot_bg.gif
1826 ms
index_img1.png
1801 ms
btn_more.png
1642 ms
index_img2.png
1644 ms
btn_pre.png
1527 ms
btn_next.png
1821 ms
num1_ov.gif
1779 ms
num2.gif
1744 ms
f_ci.gif
1454 ms
f_ci3.gif
1984 ms
f_contact_title1.gif
1634 ms
f_contact_img1_1.gif
1826 ms
f_contact_img1_2.gif
1828 ms
f_contact_img1_3.gif
1771 ms
f_contact_title2.gif
1666 ms
f_contact_img2_1.gif
1929 ms
f_contact_img2_2.gif
1841 ms
f_contact_img2_3.gif
1841 ms
f_contact_title3.gif
1742 ms
f_contact_img3_1.gif
1930 ms
f_contact_img3_2.gif
1871 ms
f_contact_img3_3.gif
2022 ms
f_contact_title4.gif
1868 ms
f_contact_img4_1.gif
1836 ms
f_contact_img4_2.gif
1782 ms
f_contact_img4_3.gif
1846 ms
copyright.gif
1999 ms
footer_bg.gif
1886 ms
index_img007.gif
2270 ms
index_img005.gif
1916 ms
index_img004.gif
1827 ms
index_img003.gif
1742 ms
index_img002.gif
1866 ms
index_img001.gif
1911 ms
snb1_ov.gif
205 ms
snb2_ov.gif
325 ms
snb3_ov.gif
310 ms
snb4_ov.gif
310 ms
snb5_ov.gif
199 ms
snb6_ov.gif
311 ms
snb7_ov.gif
398 ms
snb8_ov.gif
407 ms
snb9_ov.gif
607 ms
gnb1_ov.gif
608 ms
gnb2_ov.gif
608 ms
gnb3_ov.gif
636 ms
gnb4_ov.gif
594 ms
gnb5_ov.gif
609 ms
gnb6_ov.gif
791 ms
gnb1_snb1_ov.gif
902 ms
gnb1_snb2_ov.gif
902 ms
gnb1_snb3_ov.gif
904 ms
gnb1_snb4_ov.gif
812 ms
gnb1_snb5_ov.gif
947 ms
gnb1_snb6_ov.gif
987 ms
gnb1_snb7_ov.gif
1015 ms
util_home_ov.gif
1201 ms
util_sitemap_ov.gif
1203 ms
util_global_ov.gif
1205 ms
s_service_img1_ov.gif
1262 ms
s_service_img2_ov.gif
1181 ms
s_service_img3_ov.gif
1214 ms
history_img1_ov.gif
1378 ms
snb7-1_ov.gif
1505 ms
snb7-2_ov.gif
1505 ms
snb7-3_ov.gif
1508 ms
research_img1_on.gif
1416 ms
research_img3_ov.gif
1581 ms
gnb1_ov.gif
1572 ms
gnb2_ov.gif
1615 ms
gnb3_ov.gif
1624 ms
gnb4_ov.gif
1621 ms
gnb5_ov.gif
1517 ms
gnb6_ov.gif
1475 ms
btn_pre_ov.png
1605 ms
btn_next_ov.png
1510 ms
gnb1_snb1_ov.png
1584 ms
gnb1_snb2_ov.png
1715 ms
gnb1_snb3_ov.png
1527 ms
gnb1_snb4_ov.png
1520 ms
gnb1_snb5_ov.png
1430 ms
gnb1_snb6_ov.png
1622 ms
gnb1_snb7_ov.png
1569 ms
gnb1_snb8_ov.png
1604 ms
gnb2_snb1_ov.png
1634 ms
gnb2_snb2_ov.png
1612 ms
gnb2_snb3_ov.png
1526 ms
gnb2_snb4_ov.png
1472 ms
gnb3_snb1_ov.png
1644 ms
gnb3_snb2_ov.png
1494 ms
gnb3_snb3_ov.png
1583 ms
gnb3_snb4_ov.png
1715 ms
gnb3_snb5_ov.png
1546 ms
gnb3_snb6_ov.png
1532 ms
gnb3_snb7_ov.png
1441 ms
gnb4_snb1_ov.png
1667 ms
gnb4_snb2_ov.png
1549 ms
gnb4_snb3_ov.png
1581 ms
gnb4_snb4_ov.png
1656 ms
gnb5_snb1_ov.png
1618 ms
gnb5_snb2_ov.png
1532 ms
gnb5_snb3_ov.png
1453 ms
gnb6_snb1_ov.png
1538 ms
gnb2_ov.png
1608 ms
macrogen.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.
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
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.
macrogen.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
macrogen.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 uses legible font sizes
EN
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Macrogen.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Macrogen.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
macrogen.com
Open Graph description is not detected on the main page of MACROGEN. 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: