6.7 sec in total
1.9 sec
4.6 sec
183 ms
Welcome to ecofem.or.kr homepage info - get ready to check Ecofem best content for South Korea right away, or after learning these important things about ecofem.or.kr
작고 소박한 일상으로부터 녹색의 대안을 실천하는 사람들과 함께 합니다.
Visit ecofem.or.krWe analyzed Ecofem.or.kr page load time and found that the first response time was 1.9 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ecofem.or.kr performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value25.1 s
0/100
25%
Value14.5 s
1/100
10%
Value1,480 ms
14/100
30%
Value0.3
39/100
15%
Value26.7 s
0/100
10%
1912 ms
402 ms
402 ms
408 ms
412 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 76% of them (71 requests) were addressed to the original Ecofem.or.kr, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Ecofem.or.kr.
Page size can be reduced by 870.5 kB (58%)
1.5 MB
618.0 kB
In fact, the total size of Ecofem.or.kr main page is 1.5 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. 85% 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. Javascripts take 630.7 kB which makes up the majority of the site volume.
Potential reduce by 68.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. 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 68.7 kB or 78% of the original size.
Potential reduce by 24.5 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. Ecofem images are well optimized though.
Potential reduce by 431.6 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 431.6 kB or 68% of the original size.
Potential reduce by 345.7 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. Ecofem.or.kr needs all CSS files to be minified and compressed as it can save up to 345.7 kB or 83% of the original size.
Number of requests can be reduced by 53 (62%)
85
32
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecofem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
ecofem.or.kr
1912 ms
wp-emoji-release.min.js
402 ms
batch.css
402 ms
style.css
408 ms
styles.css
412 ms
font-awesome.min.css
424 ms
srr-css.css
602 ms
colorbox.css
603 ms
styles.css
606 ms
normalize.css
619 ms
skeleton.css
635 ms
base.css
802 ms
style.css
806 ms
superfish.css
810 ms
prettyPhoto.css
825 ms
font-awesome.min.css
847 ms
flexslider.css
1002 ms
media-queries.css
1005 ms
addtoany.min.css
1010 ms
tw-recent-posts-widget.css
1027 ms
batch.js
1031 ms
jquery.js
1269 ms
jquery-migrate.min.js
1201 ms
srr-js.js
1208 ms
jquery.colorbox-min.js
1214 ms
custom.js
1233 ms
ytprefs.min.js
1237 ms
ajaxhandlergplwt.js
1782 ms
modernizr.custom.17475.js
624 ms
jquery.easing.min.js
630 ms
jquery.prettyPhoto.js
655 ms
jquery.mobilemenu.js
658 ms
jquery.superfish.js
693 ms
jflickrfeed.js
825 ms
jquery.elastislide.js
833 ms
jquery.fitvids.js
861 ms
jquery.flexslider.js
865 ms
jquery.isotope.min.js
906 ms
jquery.imagesloaded.min.js
1029 ms
custom.js
1051 ms
comment-reply.min.js
1163 ms
jquery.form.min.js
1163 ms
scripts.js
1165 ms
fitvids.min.js
1256 ms
css
26 ms
nanumgothic.css
54 ms
wp-embed.min.js
1230 ms
iframe_api
21 ms
www-widgetapi.js
18 ms
pattern-alt.gif
646 ms
ecofem.or.kr
1521 ms
%EC%97%AC%EC%84%B1%ED%99%98%EA%B2%BD%EC%97%B0%EB%8C%80-%EB%A1%9C%EA%B3%A0-%EA%B7%B8%EB%A6%BC%ED%8C%8C%EC%9D%BC2.jpg
434 ms
loader.gif
434 ms
2261565950.jpg
1033 ms
3332988356.jpg
1039 ms
1706390514.jpg
871 ms
%EB%84%A4%EC%9D%B4%EB%B2%84%EB%B8%94%EB%A1%9C%EA%B7%B81.png
630 ms
%EC%9E%90%EB%A3%8C%EC%A7%91.png
622 ms
%ED%8A%B8%EC%9C%84%ED%84%B0.png
828 ms
%ED%8E%98%EC%9D%B4%EC%8A%A4%EB%B6%81.png
839 ms
%ED%95%B4%ED%94%BC%EB%B9%88.png
1036 ms
%ED%9B%84%EC%9B%90%ED%95%98%EA%B8%B0.png
1054 ms
%EC%97%90%EC%BD%94%ED%8E%98%EB%AF%B8%EB%8B%88%EC%A6%98%ED%95%99%EA%B5%90.png
1073 ms
%EC%9C%A0%EB%B0%A9%EC%95%94.png
1242 ms
%EC%97%90%EC%BD%94%ED%99%94%EC%9E%A5%ED%92%88.png
1243 ms
%EB%B0%A5%EA%BD%83%EB%8B%AC.png
1240 ms
%EC%96%B4%EB%A6%B0%EC%9D%B4%EA%B1%B4%EA%B0%95%ED%95%9C%ED%95%99%EA%B5%90.png
1266 ms
%EB%82%98%EB%8A%94%EB%8B%AC.png
1276 ms
%EC%B4%88%EB%A1%9D%EC%83%81%EC%83%81.jpg
1441 ms
%EB%8D%94%EC%B4%88%EB%A1%9D.jpg
1449 ms
%ED%8E%98%EC%BD%94.jpg
1447 ms
%EB%A7%88%EB%A5%B4%EC%89%90.jpg
1479 ms
DpqJfzGG0oE
205 ms
hr-dashed.gif
1447 ms
NanumGothic-Regular.woff
138 ms
NanumGothic-Bold.woff
140 ms
NanumGothic-ExtraBold.woff
142 ms
fontawesome-webfont.woff
1611 ms
fontawesome-webfont.woff
1626 ms
page.js
89 ms
count.js
92 ms
www-embed-player-vflfNyN_r.css
205 ms
www-embed-player.js
218 ms
base.js
272 ms
all.js
145 ms
overlay.png
1251 ms
184 ms
xd_arbiter.php
31 ms
xd_arbiter.php
41 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
44 ms
ad_status.js
49 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
29 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
33 ms
ping
38 ms
ecofem.or.kr 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
ecofem.or.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ecofem.or.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
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecofem.or.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 Ecofem.or.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.
ecofem.or.kr
Open Graph data is detected on the main page of Ecofem. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: