10.1 sec in total
1.5 sec
7.7 sec
922 ms
Visit loveflower.co.kr now to see the best up-to-date Loveflower content and also check out these interesting facts you probably never knew about loveflower.co.kr
전국우수꽃집 500개의 체인망을 가지고 있는 꽃배달전문기업 (주)러브플라워닷컴
Visit loveflower.co.krWe analyzed Loveflower.co.kr page load time and found that the first response time was 1.5 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
loveflower.co.kr performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value16.5 s
0/100
25%
Value18.3 s
0/100
10%
Value210 ms
89/100
30%
Value0.398
25/100
15%
Value9.6 s
29/100
10%
1500 ms
51 ms
77 ms
81 ms
395 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 74% of them (115 requests) were addressed to the original Loveflower.co.kr, 8% (12 requests) were made to Scontent.cdninstagram.com and 7% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Loveflower.co.kr.
Page size can be reduced by 572.6 kB (9%)
6.1 MB
5.5 MB
In fact, the total size of Loveflower.co.kr main page is 6.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 5.7 MB which makes up the majority of the site volume.
Potential reduce by 91.3 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 32.7 kB, which is 32% 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 91.3 kB or 90% of the original size.
Potential reduce by 310.7 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. Loveflower images are well optimized though.
Potential reduce by 133.4 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 133.4 kB or 65% of the original size.
Potential reduce by 37.2 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. Loveflower.co.kr needs all CSS files to be minified and compressed as it can save up to 37.2 kB or 84% of the original size.
Number of requests can be reduced by 50 (35%)
144
94
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loveflower. 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 6 to 1 for CSS and as a result speed up the page load time.
loveflower.co.kr
1500 ms
nanumgothic.css
51 ms
css
77 ms
css
81 ms
common.js
395 ms
cid.generate.js
407 ms
wcslog.js
7 ms
optimizer.php
436 ms
optimizer.php
921 ms
list.html
455 ms
txt_progress.gif
443 ms
01.jpg
644 ms
02.jpg
849 ms
btn_prev.png
260 ms
btn_next.png
447 ms
close_btn.png
446 ms
bar.png
461 ms
01.jpg
1036 ms
02.jpg
1044 ms
03.jpg
1084 ms
btn_recent_prev.png
841 ms
btn_recent_next.png
894 ms
bnr_s.png
1060 ms
bnr.png
1675 ms
close.png
1103 ms
search_btn.png
1266 ms
sns_ico_01.png
1266 ms
sns_ico_03.png
1267 ms
sns_ico_04.png
1289 ms
01.jpg
1315 ms
02.jpg
1424 ms
03.jpg
1439 ms
btn_prev_off.png
1459 ms
btn_next_off.png
1497 ms
logo.jpg
1526 ms
btn_wishHeart_off.png
1620 ms
btn_wishHeart_on.png
1638 ms
gohome.gif
1658 ms
01.jpg
2959 ms
02.jpg
2377 ms
03.jpg
2604 ms
04.jpg
2644 ms
05.jpg
2671 ms
btn_prev_off.png
1876 ms
img_loading.gif
822 ms
btn_next_off.png
2082 ms
m
1538 ms
NanumGothic-Regular.woff
26 ms
NanumGothic-Bold.woff
40 ms
NanumGothic-ExtraBold.woff
180 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
128 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
143 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
141 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
142 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
37 ms
4cKlrioa77J2iqTqBgkRWg.ttf
141 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
143 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
142 ms
main_bnr_01.jpg
2204 ms
main_bnr_02.jpg
2281 ms
common.css
196 ms
layout.css
391 ms
modernizr.custom.js
583 ms
jquery-1.8.1.min.js
781 ms
placeholder.js
592 ms
main_bnr_03.jpg
2153 ms
main_bnr_05.jpg
2306 ms
main_bnr_06.jpg
2559 ms
main_bnr_07.jpg
2182 ms
analytics.js
49 ms
weblog.js
631 ms
collect
15 ms
async
2125 ms
SubCategory
2140 ms
main_bnr_08.jpg
2034 ms
flower34_268.jpg
2336 ms
flower34_1289.jpg
2565 ms
flower34_1562.jpg
2286 ms
flower34_266.jpg
2333 ms
12819139_1587740324885283_1327203958_n.jpg
326 ms
10817809_196233300748412_120331907_n.jpg
438 ms
11379332_209801319387557_1094523879_n.jpg
562 ms
12826072_612599162220435_64716631_n.jpg
550 ms
12819039_1029915173734890_1073331077_n.jpg
596 ms
10518208_806787809464806_1519376089_n.jpg
550 ms
12822313_203486676680341_609896235_n.jpg
737 ms
925727_1538759893085216_1582786484_n.jpg
610 ms
1169322_1698197220433857_617282683_n.jpg
688 ms
1517289_1706226199654279_327027657_n.jpg
647 ms
1390186_1736014923283726_1935462876_n.jpg
696 ms
10534889_555511881289435_369047087_n.jpg
721 ms
mslog.js
830 ms
flower34_1450.jpg
2352 ms
flower34_1572.jpg
2171 ms
flower34_1311.jpg
2311 ms
flower34_1006.jpg
2301 ms
flower34_228.jpg
2550 ms
flower34_182.jpg
2228 ms
flower34_212.jpg
2358 ms
flower34_1382.jpg
2344 ms
flower34_237.jpg
2350 ms
flower34_480.jpg
2317 ms
flower34_231.jpg
2242 ms
flower34_1388.jpg
2376 ms
icon_201603171441221700.png
2358 ms
flower34_1317.jpg
2395 ms
flower34_1390.jpg
2178 ms
ms.log
210 ms
flower34_1379.jpg
1992 ms
flower34_1380.jpg
1752 ms
flower34_1407.jpg
2053 ms
flower34_1402.jpg
1902 ms
btn_prev_off.png
1662 ms
btn_next_off.png
1670 ms
flower34_1286.jpg
1632 ms
flower34_1286.jpg
1628 ms
icon_201603171441069100.png
1711 ms
custom_1.gif
1673 ms
flower34_123.jpg
1638 ms
flower34_123.jpg
1627 ms
flower34_989.jpg
1688 ms
flower34_989.jpg
1701 ms
flower34_1277.jpg
1663 ms
flower34_1277.jpg
1674 ms
flower34_481.jpg
1634 ms
flower34_481.jpg
1368 ms
flower34_1393.jpg
1484 ms
flower34_1393.jpg
1447 ms
custom_2.gif
1455 ms
flower34_1490.jpg
1530 ms
flower34_1490.jpg
1341 ms
flower34_1377.jpg
1341 ms
flower34_1377.jpg
1450 ms
flower34_1448.jpg
1641 ms
flower34_1448.jpg
1309 ms
flower34_1391.jpg
1340 ms
flower34_1391.jpg
1332 ms
flower34_1390.jpg
1435 ms
flower34_1382.jpg
1446 ms
flower34_1380.jpg
1456 ms
01.png
1567 ms
02.png
1600 ms
footer_bnr_01.jpg
1432 ms
footer_bnr_02.jpg
1430 ms
footer_bnr_03.jpg
1438 ms
footer_bnr_04.jpg
1447 ms
footer_ico_02.png
1442 ms
footer_ico_03.png
1423 ms
footer_ico_13.png
1427 ms
btn_top_off.png
1420 ms
btn_top_on.png
1360 ms
header_nav_bar.gif
1390 ms
search_bg.png
1437 ms
best_ico_01.png
1424 ms
sale_bg_01.gif
1404 ms
utilMenu_bar.gif
1402 ms
loveflower.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
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.
loveflower.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
loveflower.co.kr 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
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 Loveflower.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 Loveflower.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.
loveflower.co.kr
Open Graph description is not detected on the main page of Loveflower. 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: