Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

sixflower.com

六朵花鲜花网-网上花店订花-鲜花速递-提供送花上门服务

Page Load Speed

7.7 sec in total

First Response

703 ms

Resources Loaded

6.7 sec

Page Rendered

295 ms

sixflower.com screenshot

About Website

Click here to check amazing Sixflower content. Otherwise, check out these important facts you probably never knew about sixflower.com

六朵花是专门提供网上订花送花和鲜花速递服务的花店,多年来专注于网上花店的送花服务,我们深知每一束鲜花都蕴含着您的重要心意,以感恩之心设计好每一款鲜花,将您的爱、情感原汁原味传递到她的身旁。

Visit sixflower.com

Key Findings

We 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.

Performance Metrics

sixflower.com performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.214

58/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

sixflower.com

703 ms

www.sixflower.com

1415 ms

Index.css

1177 ms

loadimg.js

1092 ms

logo.jpg

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 Optimization Overview & Recommendations

Page size can be reduced by 138.4 kB (19%)

Content Size

711.6 kB

After Optimization

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.

HTML Optimization

-90%

Potential reduce by 117.2 kB

  • Original 130.1 kB
  • After minification 88.3 kB
  • After compression 12.9 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.

Image Optimization

-3%

Potential reduce by 19.5 kB

  • Original 576.4 kB
  • After minification 556.9 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.

JavaScript Optimization

-24%

Potential reduce by 275 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 878 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.

CSS Optimization

-36%

Potential reduce by 1.4 kB

  • Original 4.0 kB
  • After minification 4.0 kB
  • After compression 2.6 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.

Requests Breakdown

Number of requests can be reduced by 31 (44%)

Requests Now

70

After Optimization

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.

Accessibility Review

sixflower.com accessibility score

64

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sixflower.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

sixflower.com SEO score

99

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: