23.6 sec in total
1.6 sec
21.4 sec
513 ms
Welcome to g-enews.com homepage info - get ready to check G Enews best content for South Korea right away, or after learning these important things about g-enews.com
빠르고 깊이있는 글로벌 뉴스와 경제·금융 중심의 종합경제일간지
Visit g-enews.comWe analyzed G-enews.com page load time and found that the first response time was 1.6 sec and then it took 22 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
g-enews.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value13.9 s
0/100
25%
Value15.9 s
0/100
10%
Value720 ms
41/100
30%
Value0.609
10/100
15%
Value13.2 s
12/100
10%
1634 ms
16292 ms
16069 ms
14527 ms
86 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original G-enews.com, 61% (44 requests) were made to Nimage.globaleconomic.co.kr and 7% (5 requests) were made to Adkpf.newscloud.or.kr. The less responsive or slowest element that took the longest time to load (16.3 sec) relates to the external source Nimage.globaleconomic.co.kr.
Page size can be reduced by 208.1 kB (51%)
411.0 kB
202.9 kB
In fact, the total size of G-enews.com main page is 411.0 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. 35% of websites need less resources to load. Images take 159.2 kB which makes up the majority of the site volume.
Potential reduce by 76.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 76.5 kB or 81% of the original size.
Potential reduce by 27.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, G Enews needs image optimization as it can save up to 27.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 101.1 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 101.1 kB or 66% of the original size.
Potential reduce by 2.8 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. G-enews.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 73% of the original size.
Number of requests can be reduced by 6 (9%)
70
64
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G Enews. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
1634 ms
econ.css
16292 ms
jquery.min.js
16069 ms
sns_shared.js
14527 ms
wcslog.js
86 ms
plugin.min.js
534 ms
common@top_left
951 ms
common@top_right
969 ms
popup_pc.php
534 ms
index.jsp
1207 ms
common@gongsi_down
939 ms
common.png
671 ms
201604081528103246893_20160408153132_01.jpg
904 ms
dummy.png
264 ms
common_alpha.png
459 ms
201604071808041919459_20160408062138_01.jpg
470 ms
201604071910061983897_20160407191125_01.jpg
468 ms
201604071900251940794_20160407190346_01.jpg
472 ms
201604081646243528901_20160408164701_01.jpg
866 ms
201604081321142907391_20160408134323_01.jpg
675 ms
201604081501173154781_20160408150544_01.jpg
896 ms
201604080838422305414_20160408090318_01.jpg
677 ms
201604071748121878913_20160407184115_01.jpg
891 ms
201604080653102145991_20160408065702_01.jpg
1131 ms
IRPR_banner.gif
894 ms
Navi_banner.gif
1080 ms
201604071650351687399_20160407165353_01.jpg
1128 ms
201604071902531958467_20160407194426_01.jpg
1128 ms
201604071931532001605_20160407193324_01.jpg
1134 ms
201512311413092777428_20151231141818_01.jpg
1150 ms
201604071952472023457_20160407195304_01.jpg
1362 ms
201604051943519897138_20160405194854_01.jpg
1374 ms
201604050832128287455_20160405084219_01.jpg
1370 ms
201604050853198377214_20160405085512_01.jpg
1373 ms
201604050814088237380_20160405081705_01.jpg
1373 ms
201604041452227257636_20160404150232_01.jpg
1379 ms
201604090020000474134_20160409002737_01.jpg
1573 ms
20160408214709_fd_image_175_198_30__9618.jpg
1574 ms
201604082103360427071_20160408210802_01.jpg
1576 ms
201604082318390466504_20160408232811_01.jpg
1577 ms
201604061952071466250_20160406195742_01.jpg
1786 ms
201604062351420029322_20160407000639_05.jpg
1589 ms
201604081627233467170_20160408162753_01.jpg
2181 ms
common@typenews_down_right-2
747 ms
common@typenews_down_right
755 ms
201604081644353503365_20160408165430_01.jpg
1624 ms
201604081056332626617_20160408110253_01.jpg
1623 ms
201604081523533223892_20160408152546_01.jpg
1827 ms
201604071609421483568_20160407161808_01.jpg
1638 ms
analytics.js
94 ms
201604081601553396661_20160408160314_01.jpg
1725 ms
201604081709550039273_20160408171038_01.jpg
1541 ms
201604081745380197206_20160408174706_01.jpg
1539 ms
black-opacity-80.png
1565 ms
IRPR_sago.jpg
1938 ms
layout_future.css
963 ms
prefs
463 ms
56e680516c122694086982.jpg
1343 ms
5587655593829321758028.jpg
1818 ms
56fa002356ebb454880917.png
1615 ms
5673a1ca7a739699125241.jpg
1328 ms
564bd6df99533505079744.jpg
1325 ms
visit
152 ms
collect
17 ms
collect
90 ms
U0001.gif
970 ms
line_area_2.gif
245 ms
icon_open.gif
448 ms
icon_view.gif
452 ms
U2001.gif
965 ms
U0101.gif
974 ms
UKp200.gif
963 ms
g-enews.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
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.
g-enews.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
g-enews.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G-enews.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 G-enews.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.
g-enews.com
Open Graph description is not detected on the main page of G Enews. 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: