6.8 sec in total
670 ms
5.8 sec
331 ms
Visit olzen.co.kr now to see the best up-to-date Olzen content for South Korea and also check out these interesting facts you probably never knew about olzen.co.kr
Visit olzen.co.krWe analyzed Olzen.co.kr page load time and found that the first response time was 670 ms and then it took 6.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.
olzen.co.kr performance score
name
value
score
weighting
Value6.5 s
3/100
10%
Value16.5 s
0/100
25%
Value34.4 s
0/100
10%
Value8,180 ms
0/100
30%
Value0.583
12/100
15%
Value38.9 s
0/100
10%
670 ms
601 ms
385 ms
767 ms
1342 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 90% of them (52 requests) were addressed to the original Olzen.co.kr, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Olzen.co.kr.
Page size can be reduced by 295.3 kB (22%)
1.4 MB
1.1 MB
In fact, the total size of Olzen.co.kr main page is 1.4 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 956.2 kB which makes up the majority of the site volume.
Potential reduce by 8.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 1.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 8.7 kB or 71% of the original size.
Potential reduce by 16.1 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. Olzen images are well optimized though.
Potential reduce by 221.5 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 221.5 kB or 68% of the original size.
Potential reduce by 48.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. Olzen.co.kr needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 84% of the original size.
Number of requests can be reduced by 22 (46%)
48
26
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olzen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
olzen.co.kr
670 ms
main.asp
601 ms
import.css
385 ms
modernizr.custom.js
767 ms
TweenMax.min.js
1342 ms
jquery-1.9.1.min.js
1389 ms
slick.min.js
1182 ms
mighty.base.1.5.0.min.js
756 ms
mighty.slide.4.2.2.min.js
996 ms
matizCoverLayer.3.1.0.min.js
948 ms
default.js
955 ms
main.js
1146 ms
main.css
1154 ms
font.css
811 ms
browser-sync.css
956 ms
opt-default.css
965 ms
layout.css
994 ms
sub.css
1194 ms
member.css
1146 ms
nanumgothic.css
23 ms
analytics.js
75 ms
logo.gif
192 ms
bg_bar1.gif
193 ms
ico_mypage.gif
192 ms
ico_store.gif
198 ms
160315_mainbanner_1.jpg
781 ms
2160315_mainbanner_m.jpg
1154 ms
160201_mainbanner_1.jpg
1342 ms
1160201_mainbanner_m_1.jpg
1392 ms
btn_prev.png
396 ms
btn_next.png
401 ms
160201_banner.jpg
787 ms
1160201_banner.jpg
996 ms
bg_opacity70.png
980 ms
160318_banner.jpg
1373 ms
160201_bottom_banner_01.jpg
1175 ms
160307_bottom_banner_02.jpg
1394 ms
150916_bottom_banner_03.JPG
1535 ms
160307_bottom_banner_04.jpg
1370 ms
160307_bottom_banner_05.jpg
1531 ms
160307_bottom_banner_06.jpg
1562 ms
160201_bottom_banner_07.jpg
1564 ms
150916_bottom_banner_08.JPG
1581 ms
ico_facebook.gif
1588 ms
bg_bar2.gif
1721 ms
ico_blog.gif
1723 ms
logo_footer.png
1754 ms
logo_stylepay.png
1753 ms
paging_on.png
1772 ms
paging.png
1784 ms
georgia-webfont.woff
1910 ms
FuturaBT-Medium.woff
1915 ms
NanumGothic-Bold.woff
30 ms
NanumGothic-ExtraBold.woff
31 ms
NanumGothic-Regular.woff
83 ms
collect
58 ms
georgia-webfont.ttf
202 ms
FuturaBT-Medium.ttf
201 ms
olzen.co.kr 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
olzen.co.kr 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
Uses deprecated APIs
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
olzen.co.kr 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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olzen.co.kr 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 Olzen.co.kr 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.
olzen.co.kr
Open Graph description is not detected on the main page of Olzen. 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: