Tools & Wizards About Us
voeflorist.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

voeflorist.com

Voe Florist | 薇花坊 | Melaka Flower Shop | Florist in Melaka, malaysia | Flower Delivery

Page Load Speed

4.8 sec in total

First Response

468 ms

Resources Loaded

3.2 sec

Page Rendered

1.1 sec

voeflorist.com screenshot

About Website

Visit voeflorist.com now to see the best up-to-date Voe Florist content and also check out these interesting facts you probably never knew about voeflorist.com

Voe Florist has established 6 years, located at Melaka Raya, Melaka. We are specialized in artificial flower, congratulation or opening stand, flower basket, flower and fruit, flower and gift, graduat...

Visit voeflorist.com

Key Findings

We analyzed Voeflorist.com page load time and found that the first response time was 468 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

voeflorist.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value61.1 s

0/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.616

10/100

15%

TTI (Time to Interactive)

Value34.2 s

0/100

10%

Network Requests Diagram

voeflorist.com

468 ms

voeflorist.com

438 ms

styles2.css

104 ms

puritan.css

215 ms

default.css

298 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 96% of them (86 requests) were addressed to the original Voeflorist.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Voeflorist.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 567.2 kB (5%)

Content Size

11.0 MB

After Optimization

10.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Voeflorist.com main page is 11.0 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. 70% of websites need less resources to load. Images take 10.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 18.0 kB

  • Original 23.0 kB
  • After minification 22.0 kB
  • After compression 5.0 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 18.0 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 505.9 kB

  • Original 10.8 MB
  • After minification 10.3 MB

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. Voe Florist images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 41.2 kB

  • Original 135.9 kB
  • After minification 132.7 kB
  • After compression 94.7 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 41.2 kB or 30% of the original size.

CSS Optimization

-20%

Potential reduce by 2.2 kB

  • Original 10.9 kB
  • After minification 10.9 kB
  • After compression 8.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. Voeflorist.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (16%)

Requests Now

87

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voe Florist. 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.

Network Requests Diagram

voeflorist.com

voeflorist.com

468 ms

voeflorist.com

voeflorist.com

438 ms

styles2.css

styles2.css

104 ms

puritan.css

puritan.css

215 ms

default.css

default.css

298 ms

nivo-slider.css

nivo-slider.css

297 ms

slimbox2.css

slimbox2.css

296 ms

jquery-1.5.min.js

jquery-1.5.min.js

403 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

303 ms

ddsmoothmenu.js

ddsmoothmenu.js

321 ms

scripts.js

scripts.js

399 ms

slimbox2.js

slimbox2.js

397 ms

addthis_widget.js

addthis_widget.js

41 ms

jquery-min.js

jquery-min.js

518 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

404 ms

a1b1c22.css

a1b1c22.css

325 ms

header-bg.png

header-bg.png

114 ms

logo.png

logo.png

198 ms

loading.gif

loading.gif

114 ms

s2.jpg

s2.jpg

293 ms

1.jpg

1.jpg

388 ms

slide3.jpg

slide3.jpg

428 ms

s3.jpg

s3.jpg

587 ms

a1.jpg

a1.jpg

493 ms

a2.jpg

a2.jpg

398 ms

a3.jpg

a3.jpg

494 ms

1Rm220%209pcs%20rose.jpg

1Rm220%209pcs%20rose.jpg

491 ms

2Rm280%20%20%2015pcs.jpg

2Rm280%20%20%2015pcs.jpg

599 ms

3Rm280%2015pcs%20rose.jpg

3Rm280%2015pcs%20rose.jpg

623 ms

4Rm280%2015pcs%20rose.jpg

4Rm280%2015pcs%20rose.jpg

594 ms

5rm238.jpg

5rm238.jpg

782 ms

6Rm188.jpg

6Rm188.jpg

699 ms

7Rm458%2022pcs%20rose.jpg

7Rm458%2022pcs%20rose.jpg

878 ms

8Rm280%2012pcs%20rose.jpg

8Rm280%2012pcs%20rose.jpg

697 ms

9Rm458%2022pcs%20rose.jpg

9Rm458%2022pcs%20rose.jpg

702 ms

10Rm520%20%2033pcs%20rose.jpg

10Rm520%20%2033pcs%20rose.jpg

723 ms

11Rm380.jpg

11Rm380.jpg

804 ms

12Rm580.jpg

12Rm580.jpg

799 ms

13Rm250%20Prune%20Amethyst%20rose.jpg

13Rm250%20Prune%20Amethyst%20rose.jpg

805 ms

14Rm358.jpg

14Rm358.jpg

826 ms

15Rm300.jpg

15Rm300.jpg

981 ms

16Rm230.jpg

16Rm230.jpg

902 ms

17Rm350.jpg

17Rm350.jpg

908 ms

18300.jpg

18300.jpg

907 ms

19rm250.jpg

19rm250.jpg

931 ms

20rm%20520.jpg

20rm%20520.jpg

1077 ms

1Rm488%20%E6%B0%B8%E7%94%9F%E8%8A%B1.jpg

1Rm488%20%E6%B0%B8%E7%94%9F%E8%8A%B1.jpg

1006 ms

2Rm328.jpg

2Rm328.jpg

1012 ms

3Rm400%20include%20money%20Rm100.jpg

3Rm400%20include%20money%20Rm100.jpg

1011 ms

4Rm180.jpg

4Rm180.jpg

1036 ms

5Rm180.jpg

5Rm180.jpg

1032 ms

analytics.js

analytics.js

22 ms

puritan_regular-webfont.woff

puritan_regular-webfont.woff

1029 ms

collect

collect

15 ms

6Rm338%2033%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

6Rm338%2033%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

1008 ms

7Rm338%20%2033%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

7Rm338%20%2033%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

1008 ms

js

js

89 ms

8Rm318%20%2033%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

8Rm318%20%2033%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

950 ms

9Rm320%20%20%2048%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

9Rm320%20%20%2048%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

898 ms

10%20Rm280.jpg

10%20Rm280.jpg

807 ms

11Rm300.jpg

11Rm300.jpg

824 ms

12Rm180.jpg

12Rm180.jpg

794 ms

13Rm320.jpg

13Rm320.jpg

734 ms

14Rm288.jpg

14Rm288.jpg

757 ms

15Rm550%20%2099%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

15Rm550%20%2099%E6%9C%B5%E9%A6%99%E7%9A%82%E7%8E%AB%E7%91%B0.jpg

805 ms

16Rm288.jpg

16Rm288.jpg

716 ms

17Rm298.jpg

17Rm298.jpg

730 ms

18Rm268.jpg

18Rm268.jpg

724 ms

a150.jpg

a150.jpg

711 ms

2o350.jpg

2o350.jpg

657 ms

3Rm220.jpg

3Rm220.jpg

709 ms

1hRm268.jpg

1hRm268.jpg

705 ms

22.jpg

22.jpg

705 ms

1fRm288.jpg

1fRm288.jpg

646 ms

12.jpg

12.jpg

638 ms

5gRm188.jpg

5gRm188.jpg

656 ms

33.jpg

33.jpg

703 ms

5Rm800.jpg

5Rm800.jpg

683 ms

1RM220.jpg

1RM220.jpg

657 ms

4b150.jpg

4b150.jpg

633 ms

2sRm220.jpg

2sRm220.jpg

632 ms

2cRm180.jpg

2cRm180.jpg

652 ms

clock.png

clock.png

683 ms

call.png

call.png

629 ms

whatsapp.png

whatsapp.png

634 ms

money.png

money.png

630 ms

rhb.png

rhb.png

636 ms

maybank.png

maybank.png

631 ms

footer-bg.png

footer-bg.png

635 ms

arrows.png

arrows.png

106 ms

Accessibility Review

voeflorist.com accessibility score

65

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

voeflorist.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

voeflorist.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voeflorist.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Voeflorist.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.

Social Sharing Optimization

voeflorist.com

Open Graph description is not detected on the main page of Voe Florist. 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: