7.7 sec in total
703 ms
6.7 sec
295 ms
Click here to check amazing Sixflower content. Otherwise, check out these important facts you probably never knew about sixflower.com
六朵花是专门提供网上订花送花和鲜花速递服务的花店,多年来专注于网上花店的送花服务,我们深知每一束鲜花都蕴含着您的重要心意,以感恩之心设计好每一款鲜花,将您的爱、情感原汁原味传递到她的身旁。
Visit sixflower.comWe analyzed Sixflower.com page load time and found that the first response time was 703 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sixflower.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value3.0 s
79/100
25%
Value2.6 s
97/100
10%
Value0 ms
100/100
30%
Value0.214
58/100
15%
Value2.9 s
96/100
10%
703 ms
1415 ms
1177 ms
1092 ms
236 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 56% of them (40 requests) were addressed to the original Sixflower.com, 44% (32 requests) were made to Img1.sixflower.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Img1.sixflower.com.
Page size can be reduced by 138.4 kB (19%)
711.6 kB
573.2 kB
In fact, the total size of Sixflower.com main page is 711.6 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 576.4 kB which makes up the majority of the site volume.
Potential reduce by 117.2 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 41.8 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 117.2 kB or 90% of the original size.
Potential reduce by 19.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. Sixflower images are well optimized though.
Potential reduce by 275 B
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 275 B or 24% of the original size.
Potential reduce by 1.4 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. Sixflower.com needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 36% of the original size.
Number of requests can be reduced by 31 (44%)
70
39
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sixflower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
sixflower.com
703 ms
www.sixflower.com
1415 ms
Index.css
1177 ms
loadimg.js
1092 ms
logo.jpg
236 ms
Top1Button.gif
237 ms
bg_orange1.gif
237 ms
tableft5.gif
476 ms
tabright5.gif
474 ms
bg_green1.gif
710 ms
bg_ggreen1.gif
709 ms
2020111610472217720.jpg
946 ms
20219810535412746.jpg
946 ms
201991697821956.jpg
947 ms
20207312002235913.jpg
1196 ms
20243717151024710.jpg
2648 ms
2024361245269769.jpg
1235 ms
20244168424659369.jpg
1184 ms
202441915342237494.jpg
1183 ms
20242611325063387.jpg
1182 ms
2024213912828675.jpg
3013 ms
2024261443232569.jpg
1420 ms
202421215472398101.jpg
1420 ms
loadingback.jpg
1431 ms
bg_ggreen1.jpg
1484 ms
firstlogo.jpg
671 ms
num1.gif
909 ms
num2.gif
954 ms
num3.gif
960 ms
num4.gif
962 ms
num5.gif
974 ms
num6.gif
974 ms
num7.gif
1144 ms
num8.gif
1188 ms
num9.gif
1197 ms
num10.gif
1201 ms
button_old_41.gif
1216 ms
TitleInfo_01.gif
1217 ms
TitleInfo_02.gif
1380 ms
imageinfo_01.gif
1425 ms
imageinfo_02.gif
1434 ms
imageinfo_04.gif
1438 ms
imageinfo_05.gif
1456 ms
TitleInfo_04.gif
1453 ms
TitleInfo_06.gif
1617 ms
TitleInfo_08.gif
1663 ms
TitleInfo_10.gif
1671 ms
TitleInfo_11.gif
1676 ms
TitleInfo_12.gif
1695 ms
TitleInfo_13.gif
1698 ms
TitleInfo_14.gif
1850 ms
TitleInfo_19.gif
1898 ms
TitleInfo_20.gif
1909 ms
TitleInfo_21.gif
1915 ms
TitleInfo_22.gif
1937 ms
weixinlogo.jpg
1938 ms
onlinechat.jpg
2086 ms
gaba.png
2137 ms
FootImg1.jpg
2148 ms
FootImg2.jpg
2153 ms
202455741954075.jpg
1548 ms
20245317462140893.jpg
1546 ms
20244291265261513.jpg
1559 ms
20244291111290451.jpg
1620 ms
20244281283257781.jpg
1785 ms
2024337524853872.jpg
1785 ms
20241118323810558.jpg
1799 ms
20241811481310128.jpg
3496 ms
2024177571313059.jpg
2021 ms
2023122314284423128.jpg
2024 ms
floatchat.jpg
3333 ms
Newprodct.jpg
1519 ms
sixflower.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
sixflower.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
sixflower.com SEO score
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
![]()
ZH
![]()
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sixflower.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Sixflower.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
sixflower.com
Open Graph description is not detected on the main page of Sixflower. 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: