13.1 sec in total
621 ms
12 sec
507 ms
Welcome to ediya.com homepage info - get ready to check EDIYA best content for South Korea right away, or after learning these important things about ediya.com
Always Beside you. 이디야커피 공식홈페이지입니다.
Visit ediya.comWe analyzed Ediya.com page load time and found that the first response time was 621 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ediya.com performance score
name
value
score
weighting
Value18.0 s
0/100
10%
Value38.3 s
0/100
25%
Value21.2 s
0/100
10%
Value460 ms
61/100
30%
Value0.308
38/100
15%
Value30.8 s
0/100
10%
621 ms
1227 ms
82 ms
588 ms
1384 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 89% of them (105 requests) were addressed to the original Ediya.com, 8% (9 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Ediya.com.
Page size can be reduced by 2.0 MB (12%)
16.1 MB
14.2 MB
In fact, the total size of Ediya.com main page is 16.1 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. 75% 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 14.1 MB which makes up the majority of the site volume.
Potential reduce by 72.1 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 12.4 kB, which is 15% 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 72.1 kB or 84% of the original size.
Potential reduce by 255.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. EDIYA images are well optimized though.
Potential reduce by 892.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 892.1 kB or 84% of the original size.
Potential reduce by 743.0 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. Ediya.com needs all CSS files to be minified and compressed as it can save up to 743.0 kB or 87% of the original size.
Number of requests can be reduced by 36 (34%)
106
70
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EDIYA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
ediya.com
621 ms
ediya.com
1227 ms
js
82 ms
common.css
588 ms
ediya_2017_style.css
1384 ms
ediya_2017_member.css
1034 ms
ediya_2020_style.css
838 ms
fonts.css
638 ms
jquery-ui.css
853 ms
swiper.css
793 ms
animate.css
849 ms
ediya_eng.css
999 ms
ediya_chi.css
1060 ms
ediya_2018_festa_v180912.css
1070 ms
event_popup_style.css
1474 ms
event_2022_style.css
1396 ms
event_2023_style.css
1438 ms
event_2024_style.css
1288 ms
ediya_2023_style.css
1484 ms
ediya_2024_style.css
1502 ms
sanrio_style.css
1604 ms
sanrio_style_2nd.css
1608 ms
bluearchive_style.css
1654 ms
jquery-1.11.2.min.js
1917 ms
jquery-ui.js
3289 ms
script_function.js
1705 ms
imagesloaded.pkgd.min.js
1837 ms
jquery.pinto.min.js
1831 ms
brand_script.js
1881 ms
swiper.jquery.js
2329 ms
viewportchecker.js
2015 ms
coffee_main.bxslider.css
1856 ms
main_ani.css
1890 ms
jquery.bxslider.js
2151 ms
main_event_bn_close.png
2042 ms
catch_bn.png
2675 ms
top_logo.gif
2096 ms
top_logo_b.gif
2244 ms
slick.css
2107 ms
notosanskr.css
30 ms
css
46 ms
slick.js
2168 ms
ScrollMagic.js
1945 ms
m_nav_close.png
1832 ms
IMG_1718354437268.png
3255 ms
IMG_1718354437481.png
2182 ms
IMG_1718354437500.png
3733 ms
IMG_1717114549442.jpg
3007 ms
IMG_1717114549251.jpg
2345 ms
notosanssc.css
22 ms
IMG_1717114549191.jpg
2424 ms
IMG_1717114473693.jpg
3719 ms
IMG_1717114473604.jpg
2523 ms
IMG_1717114473708.jpg
2699 ms
IMG_1717031019478.png
2706 ms
IMG_1717031019882.png
3398 ms
IMG_1717031019720.png
3435 ms
IMG_1716356074456.jpg
3350 ms
IMG_1716356074634.jpg
3349 ms
IMG_1716356074581.jpg
7384 ms
IMG_1716356039215.jpg
4432 ms
IMG_1716356039843.jpg
3781 ms
NotoSansKR-Regular.woff
105 ms
font
134 ms
NotoSansKR-Medium.woff
141 ms
NotoSansKR-Light.woff
166 ms
NotoSansKR-Thin.woff
264 ms
NotoSansKR-Bold.woff
167 ms
NotoSansKR-Black.woff
216 ms
IMG_1716356039230.jpg
6588 ms
IMG_1714009882281.jpg
3634 ms
IMG_1714009882185.jpg
4481 ms
IMG_1714009881674.jpg
4409 ms
IMG_1714096582771.jpg
3862 ms
IMG_1714096582541.jpg
4139 ms
IMG_1714096581319.jpg
5044 ms
IMG_1709081029362.jpg
4381 ms
IMG_1709081029524.jpg
4521 ms
IMG_1709081028822.jpg
5070 ms
main_stick_ame01.png
4371 ms
main_stick_ame02.png
4597 ms
main_stick_ame03.png
4559 ms
main_stick_ame04.png
4688 ms
main_stick_latte01.png
4624 ms
main_stick_latte02.png
4868 ms
main_stick_latte03.png
4631 ms
main_stick_mix01.png
4578 ms
main_stick_mix02.png
4537 ms
dream_factory.png
4630 ms
font
8 ms
NanumSquare.woff
4573 ms
font
85 ms
main_store_btn.png
4221 ms
main_news_more.png
3959 ms
mypage_pop_close.gif
3904 ms
b2b_card.gif
3884 ms
members_pop_close.png
4027 ms
footer_ccm.png
4031 ms
bottom_logo.gif
3570 ms
util_line.gif
3392 ms
top_sns01.png
3502 ms
top_sns02.png
3499 ms
top_sns03.png
3512 ms
top_sns04.png
3467 ms
icon_search.gif
3057 ms
main_beanist_bg.gif
3292 ms
dream_factory_bg.gif
2745 ms
dream_factory_txt.png
2532 ms
block02_bg.jpg
2844 ms
company_bg.jpg
4220 ms
main_franchise_bg.jpg
2480 ms
main_store_bg.jpg
2359 ms
main_brochure_arrow.png
2270 ms
language_arrow.gif
2257 ms
footer_line.gif
2083 ms
bx_loader.gif
2194 ms
main_visual_prev.png
2111 ms
main_visual_next.png
2026 ms
ediya.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-hidden="true"] elements contain focusable descendents
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
ediya.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ediya.com SEO score
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
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 Ediya.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 Ediya.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.
ediya.com
Open Graph data is detected on the main page of EDIYA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: